/* ═══════════════════════════════════════════════════════════════════════ Overrides applied to the SITEMAP, in its embedded form on this site. READ THIS BEFORE ADDING TO IT. This is a patch from outside onto markup this repo does not own. The sitemap is a separate application, deployed separately; we only get to touch it here because functions/[[path]].js serves it through this domain and appends this file to its . Two consequences: - It applies ONLY to visitors who come through desertpalisadeslots.com. The sitemap's own URL is unaffected, so the two look different. - Every selector here is a bet on class names in someone else's build. When that build changes, these rules stop matching and quietly do nothing. They fail invisible, which is the bad way to fail. So this is a stopgap for things wanted NOW, and each rule says what it is for and what it measured, so the next person can tell a live fix from a dead one. Anything that can be fixed at source should be. ═══════════════════════════════════════════════════════════════════════ */ /* ── The inquiry modal ───────────────────────────────────────────────── Measured in the running app at 1440x900: the card .inquire-form-side carries an explicit height of 770px, and .inquire-fields inside it is flex: 1 1 auto with align-content: start — so the fields box stretches to the card's height while its rows stay at the top, and all the slack piles up in one place. 140px of it, between the agent/broker row and Submit. The card cannot shrink on its own, and `height: auto` does not help — the app already sets that, with !important, and it is powerless here: .inquire-overlay .inquire-form-side { position: fixed; top: 40px; bottom: calc(100vh - var(--inquire-map-bottom, 90vh)); height: auto !important; } A fixed box anchored at BOTH top and bottom is stretched between them and `height: auto` resolves to that distance, not to the content. 40px down from the top and 90px up from the bottom of a 900px window is exactly the 770px measured. Releasing the bottom edge is what lets it size to its content; max-height then caps it and the card scrolls if a form ever outgrows the window. */ .inquire-overlay .inquire-form-side { bottom: auto !important; max-height: min(90vh, 940px) !important; overflow-y: auto !important; } .inquire-overlay .inquire-content { flex: 0 1 auto !important; overflow-y: auto !important; } .inquire-overlay .inquire-form { flex: 0 0 auto !important; } .inquire-overlay .inquire-fields { flex: 0 0 auto !important; overflow-y: visible !important; } /* The heading was 50.4px against a 920px card — small for the one line of display type in the dialogue. Clamped rather than fixed so it holds on a phone, where the card is the width of the screen. */ .inquire-overlay .inquire-heading { font-size: clamp(38px, 4.6vw, 72px) !important; line-height: 1.04 !important; } /* ── The intro tagline ─────────────────────────────────────── "110 rare, elevated homesites", under the mark on the way in, set all in lower case. The client wants each word capitalised. text-transform, because the words are not ours to retype: the app builds that line in script, splitting the string on spaces and wrapping each word in its own span to stagger them — _e.id = "dpV2Tag"; _e.innerHTML = "110 rare, elevated homesites".split(" ").map(… dpv2-tw …) — so the text is a literal in the bundle and the only thing reachable from out here is how it is rendered. Capitalising the container covers every word without touching the stagger. The id is the app's own, not a class name, so this is a slightly safer bet than the rules above it; it still fails silently if that element is ever renamed. */ #dpV2Tag { text-transform: capitalize !important; } /* ── The heading-font lab ──────────────────────────────────── The face is chosen — Italiana, which is what both halves were already set in — so the dev panel of eleven serifs below the sitemap's footer comes off. Hidden rather than deleted, because it is not ours to delete: the block and its