/* Design system
built on Bootstrap 5.3 primitives (grid, dropdown, offcanvas,
accordion). This file supplies brand tokens and the custom
components Bootstrap doesn't provide out of the box: property
cards, the pill AI search bar, the mega-menu panel, and badges. */
:root {
--brand: #003580;
--brand-dark: #00265c;
--brand-rgb: 0,53,128;
--ink: #222222;
--muted: #6b7280;
--border: #e5e7eb;
--surface: #ffffff;
--bg: #ffffff;
/* Subtle hover/loading-placeholder background and the light "active/
selected" tint (2026-09-22, dark-mode work) — consolidated from what
were ~18 separate hardcoded near-duplicate grays/blues scattered
across this file, so both light AND dark now stay in sync from one
definition each instead of needing every call site hand-tuned. */
--surface-alt: #f4f4f6;
--surface-tint: #eef3fa;
--radius: 8px;
/* Fallback only — includes/header.php/adm/_header.php/adm/index.php
all echo render_site_font_head() right after this stylesheet loads,
which overrides this same variable per the admin's font choice
(adm/settings.php's Systém tab). This value only ever applies if
that render call is somehow skipped. */
--bs-body-font-family: 'Plus Jakarta Sans', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
}
/* Booking.com/MegaBooking-style flat, business-like corners everywhere —
overriding Bootstrap's .rounded-pill utility globally is far cheaper
than touching every button/badge/input across ~20 PHP templates that
use it inline, and keeps future markup consistent for free. */
.rounded-pill { border-radius: var(--radius) !important; }
.form-control, .form-select { border-radius: var(--radius); }
/* Sitewide 95% root scale (initially shipped at 90%, then relaxed to 95%
per direct user follow-up) — comparing this site's own feel at 100%
browser zoom against a sibling project (uctovnictvo.dataclick.sk) that
read as more "natural"/compact at the same zoom. That reference turned
out to still use a plain 16px root (confirmed live via computed
styles, not guessed) — the difference is density, not a literal
font-size trick — so this one root scale-down is the actual fix rather
than a full type-scale rebuild: Bootstrap 5's own grid gutters,
spacing utilities, and every rem-based font-size (h1-h6, .fs-*, form
controls, badges...) all shrink together by the same amount, since
they're all expressed in rem, while Bootstrap's own breakpoints are
compiled to fixed px and stay unaffected — so the responsive layout
itself doesn't shift, only how large everything reads. */
html { font-size: 95%; }
body {
font-family: var(--bs-body-font-family);
color: var(--ink);
background: var(--bg);
}
a { color: inherit; }
/* Self-hosted flag SVGs (see h() sibling flag_icon() in functions.php) —
Windows browsers render Unicode flag emoji as plain two-letter text,
not an actual flag image, so an still gives it lasting keyboard focus,
which otherwise shows a native blue outline that stays visible until
something else steals focus — not tied to the dropdown actually being
open/closed, so it looks like a stray leftover highlight on a menu item
the visitor already moved away from (2026-09-27 user report). Native
:focus-visible alone doesn't reliably distinguish this for elements
here — confirmed live that Chromium still matches :focus-visible after a
genuine mouse click on this exact element (role="button" doesn't change
that for an anchor, unlike a real ) — so the outline is instead
driven by a tiny real "was the last input a keyboard?" detector
(main.js's html.using-keyboard toggle) rather than trusting the
pseudo-class's own per-browser heuristic. Suppressed for a mouse click,
shown for genuine keyboard Tab navigation, per WCAG 2.4.7. */
.navbar-nav .nav-link:focus {
outline: none;
}
html.using-keyboard .navbar-nav .nav-link:focus {
outline: 2px solid var(--brand);
outline-offset: 2px;
}
.navbar-nav .dropdown-toggle::after {
margin-left: .4rem;
vertical-align: .1em;
transition: transform .2s ease;
}
.navbar-nav .dropdown-toggle[aria-expanded="true"]::after {
transform: rotate(180deg);
}
/* ---------- Elegant buttons (site-wide) ----------
Every Bootstrap .btn gets the same refined treatment: a full pill
shape, medium weight, a soft lift + tinted shadow on hover instead of
a flat color swap, and no visible focus ring flash. Individual
variants (outline-*, success, warning, danger, dark, link) only
override color where Bootstrap's default would clash with this. */
.btn {
border-radius: var(--radius);
font-weight: 600;
letter-spacing: .01em;
transition: background-color .18s ease, border-color .18s ease, color .18s ease, transform .12s ease, box-shadow .18s ease;
}
.btn:hover { transform: translateY(-1px); }
.btn:active { transform: translateY(0); }
.btn:focus, .btn:focus-visible { box-shadow: 0 0 0 .2rem rgba(34,34,34,.12); }
.btn.btn-sm { font-weight: 600; }
.btn-link { text-decoration: none; font-weight: 600; }
.btn-link:hover { text-decoration: underline; transform: none; }
.btn-outline-secondary,
.btn-outline-dark {
background: var(--surface);
}
.btn-outline-secondary:hover,
.btn-outline-dark:hover {
box-shadow: 0 6px 16px rgba(0,0,0,.1);
}
.btn-success:hover { box-shadow: 0 6px 16px rgba(25,135,84,.28); }
.btn-warning:hover { box-shadow: 0 6px 16px rgba(255,193,7,.35); }
.btn-danger:hover { box-shadow: 0 6px 16px rgba(220,53,69,.28); }
.btn-dark:hover { box-shadow: 0 6px 16px rgba(0,0,0,.3); }
.btn-brand {
background: var(--brand);
color: #fff;
border: none;
}
.btn-brand:hover,
.btn-brand:focus {
background: var(--brand-dark);
color: #fff;
box-shadow: 0 6px 16px rgba(var(--brand-rgb),.28);
}
.lang-switch-btn, .user-chip {
border: 1px solid var(--border);
border-radius: var(--radius);
font-weight: 600;
font-size: .85rem;
padding: .45rem .9rem;
background: var(--surface);
color: var(--ink);
transition: background-color .18s ease, border-color .18s ease;
}
.lang-switch-btn:hover, .user-chip:hover { background: var(--surface-alt); border-color: #d1d5db; }
.dropdown-item {
transition: background-color .15s ease, color .15s ease, padding-left .15s ease;
}
.dropdown-item:hover { padding-left: 1.1rem; }
.dropdown-item.active, .dropdown-item:active {
background-color: var(--surface-tint);
color: var(--brand);
}
.season-badge {
background: var(--brand);
border-radius: var(--radius);
color: #fff;
font-weight: 700;
padding: .5rem .9rem;
font-size: .8rem;
display: inline-flex;
align-items: center;
animation: seasonPulse 2.6s ease-in-out infinite;
}
@keyframes seasonPulse {
0%, 100% { box-shadow: 0 0 0 0 rgba(var(--brand-rgb),.35); }
50% { box-shadow: 0 0 0 6px rgba(var(--brand-rgb),0); }
}
/* Animated dropdown / mega-menu panels (Bootstrap toggles .show; we
keep the element always laid out but fade+slide it in/out so the
menu feels alive instead of snapping open). */
.dropdown-menu {
display: block !important;
opacity: 0;
visibility: hidden;
transform: translateY(-8px) scale(.98);
transition: opacity .18s ease, transform .18s ease, visibility .18s;
pointer-events: none;
transform-origin: top center;
}
.dropdown-menu.show {
opacity: 1;
visibility: visible;
transform: translateY(0) scale(1);
pointer-events: auto;
}
/* Destination country-tab switcher inside the mega-panel — panel
footprint stays constant as more countries get listings; only the
active country's regions/districts/cities render visible. Wraps to
a second row (not horizontal scroll) if enough countries exist that
they don't fit one line, so it degrades gracefully either way. */
.dest-tabs {
display: flex;
flex-wrap: wrap;
gap: .4rem;
}
.dest-tab {
display: inline-flex;
align-items: center;
gap: .4rem;
border: 1px solid #e5e7eb;
background: var(--surface);
border-radius: 999px;
padding: .35rem .85rem;
font-size: .85rem;
font-weight: 600;
color: var(--ink);
cursor: pointer;
transition: background .15s ease, border-color .15s ease, color .15s ease;
}
.dest-tab:hover { border-color: var(--brand); color: var(--brand); }
.dest-tab.active { background: var(--brand); border-color: var(--brand); color: #fff; }
.dest-panel { display: none; }
.dest-panel.active { display: block; }
/* "Filtre" mega-panel (2026-09-20) — reuses .dest-tabs/.dest-tab/
.dest-panel wholesale (same JS click handler in main.js already
works generically off those classes, no JS changes needed) but each
panel holds a wrapping chip grid instead of destination columns,
since a group can have 8-14 flat tags with no sub-hierarchy to
column-split. Wider than the default .mega-panel so ~14 chips per
row don't force an awkwardly tall, narrow panel. */
.mega-panel--filters { min-width: 720px; max-width: 820px; }
.filter-tag-chips {
display: flex;
flex-wrap: wrap;
gap: .5rem;
}
.filter-tag-chip {
display: inline-block;
border: 1px solid #e5e7eb;
border-radius: 999px;
padding: .4rem 1rem;
font-size: .85rem;
font-weight: 500;
color: var(--ink);
text-decoration: none;
transition: background .15s ease, border-color .15s ease, color .15s ease;
}
.filter-tag-chip:hover { background: var(--brand); border-color: var(--brand); color: #fff; }
/* Mega-menu dropdown panel. Widened + nowrap so longer destination
names (e.g. "Lednicko-valtický areál") never wrap onto a second
line inside the col-6 country columns — found live: at the old
480px min-width they did. */
.mega-panel {
min-width: 640px;
}
/* Destination lists widened to show 16 per country (2026-09-21) — a
single 16-row vertical list would make the panel oddly tall, so a
section with more than 8 rows splits into 2 sub-columns (8+8) via
CSS Grid with `max-content` column tracks: each sub-column sizes to
its own widest row's real text width, so nothing ever wraps.
Three approaches were tried and rejected live, in order: CSS
multi-column (`column-count:2`) let a long row's own text overflow
into the next column since its track width is an even split of the
container, not sized to its own content; allowing `white-space:
normal` to wrap instead avoided the overlap but produced visibly
wrapped text; making the 3 sections themselves `flex-wrap`/auto-width
(so the whole panel would grow to fit) instead made Chrome's
shrink-to-fit sizing collapse the panel back to its bare min-width
floor — a flex container with wrapping children doesn't reliably
report its full preferred width to an ancestor computing shrink-to-
fit — which then forced all 3 sections to stack vertically instead
of sitting side by side, the opposite of what was asked for. Final
fix: the panel is a normal fixed-width box again (like before this
whole feature), sections never wrap (`flex-wrap: nowrap`), and if
16-per-section content is ever wider than the panel, the sections
row itself scrolls horizontally rather than wrapping or forcing the
panel wider than the viewport. */
/* Centered horizontally on the page (2026-09-21, revised from an
earlier flush-left-at-the-logo version) rather than anchored to its
own toggle — still earns enough width to show 16 destinations per
section without the horizontal scroll fallback kicking in, without
needing to start right at the page's own left edge. `left: 50%` +
`translateX(-50%)` centers it regardless of its own actual rendered
width, so no JS measurement of the box itself is needed — only
`top`/`max-width` still need computing against the real header
height/viewport width (main.js), since those genuinely vary.
`data-bs-display="static"` on the toggle (header.php) turns off
Bootstrap's own Popper-driven positioning; `position`/`left`/
`transform` are additionally set inline by main.js (not just here)
since Bootstrap's `.dropdown-menu[data-bs-popper]` rule has higher
specificity than a plain class and was silently overriding this
class's own `position: fixed` — inline styles beat any CSS rule
regardless of specificity, which is what actually makes it stick. */
.mega-panel--destinations {
position: fixed;
left: 50%;
transform: translateX(-50%);
top: 90px;
min-width: 920px;
max-width: min(96vw, 1300px);
}
.mega-dest-sections {
align-items: flex-start;
flex-wrap: nowrap;
overflow-x: auto;
}
.mega-dest-section { flex: 0 0 auto; }
/* A default overlay scrollbar is invisible until actively scrolling —
made permanently visible (thin, subtle) so a visitor actually
notices there's more to see, instead of discovering it by accident. */
.mega-dest-sections { scrollbar-width: thin; }
.mega-dest-sections::-webkit-scrollbar { height: 6px; }
.mega-dest-sections::-webkit-scrollbar-track { background: transparent; }
.mega-dest-sections::-webkit-scrollbar-thumb { background: #d1d5db; border-radius: 999px; }
.mega-list--cols {
display: grid;
grid-template-columns: repeat(2, max-content);
grid-template-rows: repeat(var(--mega-rows, 1), auto);
grid-auto-flow: column;
column-gap: 1.75rem;
}
.mega-list li { margin-bottom: .55rem; }
.mega-list a {
text-decoration: none;
color: var(--ink);
font-weight: 500;
font-size: .92rem;
transition: color .15s ease, padding-left .15s ease;
display: inline-block;
white-space: nowrap;
}
.mega-list a:hover { color: var(--brand); padding-left: .25rem; }
/* "Zobraziť všetky..." link under each mega-panel section (2026-09-20) —
deliberately always present, not conditionally shown only once the
real list actually exceeds what's displayed, so the menu never needs
touching again as regions/districts/cities keep getting real listings. */
.mega-list__see-all {
display: inline-block;
font-size: .82rem;
font-weight: 600;
color: var(--brand);
text-decoration: none;
}
.mega-list__see-all:hover { text-decoration: underline; }
/* Region hover flyout — shows which property-type categories have
listings in that destination (e.g. "Liptov" -> "Chaty (3)"). Opens
to the RIGHT of the link (not below it) — `width: max-content` on
the `` shrinks its box to the link's own text so `left: 100%`
lands right next to the label instead of at the far edge of the
(much wider) column. Shown via a JS-added `.show` class (main.js,
same delayed mouseenter/mouseleave pattern as the top-level
dropdowns) rather than plain CSS :hover alone — a pure-CSS flyout
has a dead zone between the trigger and the flyout, and crossing
that gap was enough to hide it before the cursor arrived. `:hover`
stays too as a no-JS fallback. */
.mega-list__item { position: relative; width: max-content; max-width: 100%; }
.region-flyout {
display: none;
position: absolute;
left: 100%;
top: 50%;
margin-left: .5rem;
background: var(--surface);
border-radius: .75rem;
box-shadow: 0 10px 30px rgba(0,0,0,.14);
padding: .5rem;
min-width: 170px;
opacity: 0;
visibility: hidden;
transform: translate(-4px, -50%);
/* A snappier "ease-out" curve on the transform reads more like a real
app's flyout/tooltip than a plain linear/ease slide (2026-09-21) —
the JS-driven open (main.js) computes its own viewport-clamped
top/left/transform inline, so this transition is what actually
animates between the pre- and post-open values it sets. */
transition: opacity .18s ease, transform .22s cubic-bezier(.16, 1, .3, 1), visibility .18s;
pointer-events: none;
z-index: 20;
}
/* `display: none` (not just opacity/visibility) when closed, added
2026-09-21: a flyout for an item near the BOTTOM of its 8-row column
extends well past `.mega-dest-sections`'s own bottom edge even while
fully invisible — an opacity/visibility-hidden box still occupies
its absolutely-positioned layout space and was silently inflating
the row's own `scrollHeight`, which (since that row now needs
`overflow-x: auto`, forcing overflow-y to clip/scroll too) showed an
unwanted, unnecessary vertical scrollbar even though no visible
content actually needed one. `display: none` removes it from layout
entirely while closed, so it can no longer inflate anything. */
.mega-list__item:hover .region-flyout,
.mega-list__item.show .region-flyout {
display: block;
opacity: 1;
visibility: visible;
transform: translate(0, -50%);
pointer-events: auto;
}
/* Once `.mega-dest-sections` needs `overflow-x: auto` (2026-09-21, so
16 destinations per section can scroll instead of wrapping the whole
row), the browser is forced to also clip vertically — overflow-x and
overflow-y can't independently be scroll/visible, only one or the
other computed for both once either isn't `visible`. That silently
clipped this flyout whenever it extended above the row's own top
edge (any item in roughly the first 2 rows). Fixed in main.js by
reparenting the flyout to with JS-computed `position: fixed`
the moment it opens — no longer a descendant of the clipping
container at all — so this class (not the ancestor-dependent
`.show`/`:hover` selectors above, which stop matching the instant
it's moved) is what actually shows it while reparented; z-index
raised well past Bootstrap's own dropdown (1000) since the flyout
now sits in its own top-level stacking context on . */
.region-flyout--open {
display: block;
opacity: 1;
visibility: visible;
pointer-events: auto;
z-index: 1060;
}
.region-flyout__item {
display: block;
text-decoration: none;
color: var(--ink);
font-size: .84rem;
font-weight: 500;
white-space: nowrap;
padding: .3rem .5rem;
border-radius: .5rem;
transition: background .12s ease;
}
.region-flyout__item:hover { background: var(--surface-alt); color: var(--brand); }
/* "Typ ubytovania" mega-menu hover flyout (2026-09-21) — same visual
shape and reparent-to- JS mechanism as .region-flyout above
(shared function, main.js), kept as its own separate set of classes
rather than refactored to share CSS rules with an already-recently-
stabilized feature (History #109/#111 both fixed real regressions in
the region-flyout's own CSS) — duplicating a small, proven-working
shape here carries far less regression risk than merging it. Only
real difference: the city list itself scrolls (`max-height` +
`overflow-y: auto`) since a type can have far more matching cities
than fit in one screen's height, per the user's own explicit ask. */
.type-flyout-item { position: relative; }
.type-flyout-item__chevron { font-size: .68rem; color: var(--muted); margin-left: .75rem; flex-shrink: 0; }
.type-city-flyout {
display: none;
position: absolute;
left: 100%;
top: 0;
margin-left: .5rem;
background: var(--surface);
border-radius: .75rem;
box-shadow: 0 10px 30px rgba(0,0,0,.14);
padding: .5rem;
min-width: 220px;
opacity: 0;
visibility: hidden;
transform: translateX(-4px);
transition: opacity .18s ease, transform .22s cubic-bezier(.16, 1, .3, 1), visibility .18s;
pointer-events: none;
z-index: 20;
}
.type-flyout-item:hover .type-city-flyout,
.type-flyout-item.show .type-city-flyout {
display: block;
opacity: 1;
visibility: visible;
transform: translateX(0);
pointer-events: auto;
}
.type-city-flyout--open {
display: block;
opacity: 1;
visibility: visible;
pointer-events: auto;
z-index: 1060;
}
/* Only the country matching the visitor's current Destinácie tab
selection is ever shown (main.js toggles `.active` right before the
flyout opens) — everything else stays `display:none` so an unrelated
country's cities never flash into view even for a frame. */
.type-city-flyout__country { display: none; }
.type-city-flyout__country.active { display: block; }
.type-city-flyout__scroll {
/* 320px is only the no-JS/no-hover CSS-`:hover` fallback ceiling — on a
real hover-capable device, initHoverFlyout() overrides this inline
with a viewport-derived max-height (2026-09-21, user's own explicit
ask for "as tall as possible, only scrolls once genuinely needed"). */
max-height: 320px;
overflow-y: auto;
padding-right: .25rem;
}
.type-city-flyout__item {
display: block;
text-decoration: none;
color: var(--ink);
font-size: .84rem;
font-weight: 500;
white-space: nowrap;
padding: .3rem .5rem;
border-radius: .5rem;
transition: background .12s ease;
}
.type-city-flyout__item:hover { background: var(--surface-alt); color: var(--brand); }
/* ---------- Hero ---------- */
.hero {
position: relative;
background-image:
linear-gradient(180deg, rgba(0,20,50,.72), rgba(0,10,28,.68)),
url('https://images.unsplash.com/photo-1506905925346-21bda4d32df4?auto=format&fit=crop&w=1920&q=80');
background-size: cover;
background-position: center;
color: #fff;
padding: 45px 20px 30px;
display: flex;
flex-direction: column;
justify-content: center;
align-items: center;
text-align: center;
overflow: hidden;
transition: padding .25s ease;
}
/* Shown once a search/category filter is active, so results sit closer
to the top of the page instead of forcing a long scroll past the hero. */
.hero--compact {
padding: 32px 20px;
}
.hero--compact h1 { font-size: clamp(1.3rem, 2.4vw, 1.9rem); }
.hero--compact .subtitle { font-size: .92rem; }
.hero--compact .ai-search-hint { margin-top: .3rem; }
.hero h1 {
font-size: clamp(1.6rem, 3.2vw, 2.5rem);
font-weight: 700;
letter-spacing: 0.02em;
line-height: 1.15;
text-transform: uppercase;
text-shadow: 0 2px 12px rgba(0,0,0,0.35);
margin: 0;
}
.hero p.subtitle {
color: rgba(255,255,255,0.65);
margin-top: 0.5rem;
margin-bottom: 0;
font-size: .95rem;
font-weight: 400;
line-height: 1.3;
}
.ai-search-wrap {
position: relative;
width: 100%;
max-width: 980px;
margin: 0 auto;
/* .hero is a column flex container; auto cross-axis margins make a flex
item shrink-to-content instead of stretching, which silently defeated
max-width above. Explicit width:100% forces the stretch, then
max-width clamps it (same pattern Bootstrap's .container uses). */
align-self: center;
}
/* Full-panel loading state shown for the whole real-navigation wait
after submitting the hero search (server-side AI query parsing genuinely
takes a couple of seconds) — replaces the old live-as-you-type dropdown,
which read as a cheap suggestions popup rather than a serious tool. */
.search-loading-overlay {
position: absolute;
inset: 0;
display: flex;
flex-direction: column;
align-items: center;
justify-content: center;
gap: .9rem;
background: rgba(255,255,255,.92);
border-radius: var(--radius);
opacity: 0;
visibility: hidden;
transition: opacity .2s ease;
z-index: 25;
}
:root:not([data-theme="light"]) .search-loading-overlay { background: rgba(15,23,42,.88); }
:root[data-theme="dark"] .search-loading-overlay { background: rgba(15,23,42,.88); }
.search-loading-overlay.is-visible { opacity: 1; visibility: visible; }
.search-loading-overlay__spinner { display: flex; gap: .4rem; }
.search-loading-overlay__spinner span {
width: .65rem;
height: .65rem;
border-radius: 50%;
background: var(--brand);
animation: mu-search-bounce 1.1s ease-in-out infinite;
}
.search-loading-overlay__spinner span:nth-child(2) { animation-delay: .15s; }
.search-loading-overlay__spinner span:nth-child(3) { animation-delay: .3s; }
@keyframes mu-search-bounce {
0%, 80%, 100% { transform: scale(.6); opacity: .5; }
40% { transform: scale(1); opacity: 1; }
}
.search-loading-overlay__text {
margin: 0;
font-weight: 700;
font-size: .92rem;
color: var(--ink);
}
@media (prefers-reduced-motion: reduce) {
.search-loading-overlay__spinner span { animation: none; opacity: 1; transform: none; }
}
/* Structured, segmented search panel (Booking.com-style: Location / Type
/ Dates / Search as distinct fields in one bar) instead of a single
pill input — reads as a serious booking tool rather than a chat box. */
.search-panel {
max-width: 980px;
margin: 1.1rem auto 0;
background: var(--surface);
border-radius: var(--radius);
box-shadow: 0 10px 30px rgba(0,0,0,.22);
display: flex;
align-items: stretch;
overflow: hidden;
text-align: left;
}
.search-panel__field {
flex: 1 1 0;
min-width: 0;
padding: .4rem 1.1rem;
display: flex;
flex-direction: column;
justify-content: center;
}
.search-panel__field > label {
font-size: .62rem;
text-transform: uppercase;
letter-spacing: .05em;
font-weight: 700;
color: var(--muted);
margin-bottom: 0;
line-height: 1.3;
}
.search-panel__field > input,
.search-panel__field > select {
border: none;
outline: none;
background: transparent;
padding: 0;
font-size: .93rem;
font-weight: 500;
color: var(--ink);
width: 100%;
appearance: none;
}
/* The field itself has no visible border to move outline:none's focus
indication onto, so the visible focus ring (WCAG 2.4.7) goes on the
parent field wrapper instead when a keyboard user tabs into it. */
.search-panel__field:focus-within {
outline: 2px solid var(--brand);
outline-offset: 2px;
border-radius: var(--radius);
}
/* Both narrowed to direct children (2026-09-26) — these two selectors
used to match ANY input/select nested anywhere inside a field,
including the guests dropdown's own pet checkbox further down the
tree, which silently stripped its native checkbox appearance
(appearance:none + width:100% on a checkbox renders as an invisible
blank box) and uppercased/shrank its text. The date inputs
don't need this rule at all — .search-panel__date-sub input[type="date"]
(below) already duplicates the identical styling for them. */
.search-panel__field > input::placeholder {
color: var(--muted);
font-weight: 400;
opacity: .75;
}
.search-panel__field--type { flex: 0 1 170px; }
.search-panel__field--dates { flex: 0 1 220px; padding-left: 0; padding-right: 0; }
.search-panel__dates-inputs { display: flex; height: 100%; }
.search-panel__date-sub {
flex: 1;
min-width: 0;
position: relative;
padding: .4rem .8rem;
display: flex;
border-radius: var(--radius);
transition: background-color .15s ease;
}
.search-panel__date-sub:hover { background-color: var(--surface-alt); }
.search-panel__date-sub + .search-panel__date-sub { border-left: 1px solid var(--border); }
/* Check-in/check-out as one clickable button, not an editable native
date input sitting directly in the compact bar (2026-09-26 follow-up
— clicking a dd/mm/yyyy segment used to highlight it blue, which read
as broken/fiddly for a field meant to look like a single unit). The
real