.directory-loading{padding:60px 20px;color:var(--muted);text-align:center;font-size:15px}
/* Loads after nova.css/refinements.css (see index.html's <link> order), so
   this plain rule wins over whatever flex-wrap those set for this same
   selector - needed so near-me-status's flex-basis:100% below can actually
   wrap it onto its own line instead of being squeezed into a sliver next
   to List/Grid. */
.directory-controls{flex-wrap:wrap;justify-content:flex-end;gap:10px}
.near-me-status{flex-basis:100%;text-align:right;font-size:12px;color:var(--muted)}
/* A separate, visibly-styled button (not just a 4th option inside a closed
   <select>, which someone can easily never open) so this feature is
   actually discoverable - see directory-controller.js's activateNearMe,
   shared between this button and the dropdown's own "Near Me" option so
   either one leaves things in the same state. */
/* --orange-soft (#fff0e8, nova.css) reads as almost plain white once this
   button sits next to real content rather than isolated in a style guide -
   a dedicated, more visibly-orange "off" fill of its own (not the shared
   variable, which badges/pills/portal elsewhere rely on staying that pale)
   keeps this specific button reading as "Near Me, currently off" rather
   than "a plain button" even before the darker .is-active fill below. */
.near-me-btn{display:inline-flex;align-items:center;gap:6px;border:1px solid var(--orange);background:#ffdfc7;color:#b83d00;padding:10px 14px;font-weight:800;font-size:13px;border-radius:8px;cursor:pointer;white-space:nowrap;transition:background-color .12s ease,color .12s ease,transform .1s ease}
/* hover:hover scoping only, not a bare :hover - on a touchscreen, tapping
   the button simulates :hover with no mouse to ever leave it with, so a
   plain :hover rule here got stuck "on" after any tap. Since this hover
   color is identical to .is-active's, turning Near Me back off looked like
   nothing happened on mobile (still solid orange from the stuck hover)
   even though the class itself was removed correctly, same JS as desktop -
   only real pointer devices (a mouse that actually moves away again) get
   this effect now. */
@media(hover:hover){.near-me-btn:hover{background:#cc4400;color:#fff}}
.near-me-btn:active{transform:scale(.94)}
.near-me-btn.is-active{background:#cc4400;border-color:#cc4400;color:#fff}
/* Geolocation's own prompt/fix can take a beat even once granted, so a
   click needs feedback for that gap - a soft pulse on the button itself
   until activateNearMe's requestUserLocation() resolves (see
   directory-controller.js), rather than the button just sitting still. */
.near-me-btn.is-locating{animation:near-me-pulse 1s ease-in-out infinite}
@keyframes near-me-pulse{0%,100%{transform:scale(1)}50%{transform:scale(1.06)}}
@media(prefers-reduced-motion:reduce){.near-me-btn,.near-me-btn.is-locating{animation:none;transition:none}}
/* city-directory-controller.js's own Near Me control - unlike directory's,
   which sits inline inside .directory-controls, a city page's category-
   filter row has no equivalent control strip to join, so this is its own
   small block directly under the filter chips (margin-top negative by the
   same 5px .category-filter's own -5px top margin already trims, so the
   two don't read as oddly double-spaced apart). */
/* Now also holds the Show map button (city-directory-controller.js/
   neighborhood-controller.js both insert it right after the Near Me
   button) - flex row keeps the two buttons inline side by side, with the
   status line and map container each forced onto their own full-width
   line below. */
.city-near-me-row{display:flex;flex-wrap:wrap;align-items:center;gap:14px;margin:-5px 0 25px}
.city-near-me-row .near-me-status{flex-basis:100%;text-align:left;margin-top:8px}
.city-near-me-row .taxonomy-map{flex-basis:100%}
/* taxonomy-controller.js's own Near Me control, inside .section-head
   (nova.css: display:flex;justify-content:space-between). .section-head
   expects exactly two children (the title on the left, everything else on
   the right) - the result count/button/status used to sit as three
   SEPARATE flex children there, so showing/hiding the status paragraph
   changed how many items justify-content:space-between had to distribute,
   visibly shifting the button sideways every time Near Me was toggled.
   Grouping them into one wrapper restores the expected two-child shape;
   stacking them in a column with align-items:flex-end keeps every line's
   right edge pinned to the same spot regardless of which lines happen to
   be visible, so the button itself never moves. */
.taxonomy-results-meta{display:flex;flex-direction:column;align-items:flex-end;gap:10px;text-align:right}
.taxonomy-results-meta .near-me-status{flex-basis:auto;margin:0}
.taxonomy-action-row{display:flex;flex-wrap:wrap;justify-content:flex-end;align-items:center;gap:14px}
.taxonomy-map{position:relative;width:100%;height:420px;margin:0 0 16px;border-radius:12px;overflow:hidden;border:1px solid var(--line,#e2e6ec)}
/* The actual Google Map renders into this child div, not .taxonomy-map
   itself - city-directory-controller.js/neighborhood-controller.js/
   directory-controller.js rebuild markers (and can hit zero results) every
   time a filter changes, long after the map first exists. Writing the
   "nothing to show" message straight into .taxonomy-map's own innerHTML (as
   taxonomy-controller.js's single-shot version still does, since it never
   needs to rebuild) would destroy the live Google Map's internal DOM in
   those three - this child/overlay split keeps that DOM intact and just
   hides it. */
.taxonomy-map-canvas{width:100%;height:100%}
/* display:flex here unconditionally would override the browser's own
   [hidden]{display:none} default - author CSS always wins over that
   default regardless of the hidden attribute being present, which made
   this overlay show permanently on top of a perfectly good map underneath
   whether or not it actually had zero results. The explicit [hidden] rule
   below (higher specificity, so it applies regardless of source order)
   restores real hide/show behavior. */
.taxonomy-map__empty{position:absolute;inset:0;display:flex;align-items:center;justify-content:center;padding:24px;text-align:center;color:var(--muted,#5b6472);background:#fff}
.taxonomy-map__empty[hidden]{display:none}
/* "Your location" indicator on the taxonomy page map (taxonomy-controller.js's
   UserLocationOverlay) - a solid dot plus an expanding, fading ring behind
   it, the same pulsing-glow convention most map apps use for a live
   location fix. pointer-events:none so it never steals a click meant for a
   business pin or cluster underneath it. */
.taxonomy-map-userdot{position:absolute;width:16px;height:16px;margin:-8px 0 0 -8px;border-radius:50%;background:#1a73e8;border:2px solid #fff;box-shadow:0 0 0 2px rgba(26,115,232,.35);pointer-events:none;z-index:2}
/* Marker InfoWindow content (taxonomy/city-directory/neighborhood/directory
   -controller.js's shared buildMapInfoWindowHtml) - Google's own InfoWindow
   adds its own padding/close button chrome around whatever this renders, so
   this only needs to style the text itself, not the window frame. */
.map-infowindow{min-width:190px;font-family:var(--sans)}
.map-infowindow__photo{display:block;width:100%;height:110px;object-fit:cover;border-radius:6px;margin-bottom:8px}
.map-infowindow strong{display:block;font-size:15px;color:var(--ink);margin-bottom:4px}
.map-infowindow__meta{display:flex;align-items:center;gap:6px;margin:3px 0;font-size:13px;color:var(--muted)}
.map-infowindow__meta svg{flex:0 0 auto;color:var(--muted)}
.map-infowindow__meta a{color:var(--muted);text-decoration:none}
.map-infowindow__meta a:hover{color:var(--blue);text-decoration:underline}
.map-infowindow__link{display:inline-block;margin-top:6px;font-size:13px;font-weight:800;color:var(--blue);text-decoration:none}
.map-infowindow__link:hover{text-decoration:underline}
.taxonomy-map-userdot::before{content:'';position:absolute;inset:-20px;border-radius:50%;background:rgba(26,115,232,.35);animation:taxonomy-userdot-pulse 2s ease-out infinite}
@keyframes taxonomy-userdot-pulse{0%{transform:scale(.3);opacity:.8}70%{opacity:.15}100%{transform:scale(2.8);opacity:0}}
.business-card{overflow:hidden;display:flex;flex-direction:column;height:100%}
.business-media{height:190px;position:relative;background:#eef3f8;overflow:hidden}
.business-media img{width:100%;height:100%;object-fit:cover;display:block}
/* Only the real-photo variant gets inset - the no-photo placeholder (plain
   .business-media, no --image modifier) keeps its existing edge-to-edge
   pattern/label look untouched. object-fit:cover zoom-crops to fill the
   box regardless of what's in the photo - fine for a generic stock image,
   but it was cutting real content out of an uploaded one (a logo banner
   across the top, people at the left/right edges), on both the home page
   and the /directory/ page. contain shows the whole photo, scaled to fit,
   with the box's own background filling any leftover space instead of
   cropping it away - applies everywhere this card shows up. A white
   background here made that leftover space (and the photo's own rounded
   corners) invisible against the white card body behind it - a photo
   narrower than the box, like a logo on its own white background, just
   looked like empty space with no visible frame. The first neutral tried
   (#eef3f8) was still too close to white to read as anything but a flat
   blue-ish block, with no visible contrast against a light photo either.
   A clearly neutral gray plus a border directly on the photo itself keeps
   the rounded corner visible no matter what color the photo happens to
   be, instead of relying on contrast with the mat behind it. */
.business-media--image{position:relative;padding:14px;background:#e4e7eb}
/* Fills the mat gap (the leftover space object-fit:contain leaves on a
   mismatched-aspect photo, see the comment above) with the same photo
   instead of a flat color - blurred and scaled past the box edges so the
   blur's own soft border never shows, sitting behind the real photo via
   z-index. inset:-14px cancels this element's parent's own 14px padding
   so the blur reaches the box's true outer edge, not just its padded
   content area. */
.business-media__backdrop{position:absolute;inset:-14px;background-size:cover;background-position:center;filter:blur(18px) brightness(.85);transform:scale(1.15);z-index:0}
/* /business-category/ and /business-subcategory/ pages only ([data-taxonomy-results]
   is this grid's own container, set by taxonomy-controller.js) - the
   border exists to keep the rounded corner visible against a photo whose
   own color blends into the mat (see the comment on .business-media--image
   img below), but this page's mat is always the same flat gray, which
   already contrasts enough with a white logo on its own - the border just
   reads as a stray thin outline here. */
[data-taxonomy-results] .business-media--image img{border:none}
/* Same /business-category//business-subcategory/ scope - no mat at all on
   this page (padding:0), paired with index.html's own per-image fit()
   script (which already targets [data-taxonomy-results] too) so the photo
   is scaled to close its own gap completely against the FULL box, not
   just the formerly-padded inner area. Together these leave zero space
   above/below (or left/right) the image on this page specifically. */
[data-taxonomy-results] .business-media--image{padding:0}
/* /local/<city>/ page's own "{City} Business Directory" grid only
   ([data-city-grid] is city-shell.js's own container for it) - same thin
   stray-outline issue as the category/subcategory pages above, same fix:
   drop only the border, leave the mat/padding/scale untouched since this
   page wasn't part of that complaint. */
[data-city-grid] .business-media--image img{border:none}
/* Same [data-city-grid] scope - now also asked to close the top/bottom mat
   gap, same treatment as [data-taxonomy-results] above: zero padding here,
   paired with index.html's per-image fit() script (extended to this
   selector too) scaling each photo to close its own remaining gap against
   the full box. */
[data-city-grid] .business-media--image{padding:0}
/* /local/<city>/<neighborhood>/ page's own business strip
   ([data-neighborhood-grid] is neighborhood-controller.js's own container
   for it) - same thin stray-outline-plus-mat-gap complaint as the taxonomy
   and city pages above, same fix: drop the border and zero the padding,
   paired with index.html's per-image fit() script (extended to this
   selector too) so the photo scales to close its own remaining gap
   against the full box. */
[data-neighborhood-grid] .business-media--image img{border:none}
[data-neighborhood-grid] .business-media--image{padding:0}
/* /directory/ page's own result list (list and grid view both nest under
   this same .directory-result-list container) - same thin stray-outline-
   plus-mat-gap complaint as the taxonomy/city/neighborhood grids above,
   somehow never carried over here when those three got fixed. Same
   treatment: drop the border, zero the padding, paired with index.html's
   per-image fit() script (BOX_SELECTOR already includes this container) so
   each photo scales to close its own remaining gap against the full box
   instead of leaving a visible blurred mat frame top/bottom (or left/right). */
.directory-result-list .business-media--image img{border:none}
.directory-result-list .business-media--image{padding:0}
/* /favorites/ page's saved-businesses grid ([data-favorites-grid] is
   router.js's own container for it) - same thin stray-outline-plus-mat-gap
   complaint as the taxonomy/city/neighborhood/directory grids above, same
   fix: drop the border and zero the padding, paired with index.html's
   per-image fit() script (BOX_SELECTOR extended to this selector too) so
   each photo scales to close its own remaining gap against the full box
   instead of leaving a visible blurred mat frame top/bottom (or left/right). */
[data-favorites-grid] .business-media--image img{border:none}
[data-favorites-grid] .business-media--image{padding:0}
/* object-fit:contain only, no transform/scale - any amount of scale-up
   necessarily crops into the photo to close its mat gap (uniform scale
   grows both dimensions together, so closing a vertical gap on a
   wide/banner-shaped image crops its left/right edges, which chopped
   real legible content off a business's logo). A fixed scale was tried
   repeatedly here and kept trading one photo shape's gap for another
   shape's crop - never crop; a visible mat on a mismatched-aspect photo
   is the accepted look instead. */
.business-media--image img{position:relative;z-index:1;border-radius:8px;border:1px solid rgba(11,26,46,.08);object-fit:contain}
/* Home page's own "Worth discovering" large cards only (.business-card--large)
   - this scale was tuned and confirmed directly against the live home page
   earlier and was never part of the directory/category cropping complaint.
   Scoped here instead of on the shared .business-media--image img rule above
   so a directory/category-only change can never silently touch home again. */
.business-card--large .business-media--image img{transform:scale(1.18)}
/* /directory/ page only (list and grid view both nest under this same
   container class). This fixed value is only the pre-JS/no-JS fallback -
   index.html's own early inline script overrides it per-image once each
   photo loads, scaling it by exactly the amount that closes THAT photo's
   own gap (full fill, cropping an extreme shape like a wide banner logo
   if that's what it takes - see that script for the full explanation).
   Scoped here, not on the shared rule above, so this can never again
   silently reach category/subcategory ([data-taxonomy-results]) or home
   (.business-card--large). */
.directory-result-list .business-media--image img{transform:scale(1.16)}
.business-media__featured{position:absolute;z-index:2;top:12px;left:12px;padding:6px 10px;border-radius:999px;background:#157a3b;color:#fff;font-size:12px;font-weight:700;line-height:1}
.business-body{padding:18px!important;display:flex;flex:1;flex-direction:column}
.business-badges{margin:0 0 8px}
.badge--claimed{background:#eef5f2;color:#24483c}
.business-body .eyebrow{font-size:12px;margin-bottom:6px}
.business-body h3{margin:0 0 7px;line-height:1.2}
.business-body h3 a{color:inherit;text-decoration:none}
.business-body h3 a:hover{text-decoration:underline}
.business-card-description{min-height:38px;margin:0 0 12px;color:#53657a;line-height:1.45}
.business-rating-row{display:flex;align-items:center;flex-wrap:wrap;gap:7px;margin:0 0 8px;color:#465568;font-weight:700}
.business-rating-stars{color:#ffad00;letter-spacing:1px;font-size:16px;line-height:1}
.business-rating-score{color:#465568}
.business-status-row{display:flex;align-items:center;flex-wrap:wrap;gap:7px;margin:0 0 10px;font-size:14px;line-height:1.35;font-weight:700}
.business-status{color:#677589}
.business-status--open{color:#157a3b}
.business-status--closed{color:var(--orange)}
.business-close-time{color:#677589;font-weight:600}
.business-card-phone{display:inline-flex;width:max-content;margin:0 0 12px;color:#0054cc;font-size:14px;font-weight:800;text-decoration:none}
.business-card-phone:hover{text-decoration:underline}
.card-actions{margin-top:auto!important;padding-top:12px;border-top:1px solid #e6ebf0;display:flex;align-items:center;justify-content:space-between;gap:10px;flex-wrap:wrap}
.card-actions .text-link{white-space:nowrap}
.card-features{gap:7px;display:flex;align-items:center;flex-wrap:wrap}
.card-feature,.card-feature--directions,.card-feature--website{background:#eef3f8!important;color:#173b67!important;border:1px solid #d8e1ea!important;border-radius:999px!important;text-decoration:none!important}
.card-feature:hover{background:#e2eaf2!important}
/* city-directory-controller.js injects the overflow category chips (past
   visibleCategoryLimit) into this plain, previously unstyled <div> - with
   no display/gap of its own it fell back to default block + inline-button
   flow, packing those chips ~4px apart instead of the main row's 8px flex
   gap. Matching display/gap here makes the expanded "More Categories" row
   look like one continuous row instead of a visibly tighter tail end.
   [hidden] override needed because this selector's own display:flex would
   otherwise beat the plain [hidden]{display:none} UA rule and defeat the
   show/hide toggle (see city-directory-controller.js's panel.hidden). */
.city-category-more{display:flex;gap:8px;flex-wrap:wrap}
.city-category-more[hidden]{display:none}
.filter-option{display:flex;align-items:center;gap:8px;padding:4px 0;cursor:pointer;font-size:13px;color:var(--ink-2)}
.filter-option:hover{color:var(--blue)}
.filter-option input{flex:0 0 auto}
.filter-option span{flex:1}
.filter-option-count{flex:0 0 auto;color:var(--muted);font-size:12px;font-weight:700}
.filter-chip-count{margin-left:2px;font-weight:700;opacity:.65}
.filter-option--extra{display:none!important}
.filter-group.is-expanded>.filter-option--extra,
.filter-subgroup.is-expanded .filter-option--extra{display:flex!important}
.filter-group.is-searching .filter-option--extra{display:flex!important}
.filter-group .filter-option.is-search-hidden{display:none!important}
.filter-more{border:0;background:transparent;padding:8px 0 0;color:#0054cc;font:inherit;font-weight:800;cursor:pointer}
.filter-more:hover{text-decoration:underline}
.filter-more[hidden]{display:none}

/* City filter: a live-search box above the checkbox list, since a flat list
   stopped being browsable once the directory reached dozens of cities. */
.filter-search-wrap{position:relative;margin-bottom:8px}
.filter-search{width:100%;height:38px;margin-bottom:0;padding:0 32px 0 12px;border:1px solid var(--line);border-radius:8px;font:500 14px var(--sans);color:var(--ink)}
.filter-search:focus-visible{outline:2px solid var(--blue);outline-offset:1px}
.filter-search-clear{position:absolute;top:50%;right:6px;transform:translateY(-50%);width:24px;height:24px;padding:0;border:0;border-radius:50%;background:transparent;color:var(--muted);font-size:18px;line-height:1;cursor:pointer;display:flex;align-items:center;justify-content:center}
.filter-search-clear:hover{background:var(--paper);color:var(--ink)}
.filter-search-clear[hidden]{display:none}
.filter-empty{margin:6px 0 0;color:var(--muted);font-size:13px}
.filter-empty[hidden]{display:none}

/* Category tree: a top-level category row with an optional expand toggle
   revealing its subcategories (e.g. cuisines under Restaurants & Dining)
   indented beneath - collapsed by default so N categories still reads as N
   rows rather than every subcategory dumped at once. */
.filter-tree-row{border-bottom:1px solid var(--line)}
.filter-tree-row:last-child{border-bottom:0}
.filter-tree-head{display:flex;align-items:center;gap:4px}
.filter-tree-head .filter-option{flex:1;padding:6px 0}
.filter-tree-toggle,.filter-tree-spacer{flex:0 0 auto;width:22px;height:22px}
.filter-tree-toggle{display:flex;align-items:center;justify-content:center;border:0;background:transparent;color:var(--muted);cursor:pointer;border-radius:5px;transition:transform .15s ease,background-color .15s ease}
.filter-tree-toggle:hover,.filter-tree-toggle:focus-visible{background:#f1f5f9;color:var(--ink)}
.filter-tree-toggle:before{content:'';display:block;width:7px;height:7px;border-right:2px solid currentColor;border-bottom:2px solid currentColor;transform:rotate(-45deg);margin-left:-2px}
.filter-tree-row.is-open>.filter-tree-head .filter-tree-toggle{transform:rotate(90deg)}
.filter-subgroup{display:none;margin:0 0 8px 26px}
.filter-tree-row.is-open .filter-subgroup{display:block}
.filter-option--sub{font-size:12px;padding:3px 0}
/* Bounded, independently-scrolling box for the category rows themselves -
   with 30+ top-level categories in the taxonomy, letting this list grow
   unbounded pushed every filter group below it (City included) far down
   the sidebar, effectively hiding them behind a full-page scroll. */
.filter-tree-scroll{max-height:320px;overflow-y:auto;padding-right:6px;margin-right:-6px;scrollbar-width:thin}
.filter-tree-scroll::-webkit-scrollbar{width:6px}
.filter-tree-scroll::-webkit-scrollbar-thumb{background:#cbd5e1;border-radius:999px}
.filter-tree-scroll::-webkit-scrollbar-track{background:transparent}
.directory-no-results{padding:32px;border:1px solid #d8e1ea;border-radius:14px;background:#fff}
.directory-no-results h2,.directory-no-results h3{margin:0 0 10px;color:#173b67;font-size:26px}
.directory-no-results p{max-width:720px;margin:0 0 10px;color:#53657a;line-height:1.55}
.directory-no-results__hint{font-weight:600;color:#3f5167}
.directory-no-results p.directory-no-results__suggestion{display:flex;align-items:center;gap:12px;flex-wrap:wrap;max-width:none;margin:14px 0;padding:14px 16px;border-radius:10px;background:#eef4ff;border:1px solid #cfe0fb;color:#173b67}
.directory-no-results__suggestion strong{color:#0b1a2e}
.directory-no-results__actions{display:flex;gap:10px;flex-wrap:wrap;margin-top:20px}
.directory-no-results__primary{background:#0054cc!important;border-color:#0054cc!important;color:#fff!important}
.directory-search button{cursor:pointer;transition:background-color .15s ease,border-color .15s ease,transform .08s ease,box-shadow .15s ease}
.directory-search button:hover{background:#003f9e!important;border-color:#003f9e!important;box-shadow:0 5px 14px rgba(0,84,204,.22)}
.directory-search button:active,.directory-search button.is-searching{background:#002f78!important;border-color:#002f78!important;transform:translateY(1px);box-shadow:none}
.directory-search button:focus-visible{outline:3px solid rgba(0,84,204,.28);outline-offset:3px}
.directory-result-list.is-grid{grid-template-columns:repeat(3,minmax(0,1fr))!important}
@media(max-width:1100px){.directory-result-list.is-grid{grid-template-columns:repeat(2,minmax(0,1fr))!important}}
/* This switches .directory-controls from flex to a 2-column grid at mobile
   widths, but originally only gave explicit grid placement to select/
   .view-toggle - .near-me-btn and .near-me-status (both still just flex
   items as far as this grid's auto-placement algorithm is concerned) fell
   into whatever cells grid auto-flow happened to leave open, landing
   .near-me-status directly beside the "List" toggle button instead of on
   its own line. Giving both an explicit full-width grid-column puts every
   control on its own row, with the two .view-toggle buttons naturally
   auto-placed side by side in the remaining row. */
@media(max-width:700px){.directory-controls{display:grid!important;grid-template-columns:repeat(2,minmax(0,1fr));width:100%}.directory-controls .near-me-btn{grid-column:1/-1}.directory-controls select{grid-column:1/-1;width:100%}.directory-controls .near-me-status{grid-column:1/-1;text-align:left;flex-basis:auto}.directory-controls .view-toggle{width:100%}.directory-result-list.is-grid{grid-template-columns:1fr!important}.directory-no-results{padding:24px}.directory-no-results__actions{align-items:stretch;flex-direction:column}}
@media(max-width:620px){.business-media{height:170px}.business-body{padding:15px!important}}
