/**
 * Будинок Затишку — global chrome. See mebelvdom-redesign-spec.md §3.
 * Utility bar, main header, category nav, footer, mobile bottom nav.
 */

* { box-sizing: border-box; }
/* Cassiopeia's own template.min.css sets body{background:#fff} and loads
   AFTER tokens.css in the <head> (same specificity, later wins), silently
   overriding tokens.css's body{background:var(--c-bg)} — the page canvas
   rendered pure white instead of the intended warm cream. chrome.css loads
   after Cassiopeia's stylesheet, so restating it here wins the cascade
   without touching the core file or reaching for !important. */
body { margin: 0; background: var(--c-bg); overflow-x: hidden; }

:root {
  /* The site's two page widths, named once. --bz-container-wide is the real
     content grid (category, product, home, catalog directory, cart);
     --bz-container-narrow is the reading column articles/404 keep.
     Anything that has to LINE UP with page content sets --bz-container-max
     to one of these rather than restating the number — the global chrome
     and the breadcrumb trail both do.
     Owner, 2026-09-27 (design file "6 Cart.dc.html"): cart moved from the
     narrow group to wide, both the outer grid track (templates/budynok/
     index.php's $isWidePage) and its own content width (cart.css's
     #cart-view/.vm-cart-header-container) — it was squeezed into the
     ~1272px "main" grid column while the header/breadcrumb above it
     already spanned the full site width. */
  --bz-container-narrow: 1280px;
  --bz-container-wide: 2400px;

  /* The page's side gutter — the breathing room between the content and the
     viewport edge, on EVERY band that touches that edge. Owner, 2026-09-01:
     a flat 16px read as "too edgy". This clamp is not a new number: it is
     the one the homepage hero has always used for its own copy inset
     (home.css .bz-vhero__copy), i.e. the design's own answer to this
     question, now shared by the whole site instead of that one panel.
     20px on a phone, ~43px at 1280, 46px from ~1353px up.
     --space-4 stays what it was: component padding INSIDE a card or panel
     is a different measurement and must not follow this. */
  --bz-gutter: clamp(20px, 3.4vw, 46px);
}

.bz-container {
  max-width: var(--bz-container-max, var(--bz-container-narrow));
  margin: 0 auto;
  padding: 0 var(--bz-gutter);
}

/* Category/product/home pages get more room so the product grid can show
   more columns as the viewport grows, per owner request — near-edge-to-edge
   on all but ultra-wide monitors. */
.bz-container--wide {
  --bz-container-max: var(--bz-container-wide);
}

/* The global chrome rides the WIDE grid on every page, never the narrow one.
   Two reasons, and the second is why it is not conditional on the page:

   1. The logo's left edge has to land on the same gutter as the content it
      sits above — the product cards, the filter panel, the product layout,
      the breadcrumb trail, all of which are .bz-container--wide. Measured
      2026-09-01 on a 1920px viewport before this rule: page content began at
      x=16, the logo at x=329, and the header's own right-hand actions
      stopped ~380px short of the content's right edge.
   2. A header whose width followed the page would slide the logo sideways
      every time you moved between a category page and an article. The frame
      around the site stays put; only the page column inside it changes. */
.bz-utility > .bz-container,
.bz-header > .bz-container,
.bz-megacatalog__header > .bz-container,
.bz-footer > .bz-container,
.bz-footer__bottom > .bz-container {
  --bz-container-max: var(--bz-container-wide);
}

/* Cassiopeia's own .grid-child has its own max-width (its "xxl" breakpoint
   cap) independent of the .site-grid column constraint that .full-width
   already escapes — override both so wide pages actually reach 2400px. */
.grid-child.full-width {
  max-width: none;
}

/* Cassiopeia also force-pins .container-component's grid-column to the
   4-track "main" area whenever there's no sidebar (see _css-grid.scss:
   "body:not(.has-sidebar-left) .site-grid .container-component { grid-
   column-start: main-start }") — that selector is MORE specific than the
   generic ".full-width" rule, so it wins even with .full-width applied.
   Match/beat that specificity explicitly so wide pages actually span the
   full grid instead of silently staying capped at the main area's width. */
body:not(.has-sidebar-left) .site-grid .container-component.full-width,
body:not(.has-sidebar-right) .site-grid .container-component.full-width {
  grid-column: full-start / full-end;
}

/* ---------- §3.1 Utility top bar ---------- */

.bz-utility {
  background: var(--c-coffee);
  color: var(--c-card);
  font-size: 12px;
}
.bz-utility .bz-container {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-4);
  padding-top: 8px;
  padding-bottom: 8px;
}
.bz-utility__links {
  display: flex;
  gap: var(--space-4);
  list-style: none;
  margin: 0;
  padding: 0;
}
.bz-utility__links a {
  color: var(--c-card);
  opacity: .85;
  text-decoration: none;
}
.bz-utility__links a:hover { opacity: 1; text-decoration: underline; }
.bz-utility__right {
  display: flex;
  align-items: center;
  gap: var(--space-4);
  white-space: nowrap;
}
/* Language switcher — a segmented pill, as the design draws it: the active
   language is a solid chip inside a hairline capsule, the other sits flat
   beside it. Replaces the old "УКР / РУС" underlined-link pair (owner,
   2026-07-29), which read as two links rather than one control and gave no
   affordance that the two are alternatives.

   This base is the dark-bar skin (utility bar, mobile drawer). The landing
   state over the hero video has its own glass variant further down — search
   .bz-header__lang. No container-level opacity here: it would dim the solid
   chip along with everything else, which is what makes the control readable
   at 11px on the coffee bar. */
.bz-lang-toggle {
  display: inline-flex;
  align-items: center;
  border: 1px solid var(--c-stock);
  border-radius: var(--radius-pill);
  overflow: hidden;
  line-height: 1;
  color: var(--c-card);
  font-size: 11px;
}
/* The language you are on is a plain <span class="is-active"> — a page never
   links to itself (SEO audit 2026-10-09) — so the chip is styled by class, and
   the base rule below covers both the link and that span. */
.bz-lang-toggle a,
.bz-lang-toggle .is-active {
  display: inline-flex;
  align-items: center;
  padding: 3px 10px;
  background: none;
  border: none;
  color: inherit;
  font: inherit;
  font-size: inherit;
  font-weight: 700;
  cursor: pointer;
  opacity: .7;
  text-decoration: none;
  transition: background .2s ease, color .2s ease, opacity .2s ease;
}
.bz-lang-toggle a:hover { opacity: 1; text-decoration: none; }
.bz-lang-toggle .is-active {
  background: var(--c-card);
  color: var(--c-coffee);
  font-weight: 800;
  opacity: 1;
  text-decoration: none;
}

.bz-utility__mobile { display: none; }

/* ---------- §3.2 Main header ---------- */

.bz-header {
  background: var(--c-card);
  border-bottom: 1px solid var(--c-line);
  position: sticky;
  top: 0;
  z-index: 100;
}
.bz-header .bz-container {
  display: flex;
  align-items: center;
  gap: var(--space-5);
  padding-top: var(--space-3);
  padding-bottom: var(--space-3);
}
.bz-logo-placeholder {
  font-family: var(--font-heading);
  font-weight: 600;
  font-size: 20px;
  color: var(--c-coffee);
  text-decoration: none;
  white-space: nowrap;
}
.brand-logo { display: inline-flex; align-items: center; flex-shrink: 0; }
.brand-logo img { display: block; height: 42px; width: auto; }
@media (max-width: 599px) {
  .brand-logo img { height: 32px; }
}
.bz-header__catalog-btn {
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  background: var(--c-coffee);
  color: var(--c-card);
  border: none;
  border-radius: var(--radius-pill);
  padding: 10px 20px;
  font-weight: 700;
  font-size: 14px;
  cursor: pointer;
  white-space: nowrap;
  flex-shrink: 0;
}
.bz-header__catalog-btn:hover { opacity: .9; }
.bz-header__catalog-btn .bz-icon { width: 16px; height: 16px; flex-shrink: 0; }
.bz-header__search {
  flex: 1;
  min-width: 0;
  position: relative;
}
.bz-header__search input {
  width: 100%;
  border: 1px solid var(--c-line);
  border-radius: var(--radius-pill);
  padding: 10px 46px 10px 18px;
  font-family: var(--font-body);
  font-size: 14px;
  background: var(--c-bg);
  color: var(--c-text);
  /* Safety net for the narrowest part of the landing hero's own 900-
     1200px band, where even chrome.js's fully-collapsed last resort
     still can't fit the (owner-lengthened, 2026-09-04) short placeholder
     — there's no further step to fall back to, so this at least turns a
     jarring mid-word clip into an honest "…" rather than pretending the
     text just ends there. */
  overflow: hidden;
  text-overflow: ellipsis;
}
.bz-header__search input::placeholder { color: var(--c-muted); }
.bz-header__actions {
  display: flex;
  align-items: center;
  gap: var(--space-4);
  flex-shrink: 0;
}
/* The phone numbers are one group, not loose siblings of ♡ and the cart:
   they share a single ✆, a single ▾, and -- when the contacts panel is
   opened from inside here -- they are what that panel hangs below. Hence
   position: relative; components.css positions the panel against it. The
   gap is tighter than .bz-header__actions' own so the numbers read as one
   block with a little air, not as separate controls. */
.bz-header__phones {
  position: relative;
  display: inline-flex;
  align-items: center;
  gap: var(--space-3);
}
/* Sized and coloured like the caret that used to sit inside the first
   button, just promoted to the group's own trailing control. */
.bz-header__phones-caret {
  display: inline-flex;
  align-items: center;
  background: none;
  border: none;
  padding: 0;
  cursor: pointer;
  color: var(--c-coffee);
  font-size: 12px;
  line-height: 1;
}
.bz-header__phone {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  background: none;
  border: none;
  font-family: var(--font-body);
  font-weight: 700;
  font-size: 14px;
  color: var(--c-coffee);
  cursor: pointer;
  white-space: nowrap;
}
.bz-header__phone .bz-icon { width: 15px; height: 15px; flex-shrink: 0; }
/* Icon + label, stacked — matches the design's header action pattern
   (frame 4a: "♡ Обране" / "▣ Кошик" both render icon-on-top, label
   underneath, badge pinned to the icon's corner). */
.bz-header__icon-btn {
  display: inline-flex;
  flex-direction: column;
  align-items: center;
  gap: 2px;
  padding: 2px 4px;
  border-radius: var(--radius-sm);
  border: none;
  background: none;
  color: var(--c-text);
  font-family: var(--font-body);
  font-size: 11px;
  font-weight: 600;
  line-height: 1.2;
  cursor: pointer;
  text-decoration: none;
}
.bz-header__icon-btn:hover { background: var(--c-pillow); }
.bz-header__icon-glyph { position: relative; color: var(--c-coffee); }
.bz-header__icon-glyph .bz-icon { width: 16px; height: 16px; }
.bz-header__badge {
  position: absolute;
  top: -5px;
  right: -8px;
  min-width: 16px;
  height: 16px;
  padding: 0 4px;
  border-radius: var(--radius-pill);
  background: var(--c-ginger);
  color: #fff;
  font-size: 9px;
  font-weight: 700;
  line-height: 16px;
  text-align: center;
}

/* Mobile-only replacement for the full phone number (owner request,
   2026-09-04): four icon-only buttons -- phone / search / favourites /
   cart -- shown below 900px instead of .bz-header__phones (see the
   @media (max-width: 899px) block further down, which hides one cluster
   and shows the other; never both). Material Design's own "icon button"
   shape -- a flat 40px circle, outlined-stroke glyph, a tinted state
   layer on hover/press instead of a shadow -- no ripple animation since
   that needs JS and a flat tint reads the same at a glance. */
.bz-header__mobile-actions {
  display: none;
  align-items: center;
  gap: 2px;
}
.bz-header__mobile-btn {
  position: relative;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 40px;
  height: 40px;
  border-radius: 50%;
  border: none;
  background: none;
  color: var(--c-coffee);
  cursor: pointer;
  text-decoration: none;
  -webkit-tap-highlight-color: transparent;
  transition: background-color .15s ease;
}
.bz-header__mobile-btn .bz-icon { width: 22px; height: 22px; }
.bz-header__mobile-btn:hover,
.bz-header__mobile-btn:focus-visible { background: var(--c-pillow); }
.bz-header__mobile-btn:active { background: var(--c-line); }
.bz-header__mobile-btn[hidden] { display: none; }
/* The overflow menu itself (owner request, 2026-09-04): logo keeps its
   natural size below 900px instead of shrinking to make room (see
   .brand-logo in the @media (max-width: 899px) block), so search/cart
   stay directly on the row and phone -- the one action that can afford
   an extra tap -- collapses behind this "⋯" button instead, the common
   mobile "show more" pattern. Positioned against .bz-header__more (a
   plain wrapper), not the button itself, since the button already needs
   its own position: relative for nothing in particular here but shares
   .bz-header__mobile-btn with the cart button, which does. */
.bz-header__more { position: relative; display: inline-flex; }
.bz-header__more-menu {
  position: absolute;
  top: calc(100% + 6px);
  right: 0;
  min-width: 180px;
  background: var(--c-card);
  border: 1px solid var(--c-line);
  border-radius: var(--radius-md);
  box-shadow: 0 8px 24px rgba(46, 32, 22, .16);
  padding: 4px;
  z-index: 105;
}
.bz-header__more-menu[hidden] { display: none; }
.bz-header__more-menu-item {
  display: flex;
  align-items: center;
  gap: 10px;
  width: 100%;
  padding: 10px 12px;
  border: none;
  background: none;
  border-radius: var(--radius-sm);
  font-family: var(--font-body);
  font-size: 14px;
  font-weight: 600;
  color: var(--c-text);
  cursor: pointer;
  text-align: left;
}
.bz-header__more-menu-item:hover { background: var(--c-pillow); }
.bz-header__more-menu-item[hidden] { display: none; }
.bz-header__more-menu-item .bz-icon { width: 18px; height: 18px; color: var(--c-coffee); flex-shrink: 0; }
/* The cart badge (module "cart-icon-header-mobile") lands here via the
   shared .bz-cart-icon--mobile rules further down -- same absolute
   overlay + pointer-events: none trick the bottom nav's cart entry
   uses, positioned against this button's own position: relative. */

/* ---------- §3.3 Category nav bar (desktop) ---------- */

.bz-catnav {
  background: var(--c-bg);
  border-bottom: 1px solid var(--c-line);
}
.bz-catnav__list {
  display: flex;
  gap: var(--space-5);
  list-style: none;
  /* No .bz-container wrapper in the markup — the <ul> is the row — so it
     carries the wide cap itself and centres like one. Without this it is
     full-bleed and its first item walks off the gutter every other chrome
     element stops at, once the viewport clears 2400px. */
  max-width: var(--bz-container-wide);
  margin: 0 auto;
  padding: 10px var(--bz-gutter);
  overflow-x: auto;
}
.bz-catnav__list a,
.bz-catnav__list button {
  color: var(--c-text);
  text-decoration: none;
  font-size: 14px;
  font-weight: 600;
  white-space: nowrap;
}
/* A root category with subcategories has no page of its own worth linking
   to (see BUSINESS-RULES.md "Category listing" / "Mega-catalog") — its
   nav entry is a <button> that opens the mega-catalog straight to that
   category's panel instead of navigating to an empty listing. Reset the
   button chrome so it's visually identical to the plain <a> entries
   beside it (a leaf root category, e.g. Матраци, still IS a real link). */
.bz-catnav__list button {
  background: none;
  border: none;
  padding: 0;
  font-family: inherit;
  cursor: pointer;
}
.bz-catnav__list a:hover,
.bz-catnav__list button:hover { color: var(--c-ginger); }

/* Room entries pair an icon with the label. The icon comes from the menu
   item's own "Link CSS Style" field (bz-room--NAME -> an inline SVG symbol),
   so adding a room in the menu manager is enough to get one — and a room
   with no icon set simply renders as the label, with no gap left behind. */
.bz-catnav__room {
  display: inline-flex;
  align-items: center;
  gap: 7px;
}
.bz-catnav__icon {
  width: 18px;
  height: 18px;
  flex: 0 0 auto;
  color: var(--c-ginger);
  transition: color .15s ease;
}
img.bz-catnav__icon {
  object-fit: contain;
  border-radius: 3px;
}
.bz-catnav__list a:hover .bz-catnav__icon,
.bz-catnav__list button:hover .bz-catnav__icon { color: inherit; }

/* «Акції %» is a room-menu item like any other; it keeps the sale accent. */
.bz-catnav__list .bz-room--sale { color: var(--c-sale); }
.bz-catnav__list .bz-room--sale .bz-catnav__icon { color: currentColor; }

/* ---------- §3.5 Footer ---------- */

.bz-footer {
  /* Ground and text ramp come straight from design frames 2a/2d: the
     darkest brown in the palette (--c-text), NOT --c-coffee, which is what
     the rest of the dark chrome sits on. The two values below have no
     token because they exist nowhere else on the site — a warm-grey link
     colour quieter than --c-pillow, and a greyer hairline than the
     pillow-tinted one the header uses. They stay local to the footer
     rather than being promoted into tokens.css for one consumer. */
  --bz-footer-link: #C8BFAE;
  --bz-footer-rule: #4A463E;
  background: var(--c-text);
  color: var(--bz-footer-link);
  font-size: 14px;
}
.bz-footer .bz-container {
  display: grid;
  /* Capped tracks + space-between, not four 1fr. On the wide grid 1fr
     tracks stretch to ~466px each while what sits in them is a short list,
     so the columns drift apart and the last one text stops ~300px short of
     the right gutter that the header actions above it end on. Capping the
     track and distributing the slack pins column one to the left gutter and
     column four to the right — the same shape as the header row, and the
     column widths stay close to what they were on the narrow grid.
     minmax(0, ...) so the tracks still shrink on a tight row rather than
     overflowing; below 900px the two-column override takes over and the
     tracks fill the row, which makes space-between a no-op there. */
  grid-template-columns: minmax(0, 340px) repeat(3, minmax(0, 280px));
  justify-content: space-between;
  gap: var(--space-5);
  padding-top: var(--space-6);
  padding-bottom: var(--space-6);
}
/* Design 2a sets the column headings in the BODY face at 800, uppercase
   and letterspaced — not Lora. Lora stays on the brand name alone, which
   is the one thing down here that should read as a wordmark. */
/* :root prefix: productdetails.css re-sizes `:root h3` (0,1,1) and loads after this file. line-height 22px is what the
   old h4 level gave these headings. */
:root .bz-footer h3 {
  font-family: var(--font-body);
  line-height: 22px;
  color: var(--c-card);
  font-size: 12px;
  font-weight: 800;
  letter-spacing: .06em;
  text-transform: uppercase;
  margin: 0 0 var(--space-3);
}

/* ---- Column one: brand block ---- */
.bz-footer__brand {
  display: flex;
  flex-direction: column;
  gap: var(--space-2);
}
.bz-footer__name {
  font-family: var(--font-heading);
  font-weight: 600;
  font-size: 19px;
  line-height: 1.2;
  color: var(--c-card);
}
/* The slogan is the site's own line, kept through the redesign; the mockup
   only had the descriptive sentence below it. It sits one step brighter
   than that sentence so the order reads slogan-then-detail. */
.bz-footer__slogan {
  margin: 0;
  font-size: 13px;
  line-height: 1.5;
  color: var(--bz-footer-link);
}
.bz-footer__about {
  margin: 0;
  font-size: 12px;
  line-height: 1.6;
  color: var(--c-muted-on-dark);
}
.bz-footer .bz-footer__about a { text-decoration: underline; }
.bz-footer a.bz-footer__phone {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  align-self: flex-start;
  margin-top: var(--space-2);
  font-size: 17px;
  font-weight: 800;
  color: var(--c-card);
  opacity: 1;
}
.bz-footer__phone .bz-icon { width: 16px; height: 16px; flex-shrink: 0; }
.bz-footer__hours {
  margin: 0;
  font-size: 11.5px;
  line-height: 1.5;
  color: var(--c-muted-on-dark);
}
/* Opens the same "Усі контакти" popup as the header's phone button — the
   footer has no social row of its own precisely because the messengers
   live in there (design 2a: "усі контакти й месенджери — у попапі"). */
.bz-footer__contacts {
  padding: 0;
  border: 0;
  background: none;
  font: inherit;
  color: var(--bz-footer-link);
  text-decoration: underline;
  text-underline-offset: 2px;
  cursor: pointer;
}
.bz-footer__contacts:hover { color: var(--c-card); }
.bz-footer ul { list-style: none; margin: 0; padding: 0; }
.bz-footer li { margin-bottom: var(--space-2); }
.bz-footer li { font-size: 12.5px; }
.bz-footer a { color: var(--bz-footer-link); text-decoration: none; opacity: .9; }
.bz-footer a:hover { opacity: 1; color: var(--c-card); text-decoration: underline; }
/* The mobile home of what the utility bar used to carry at the top of the
   page — delivery line, hours, УКР/РУС. Shown below 900px on EVERY page.
   It was scoped to the catalog directory page alone (body.layout-katalog)
   for a day, and that was the wrong call: "the catalog page" reads just as
   naturally as a category listing, where the strip then wasn't there at
   all, and it was reported twice as a missing footer. Since this is also
   the only place the language toggle lives on mobile, page-scoping it buys
   nothing and costs the toggle on every page it excludes. See the
   .bz-utility { display: none } rule in the responsive section. */
.bz-footer__utility { display: none; }
@media (max-width: 899px) {
  .bz-footer__utility {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: center;
    gap: var(--space-2) var(--space-4);
    border-top: 1px solid var(--bz-footer-rule);
    padding: var(--space-3) var(--bz-gutter);
    font-size: 12px;
  }
  /* The toggle's own skin is the dark-bar one (.bz-lang-toggle in this
     file) — the footer is the same coffee ground it was designed against,
     so it needs nothing extra here beyond not inheriting the footer link
     styling, which would repaint both halves pillow and underline them. */
  .bz-footer__utility .bz-lang-toggle a { color: inherit; opacity: .7; }
  .bz-footer__utility .bz-lang-toggle a:hover { opacity: 1; text-decoration: none; }
  .bz-footer__utility .bz-lang-toggle .is-active { color: var(--c-coffee); opacity: 1; }
}

/* Design 2a splits the bottom bar: copyright left, payment methods right,
   both on the same column grid as the four blocks above — hence the inner
   .bz-container rather than a --bz-gutter padding on the band itself,
   which would have let the text drift to the viewport edge on the wide
   grid while the columns above stayed put. */
.bz-footer__bottom {
  border-top: 1px solid var(--bz-footer-rule);
  padding: var(--space-4) 0;
  font-size: 11px;
  color: var(--c-muted-on-dark);
}
.bz-footer__bottom > .bz-container {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-2) var(--space-4);
}

/* ---------- §3.4 Mobile bottom nav ---------- */

.bz-bottomnav {
  display: none;
  position: fixed;
  bottom: 0;
  left: 0;
  right: 0;
  background: var(--c-card);
  border-top: 1px solid var(--c-line);
  z-index: 200;
  padding-bottom: env(safe-area-inset-bottom, 0);
  /* For the landing's hold-back-then-slide-in — see the
     body.bz-home-hero:not(.is-hero-stuck) rule in the responsive
     section below. Inert everywhere else (nothing else moves it). */
  transition: transform .35s ease, opacity .35s ease;
}
.bz-bottomnav__list {
  display: flex;
  list-style: none;
  margin: 0;
  padding: 0;
}
.bz-bottomnav__list li { flex: 1; }
.bz-bottomnav__list a,
.bz-bottomnav__list button {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 2px;
  width: 100%;
  border: none;
  background: none;
  padding: 8px 4px 6px;
  color: var(--c-muted);
  font-size: 10px;
  font-family: var(--font-body);
  text-decoration: none;
  cursor: pointer;
  position: relative;
}
.bz-bottomnav__list a.is-active,
.bz-bottomnav__list button.is-active { color: var(--c-coffee); }
.bz-bottomnav__icon { font-size: 18px; }
.bz-bottomnav__icon .bz-icon { width: 18px; height: 18px; }
.bz-bottomnav__badge {
  position: absolute;
  top: 2px;
  right: 22%;
  min-width: 14px;
  height: 14px;
  border-radius: var(--radius-pill);
  background: var(--c-ginger);
  color: #fff;
  font-size: 9px;
  font-weight: 700;
  line-height: 14px;
  text-align: center;
}

/* ---------- Responsive ---------- */

@media (max-width: 899px) {
  /* The utility bar is gone from the top of the page on phones (owner,
     2026-07-29) — the delivery line, the hours and the УКР/РУС toggle it
     carried are worth less than the vertical space at this width. They
     reappear at the bottom of the catalog directory page instead; see
     .bz-footer__utility below, which is the only place they now live on
     mobile. Note this also zeroes --bz-utility-h (home.js and chrome.js
     both measure offsetHeight), so the fixed header stacks from 0. */
  .bz-utility { display: none; }
  .bz-utility__links,
  .bz-catnav { display: none; }
  .bz-utility__mobile { display: inline; }
  .bz-header__catalog-btn span.bz-label { display: none; }
  /* Label-less here, so the button is just the menu icon — it leads the
     header row at this width instead of trailing the logo, sitting in the
     top-left corner flush with .bz-container's own gutter (the same left
     edge every other mobile element lines up on). First in source order
     would need markup surgery; order is enough, the container is flex. */
  .bz-header__catalog-btn {
    order: -1;
    background: none;
    color: var(--c-coffee);
    padding: 0;
    width: 40px;
    height: 40px;
    justify-content: center;
    border-radius: 50%;
    /* Optical edge alignment (owner report, 2026-09-04: "a big gap from
       the left edge to the menu icon" once the button lost its filled
       background -- a solid pill reads as flush with the edge on its
       own visual weight; a bare icon centred in the same 40px tap
       target does not, since the container's own gutter PLUS this
       button's centring padding both apply before any pixel of the icon
       shows). The tap target stays the full 40px (padding: 0 above only
       zeroed the button's OWN inset, not the icon's centring within it)
       -- this just pulls the whole circle left so the icon's leading
       edge lines up with where the gutter alone would put it, the same
       trick Material's own icon buttons use for a leading position. */
    margin-left: -8px;
  }
  .bz-header__catalog-btn:hover { opacity: 1; background: var(--c-pillow); }
  .bz-header__catalog-btn:active { background: var(--c-line); }
  .bz-header__catalog-btn .bz-icon { width: 22px; height: 22px; }
  .bz-bottomnav { display: block; }
  /* Reserve the fixed bottom nav's height, or whatever ends the page sits
     behind it — which is what was swallowing the footer's last rows.
     A flat 56px was wrong twice over: the bar actually measures 59px, and
     it carries padding-bottom: env(safe-area-inset-bottom), so on a phone
     with a home indicator it is another ~34px taller than any number a
     stylesheet can name. chrome.js measures the real thing (inset
     included) into --bz-bottomnav-h; the fallback here only has to hold
     until that runs, so it spells the same sum out longhand.

     The +12px is deliberate breathing room, not slop. Reserving the bar's
     exact height leaves the page's last line resting flush on its top edge
     — measured at 0.2px clearance — which reads as "there is more down
     there, cut off" even though nothing is. */
  body { padding-bottom: calc(var(--bz-bottomnav-h, calc(59px + env(safe-area-inset-bottom, 0px))) + 12px); }

  /* The landing holds its bottom nav back: the hero fills the screen and
     carries its own CTAs, so the bar would just sit on the footage before
     the visitor has engaged with anything. The body padding it reserves is
     dropped for the same stretch, so the hero gets that space back (see
     .bz-vhero__copy's padding-bottom in home.css, which is sized against
     this) and nothing shifts underneath.

     It is released the instant the settle COMMITS to travelling past the
     hero — mid-gesture, before the scroll lands — not on arrival, which
     read as a lag. is-hero-stuck is what marks that commit now (home.js
     puts the cream bar in place for the whole downward trip rather than
     sliding it out and back). is-hero-gone is still listed because it is
     what marks the opposite trip, back up to the video, where the nav
     should likewise stay up until the video is actually reached.

     Landing only; every other page still shows the nav from first paint. */
  body.bz-home-hero:not(.is-hero-stuck):not(.is-hero-gone) { padding-bottom: 0; }
  body.bz-home-hero:not(.is-hero-stuck):not(.is-hero-gone) .bz-bottomnav {
    transform: translateY(100%);
    opacity: 0;
    pointer-events: none;
  }
  /* ...except with the mega-catalog overlay open over the landing: it's
     the only way to reach Пошук/Кошик/Обране from in there (the overlay
     covers the transparent hero header too), so the nav has to show
     regardless of hero state. megacatalog.js adds/removes this class in
     lockstep with the overlay's own open()/close(). Same specificity
     "shape" as the hiding rule above (plus the new class), so it wins on
     its own merits rather than relying on source order. */
  body.bz-home-hero.bz-megacatalog-open:not(.is-hero-stuck):not(.is-hero-gone) .bz-bottomnav {
    transform: translateY(0);
    opacity: 1;
    pointer-events: auto;
  }

  .bz-footer .bz-container { grid-template-columns: 1fr 1fr; }
  /* Design 2d leads with the brand block full-width and drops the link
     columns underneath it; below 600px the two ends of the bottom bar
     stop being two ends and centre instead. */
  .bz-footer__brand { grid-column: 1 / -1; }
  .bz-footer__name { font-size: 16px; }
}

@media (max-width: 599px) {
  .bz-footer__bottom > .bz-container {
    justify-content: center;
    text-align: center;
  }
}

@media (max-width: 899px) {
  /* Mobile header layout, reworked (owner request, 2026-09-04): row 1 is
     hamburger + logo (fixed size, does NOT shrink -- .brand-logo keeps
     its base-rule flex-shrink: 0 and fixed img height, no override here
     any more) + search/cart/"⋯more" pushed flush right by
     margin-left: auto on .bz-header__actions below (the actual flex
     child of this row -- .bz-header__mobile-actions is nested another
     level inside it and had no spare space of its own to push into, see
     that rule's own comment). Search
     becomes its own full-width row underneath rather than squeezed into
     row 1. Favourites stays out of this row entirely -- the bottom nav
     already has its own "Обране" entry and cart badge. */
  .bz-header .bz-container { flex-wrap: wrap; gap: var(--space-3); }
  /* On phones the search field is not shown until asked for (owner,
     2026-07-29): the bottom nav's "Пошук" opens it and focuses it, and
     chrome.js drops the class again the moment focus leaves. Keeps the
     mobile header to its one compact row the rest of the time. When it
     does open it is still its own full-width second row, not squeezed
     into row 1 — `order: 10` puts it after everything else in the
     wrapping flex container. */
  .bz-header__search {
    order: 10;
    flex-basis: 100%;
    max-width: none;
    display: none;
  }
  body.is-search-open .bz-header__search { display: block; }
  /* Full phone-number group replaced by the "⋯" more menu's phone item
     below 900px (owner request, 2026-09-04) -- the caret rule above is
     now moot (its parent is hidden) but stays so nothing regresses if
     that width range is ever widened again. */
  .bz-header__phones { display: none; }
  .bz-header__phones-caret { display: none; }
  .bz-header__mobile-actions { display: flex; }
  .bz-header__actions { gap: var(--space-2); margin-left: auto; }
  .bz-header__actions > .bz-header__icon-btn { display: none; }
  /* The bottom nav's own badge (.bz-cart-icon--mobile) already covers
     cart access at this width too. */
  .bz-header__actions .bz-cart-icon { display: none; }
}

@media (min-width: 900px) {
  /* The search field takes ALL the room the rest of the row does not want
     (owner, 2026-09-01): no max-width, so `flex: 1` simply absorbs the
     remainder and the header never shows a dead gap. It had a cap here
     before — first a flat 480px, then clamp(480px, 36vw, 860px) — and both
     left visible emptiness on a large laptop: measured at 1728px, the row
     used 1323px of 1621px and the missing 298px sat between the field and
     the actions. Sizing the field to the leftover is the whole point; a
     cap is what created the gap. It still shrinks on a tight row, because
     flex: 1 + min-width: 0 governs that, not max-width. */
  .bz-header__search { max-width: none; }
  /* Kept as a backstop rather than as the mechanism: with the field
     uncapped there is normally no slack left for it to push. It only does
     anything if the row ever has spare width the field cannot take — e.g.
     if search is hidden — and then the actions still end on the right
     gutter instead of trailing off mid-row. Desktop only; below 900px the
     row wraps and .brand-logo is the flexible element instead. */
  .bz-header__actions { margin-left: auto; }
}

/* Header phone/search degrade in four steps as the row narrows (owner,
   2026-09-04, revised twice — first "one phone number should disappear,
   then second one be replaced with an icon ... and only then the Поиск
   hint should be changed", then corrected to "First collapse secondary
   phone number, then search, then primary phone number everywhere" —
   SEARCH gives way before the primary number does, not after). Each step
   only gives up the next-least-important thing, latest first:
     1. both numbers, full text; full search placeholder
     2. ONE number (extra hidden), full text; full placeholder
     3. ONE number, full text; SHORT "Шукати: назва, артикул, фабрика"/
        "Искать: название, артикул, фабрика" placeholder
     4. ONE number -> icon (+ small label like ♡/Кошик on the ordinary
        header; bare icon, no label, on the landing hero — "no need for
        description text on a landing page header"); short placeholder
   Only step 1's threshold has a plain @media default (1500px, tuned
   against the ORDINARY header) — steps 2-4 depend on each other in a
   sequence a fixed breakpoint can't express (whichever step-3 text is
   showing changes how much room is left for step 4's decision), so
   chrome.js measures the placeholder's ACTUAL rendered width against the
   search input's real clientWidth (canvas-measured, not guessed) and
   drives all of them through .bz-phone-extra-hidden/.bz-phone-compact on
   the .bz-header element plus the placeholder string itself. This also
   fixes a fixed-breakpoint version's real failure: the LANDING hero
   header (same markup, different surrounding chrome — its own catalog-
   button backdrop/border, bigger gaps) needs meaningfully more room for
   the same content than the ordinary header at the same viewport width,
   so one breakpoint tuned on one reliably clipped the placeholder on the
   other. Same principle as the mobile fit-check above ("measuring
   instead of guessing a breakpoint"), just applied to the desktop row. */

/* Step 1 default: secondary phone numbers ride in the header only when
   the row genuinely has room for them (owner, 2026-09-01: "if there is
   enough space like on 16 inches screen, show all phones"). Hidden by
   default — so phones and small laptops are unaffected and keep the
   single main number — and revealed from 1500px up on the ordinary
   header. A 16" laptop (1728px logical) clears this comfortably. The
   extras are in the markup at every width either way, so this is purely
   a display decision — see index.php's header actions block. */
.bz-header__phone--extra { display: none; }
@media (min-width: 1500px) {
  .bz-header__phone--extra { display: inline-flex; }
}
/* chrome.js's step-2 override, only ever adds a hide (three classes here
   vs. one on the rule above, so this always wins on specificity alone —
   no !important needed). */
.bz-header.bz-phone-extra-hidden .bz-header__phone--extra { display: none; }

/* Step 4 (last resort — steps 2/3 have no CSS presence: hiding the extra
   button is covered by the rule above, and a placeholder string can't be
   conditioned in CSS at all, so chrome.js sets both directly). The one
   remaining number collapses from full text to an icon + small label —
   the same icon-on-top/label-underneath shape as the ♡ Избранное / Кошик
   actions right next to it (.bz-header__icon-btn), not a bare icon: the
   label span (.bz-header__phone-label, "Телефон", identical in both
   languages) is in the markup at every width and only shown here. Only
   :not(.bz-header__phone--extra) is targeted — an extra button, on the
   rare width band where JS might reveal one this low, has no label span
   to show and would rather just stay hidden than grow a mismatched
   control. No plain @media default here (unlike step 1) — this step only
   makes sense once steps 2/3 have already failed, which a width-only
   breakpoint can't know, so it exists purely as chrome.js's
   .bz-header.bz-phone-compact class. */
.bz-header.bz-phone-compact .bz-header__phones .bz-header__phone:not(.bz-header__phone--extra) {
  flex-direction: column;
  gap: 2px;
  padding: 2px 4px;
  font-size: 11px;
  font-weight: 600;
}
.bz-header.bz-phone-compact .bz-header__phones .bz-header__phone:not(.bz-header__phone--extra) .bz-header__phone-number { display: none; }
.bz-header.bz-phone-compact .bz-header__phones .bz-header__phone:not(.bz-header__phone--extra) .bz-header__phone-label { display: inline; }
.bz-header.bz-phone-compact .bz-header__phones .bz-header__phone:not(.bz-header__phone--extra) .bz-icon { width: 16px; height: 16px; }
/* The label only ever shows inside step 4 above — hidden by default so
   it doesn't add a stray word next to the number at every wider width. */
.bz-header__phone-label { display: none; }
/* Landing hero header never shows it AT ALL, even once step 4 kicks in
   (owner, 2026-09-04: "no need for description text on a landing page
   header") — bare icon there, same shape the mobile-collapsed circle
   already uses. !important because .bz-phone-compact's own label rule
   above is more specific (6 classes vs. this rule's 3 classes + type)
   and would otherwise win; nothing else sets this property with
   !important, so there's no fight to lose. */
body.bz-home-hero:not(.is-hero-stuck) .bz-header__phone-label { display: none !important; }

/* ---------- Header cart icon (mod_virtuemart_cart, dropdown layout) ---------- */
/* Real live cart count, reused across header actions, mega-catalog header
   and mobile bottom nav — see mebelvdom-redesign-spec.md §6.6/§7.7 and the
   "cart-icon"/"cart-icon-megacatalog"/"cart-icon-mobile" module positions
   wired in index.php. Badge text is reformatted to a bare digit by
   chrome.js (VM's own totalProductTxt is a full phrase like "3 товари"). */

.bz-cart-icon,
.bz-cart-icon--mobile {
  position: relative;
  display: inline-flex;
}
/* Same icon-on-top/label-underneath shape as .bz-header__icon-btn (its
   sibling ♡ "Обране" button) — see dropdown.php's override for why the
   markup has an icon-wrap span around the glyph+badge. */
.bz-cart-icon .dropdownCart-btn,
.bz-cart-icon--mobile .dropdownCart-btn {
  display: inline-flex;
  flex-direction: column;
  align-items: center;
  gap: 2px;
  border: none;
  background: none;
  color: var(--c-text);
  font-family: var(--font-body);
  font-size: 11px;
  font-weight: 600;
  line-height: 1.2;
  cursor: pointer;
  padding: 2px 4px;
  border-radius: var(--radius-sm);
}
.bz-cart-icon .dropdownCart-btn:hover { background: var(--c-pillow); }
.bz-cart-icon .dropdownCart-icon-wrap { position: relative; display: inline-flex; }
.bz-cart-icon .dropdownCart-icon,
.bz-cart-icon--mobile .dropdownCart-icon {
  font-size: 16px;
  font-style: normal;
  color: var(--c-coffee);
}
.bz-cart-icon .dropdownCart-icon .bz-icon,
.bz-cart-icon--mobile .dropdownCart-icon .bz-icon { width: 16px; height: 16px; }
.bz-cart-icon .dropdownCart-icon img { width: 18px; height: 18px; }
.bz-cart-icon .dropdownCart-label { color: var(--c-text); }
.bz-cart-icon .total_products,
.bz-cart-icon--mobile .total_products {
  position: absolute;
  top: -5px;
  right: -8px;
  min-width: 16px;
  height: 16px;
  padding: 0 4px;
  border-radius: var(--radius-pill);
  background: var(--c-ginger);
  color: #fff;
  font-size: 9px;
  font-weight: 700;
  line-height: 16px;
  text-align: center;
  white-space: nowrap;
}
.bz-cart-icon .total_products:empty,
.bz-cart-icon--mobile .total_products:empty { display: none; }

/* Hover dropdown panel listing cart items — matches design frame 4a
   "Хедер — кошик при наведенні" pixel-for-pixel (colors/radii/shadow
   taken directly from that mockup's inline styles; the ones that match
   existing tokens use the token, #f0e9dd doesn't have one so it's
   literal). */
/* Section enlarged + fonts bumped 2026-09-27 (owner: "make cart preview
   section bigger") — was 520x420 with 11-16px text throughout. */
.bz-cart-icon .dropdownCart-container {
  display: none;
  position: absolute;
  top: 38px;
  right: -20px;
  /* Owner, 2026-09-28: "taller and wider if needed" — was a flat 580px.
     min() lets it use the extra room on a real desktop viewport while
     still never overflowing a narrower one. */
  width: min(640px, 94vw);
  background: var(--c-card);
  border: 1px solid var(--c-line);
  border-radius: 16px;
  box-shadow: 0 22px 48px rgba(58, 44, 32, .24);
  padding: 20px 22px;
  text-align: left;
  z-index: 5;
}
.bz-cart-icon .dropdownCart-container.dropdown_align_left { right: auto; left: -20px; }
/* Owner, 2026-09-28: dropdown.php now always renders the header/total/
   actions skeleton (see that file's own comment on why — in short, VM
   core's update_cart.js only fills EXISTING elements on an AJAX cart
   update, it never creates missing ones, so gating this markup behind
   "cart has items" at initial page-load time meant the very first
   add-to-cart on a page that loaded with an empty cart produced a preview
   with the item but no "Итого"/buttons at all: nothing was there for
   update_cart.js's .find(".total").html(...) etc. to write into).
   Hiding purely via :has() here keeps the exact same look for a
   genuinely empty cart (just the friendly .bz-cart-empty message) but
   self-corrects the instant update_cart.js swaps in a real product row —
   no JS involved, :has() re-evaluates live off the current DOM. */
.bz-cart-icon .dropdownCart-container:has(.bz-cart-empty) .dropdownCart-header,
.bz-cart-icon .dropdownCart-container:has(.bz-cart-empty) .dropdownCart-total,
.bz-cart-icon .dropdownCart-container:has(.bz-cart-empty) .dropdownCart-actions {
  display: none;
}
/* Owner, 2026-09-27: with 5+ items (or any item whose picked options ran to
   several lines — see the one-per-row cart.css fix from the same day),
   the product list alone could exceed the container's old 480px
   max-height, and since .dropdownCart-total/.dropdownCart-actions are
   siblings AFTER .vm_cart_products in the SAME scrolling box (see
   mod_virtuemart_cart/dropdown.php), they scrolled out of view along with
   it — the "Итого"/"Оформити замовлення" footer looked like it had simply
   disappeared, with no visible scrollbar affordance hinting otherwise.
   Moving the cap to the product list only keeps the header/total/actions
   always rendered below it in normal flow, always visible; only the list
   itself scrolls once it grows past a couple of items.
   Owner, 2026-09-28: raised 320px -> min(440px, 55vh) ("taller if
   needed") now that the footer no longer shares this scroll box with it
   — there's no more reason to keep the cap small, only a reason to keep
   SOME cap so the popup can't run off the bottom of a short viewport. */
.bz-cart-icon .vm_cart_products {
  max-height: min(440px, 55vh);
  overflow-y: auto;
}
.bz-cart-icon .dropdownCart-header {
  display: flex;
  justify-content: space-between;
  align-items: center;
  padding-bottom: 11px;
}
.bz-cart-icon .dropdownCart-header-title { font-family: var(--font-heading); font-weight: 600; font-size: 18px; color: var(--c-text); }
.bz-cart-icon .dropdownCart-header .total { font-weight: 800; font-size: 16px; color: var(--c-text); }
/* Grid, not flex: the 96px thumb needs to span all three text rows
   (name, concise options, price) beside it — same trick as the main
   cart page's .bz-cart-item (cart.css), just with .product_row_info
   dissolved via display:contents so its own children (.image,
   .product_name_line, .product_price) can sit directly in this grid
   alongside their sibling .customProductDataConcise. */
.bz-cart-icon .vm_cart_products .product_row {
  display: grid;
  grid-template-columns: 96px 1fr;
  grid-template-areas:
    "thumb name"
    "thumb fields"
    "thumb price";
  column-gap: 14px;
  row-gap: 7px;
  padding: 14px 0;
  border-top: 1px solid #f0e9dd;
}
.bz-cart-icon .product_row_info { display: contents; }
.bz-cart-icon .product_row_info .image {
  grid-area: thumb;
  width: 96px;
  height: 96px;
  border-radius: 10px;
  background: var(--c-bg);
  border: 1px solid var(--c-line);
  overflow: hidden;
}
/* VM renders this with Bootstrap's own .img-thumbnail class, which
   carries its own padding + white background-color — reset both
   explicitly or the photo sits in a visible white inset regardless of
   this box's own border/radius (same fix as cart.css's item thumb). */
.bz-cart-icon .product_row_info .image img { width: 100%; height: 100%; object-fit: cover; padding: 0; background: none; border: none; }
.bz-cart-icon .product_name_line {
  grid-area: name;
  display: flex;
  align-items: baseline;
  gap: 4px;
  min-width: 0;
}
.bz-cart-icon .product_name { font-size: 16px; font-weight: 700; color: var(--c-text); line-height: 1.35; min-width: 0; }
/* "× 2" — the multiplication sign is CSS content, not markup, so VM's
   own update_cart.js can keep replacing .quantity's innerHTML with a
   bare number on every AJAX cart refresh without needing to know about
   the prefix. */
.bz-cart-icon .quantity { font-size: 13px; color: var(--c-muted); white-space: nowrap; flex: none; }
.bz-cart-icon .quantity:not(:empty)::before { content: '× '; }
/* Concise picked-options row (design frame 4a) — see
   BzMegaCatalog::renderConciseCartCustomFieldsHtml() for how this
   markup is built. */
.bz-cart-icon .customProductDataConcise { grid-area: fields; }
/* One option per row (owner, 2026-09-28) — same reasoning and fix as the
   full /cart page's identical change (cart.css, 2026-09-27): flex-wrap
   packed as many "Label: value" pairs per line as the row's width
   allowed, inconsistent from one item to the next. */
.bz-cart-icon .bz-cart-preview-fields {
  display: flex;
  flex-direction: column;
  gap: 3px;
  font-size: 13px;
  line-height: 1.5;
}
.bz-cart-icon .bz-cart-preview-field__label { color: var(--c-muted); }
.bz-cart-icon .bz-cart-preview-field__value { color: var(--c-text); font-weight: 600; }
/* Colour swatch mini-icon (owner, 2026-09-27) — same element
   BzMegaCatalog::renderConciseCartCustomFieldsHtml() now emits on the full
   /cart page (see cart.css); styled here too so it doesn't render as a
   bare unstyled span in this header preview. No hover-zoom in this small
   dropdown — that's cart.css/cart.js's addition, scoped to the full page. */
.bz-cart-icon .bz-cart-swatch {
  display: inline-block;
  vertical-align: middle;
  width: 18px;
  height: 18px;
  border-radius: 5px;
  border: 1px solid var(--c-line);
  background-size: cover;
  background-position: center;
  background-color: var(--c-bg);
  margin-right: 2px;
  cursor: default;
}
.bz-cart-icon .product_price {
  grid-area: price;
  font-weight: 800;
  font-size: 16px;
  color: var(--c-text);
  white-space: nowrap;
  align-self: end;
}
.bz-cart-icon .dropdownCart-total {
  display: flex;
  justify-content: space-between;
  align-items: baseline;
  padding: 12px 0 2px;
  border-top: 1px solid var(--c-line);
}
.bz-cart-icon .dropdownCart-total span:first-child { font-size: 15px; color: var(--c-muted); }
.bz-cart-icon .dropdownCart-total .total { font-family: var(--font-heading); font-weight: 700; font-size: 24px; color: var(--c-text); }
.bz-cart-icon .dropdownCart-actions { display: flex; gap: 9px; margin-top: 11px; }
.bz-cart-icon .dropdownCart-action {
  flex: 1;
  text-align: center;
  font-weight: 700;
  font-size: 15px;
  padding: 13px 0;
  border-radius: 11px;
  text-decoration: none;
}
.bz-cart-icon .dropdownCart-action--outline {
  border: 1.5px solid var(--c-coffee);
  color: var(--c-coffee);
}
.bz-cart-icon .dropdownCart-action--fill {
  background: var(--c-ginger);
  color: var(--c-card);
}
.bz-cart-icon .dropdownCart-action:hover { opacity: .9; text-decoration: none; }
.bz-cart-empty {
  padding: var(--space-4) var(--space-2);
  text-align: center;
  color: var(--c-muted);
  font-size: 15px;
}

/* Mobile bottom-nav variant: badge only, overlaid on the sibling nav
   item's own icon — see the "bz-bottomnav__cart" <li> in index.php. */
.bz-bottomnav__cart { position: relative; }
.bz-cart-icon--mobile {
  position: absolute;
  top: 2px;
  right: 22%;
  pointer-events: none;
}
.bz-cart-icon--mobile .dropdownCart-btn {
  all: unset;
  display: block;
  pointer-events: none;
}
.bz-cart-icon--mobile .dropdownCart-icon,
.bz-cart-icon--mobile .dropdownCart-label { display: none; }
.bz-cart-icon--mobile .total_products {
  position: static;
  display: inline-block;
  min-width: 14px;
  height: 14px;
  font-size: 9px;
  line-height: 14px;
}


/* ---------- §4b Search icon button + Ajax quick-search dropdown ---------- */
/* One ⌕ submit button sits inside the search pill (header + mega-catalog);
   clicking it, like Enter, goes to the full results page. Shared class so
   both search fields get the same control. */
.bz-search-btn {
  position: absolute;
  top: 50%;
  right: 5px;
  transform: translateY(-50%);
  width: 34px;
  height: 34px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  border: none;
  border-radius: var(--radius-pill);
  background: transparent;
  color: var(--c-muted);
  font-size: 18px;
  line-height: 1;
  cursor: pointer;
  transition: background .15s ease, color .15s ease;
}
.bz-search-btn .bz-icon { width: 18px; height: 18px; }
.bz-search-btn:hover,
.bz-search-btn:focus-visible {
  background: var(--c-coffee);
  color: var(--c-card);
  outline: none;
}

/* The dropdown is appended to each [data-bz-quicksearch] form by chrome.js;
   the form is position:relative so this anchors under the field. */
.bz-quicksearch {
  position: absolute;
  top: calc(100% + 8px);
  left: 0;
  right: 0;
  z-index: 60;
  display: none;
  padding: 10px;
  background: var(--c-card);
  border: 1px solid var(--c-line);
  border-radius: var(--radius-lg);
  box-shadow: 0 24px 52px rgba(58, 44, 32, .22);
  max-height: min(70vh, 560px);
  overflow-y: auto;
  text-align: left;
}
.bz-quicksearch.is-open { display: block; }
.bz-quicksearch__item {
  display: flex;
  gap: 12px;
  align-items: center;
  padding: 8px;
  border-radius: 10px;
  text-decoration: none;
  color: var(--c-text);
}
.bz-quicksearch__item + .bz-quicksearch__item { border-top: 1px solid var(--c-line); }
.bz-quicksearch__item:hover { background: var(--c-bg); }
.bz-quicksearch__thumb {
  width: 52px;
  height: 52px;
  flex: none;
  border-radius: 9px;
  border: 1px solid var(--c-line);
  background: var(--c-bg);
  object-fit: cover;
}
.bz-quicksearch__thumb--empty {
  background: repeating-linear-gradient(45deg, #ece5d8 0 7px, #f3ede2 7px 14px);
}
/* Manufacturer logos are transparent-background artwork, not product
   photos — object-fit:contain + padding keeps them un-cropped instead of
   filling/cropping the square thumb like a product photo does. */
.bz-quicksearch__thumb--logo {
  object-fit: contain;
  padding: 6px;
  background: var(--c-card);
}
.bz-quicksearch__body { flex: 1; min-width: 0; }
.bz-quicksearch__title {
  display: block;
  font-weight: 700;
  font-size: 14px;
  line-height: 1.25;
  color: var(--c-text);
}
.bz-quicksearch__meta { display: block; margin-top: 2px; font-size: 11.5px; color: var(--c-muted); }
.bz-quicksearch__meta b { color: var(--c-text); }
.bz-quicksearch__cats {
  margin-top: 8px;
  padding-top: 9px;
  border-top: 1px solid var(--c-line);
  display: flex;
  gap: 8px;
  flex-wrap: wrap;
}
.bz-quicksearch__cat {
  padding: 6px 12px;
  background: var(--c-bg);
  border: 1px solid var(--c-line);
  border-radius: var(--radius-pill);
  font-size: 11.5px;
  font-weight: 600;
  color: var(--c-text);
  text-decoration: none;
}
.bz-quicksearch__cat:hover { border-color: var(--c-coffee); }
.bz-quicksearch__all {
  display: block;
  margin-top: 10px;
  padding: 6px 8px;
  font-weight: 700;
  font-size: 12.5px;
  color: var(--c-ginger);
  text-decoration: none;
}
.bz-quicksearch__all:hover { text-decoration: underline; }
.bz-quicksearch__empty {
  padding: 16px 8px;
  text-align: center;
  font-size: 12.5px;
  color: var(--c-muted);
}

/* ---------- Breadcrumbs (mockups 2c/2d) ----------
   Replace Joomla/Bootstrap's loud default (16px blue links, dark "/",
   grey pill box + location-pin icon) with the design's concise, muted
   "/"-separated trail. Applies wherever the breadcrumbs module renders
   (category + product pages etc.), styled globally here in chrome.css. */
.mod-breadcrumbs__wrapper { margin: 0; }  /* full-width flex item; centering is on the <ol> below */
.mod-breadcrumbs.breadcrumb {
  /* mirror .bz-container--wide so the crumb lines up with the page content
     (max-width + auto-centering + 16px side padding). */
  max-width: var(--bz-container-wide);
  margin: 0 auto;
  padding: var(--space-3) var(--bz-gutter) 0 !important;
  background: none;
  font-size: 12px;
  line-height: 1.4;
}
/* drop the leading location-pin divider */
.mod-breadcrumbs .mod-breadcrumbs__divider { display: none; }
.mod-breadcrumbs .breadcrumb-item,
.mod-breadcrumbs .breadcrumb-item a,
.mod-breadcrumbs .breadcrumb-item a.pathway {
  color: var(--c-muted);
  text-decoration: none;
}
.mod-breadcrumbs .breadcrumb-item a:hover { color: var(--c-coffee); }
/* concise "/" separator in light tan, only between crumbs */
.mod-breadcrumbs .breadcrumb-item + .breadcrumb-item::before {
  content: "/";
  color: #c8bfae;
  padding: 0 8px;
  float: none;
}
/* current page: dark + semibold, no link */
.mod-breadcrumbs .breadcrumb-item.active,
.mod-breadcrumbs .breadcrumb-item.active > span {
  color: var(--c-text);
  font-weight: 600;
}

/* ---------- Home page video hero: global chrome overrides ----------
   Only while body.bz-home-hero is set (index.php sets it for the home menu
   item's com_virtuemart view, which is the only page with the video hero).

   The design's hero has no utility bar and no category nav — the header
   rides transparently over the video, slides away as the video scrolls
   out, and comes back as a compact cream bar. Three states, all driven by
   body classes that home.js toggles:

     (neither)       transparent header over the video
     .is-hero-gone   header slid up, mid-handover
     .is-hero-stuck  compact cream bar pinned to the top

   The header is position:fixed here (not sticky) so the hero can start at
   the very top of the document and the video is never pushed down by a
   band of chrome. */

body.bz-home-hero .bz-catnav { display: none; }

/* The utility bar ("subheader": info links, hours, language toggle) rides
   with the compact cream bar — off-screen while the transparent header is
   over the video, sliding in above the header once the video is behind us.
   It has to be fixed rather than in flow because the header is, and the two
   must stay stacked. home.js measures it and publishes --bz-utility-h,
   since its height depends on breakpoint and font metrics. */
body.bz-home-hero .bz-utility {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  z-index: 101;
  transform: translateY(-100%);
  transition: transform .32s cubic-bezier(.22, .7, .2, 1);
  will-change: transform;
}
body.bz-home-hero.is-hero-stuck .bz-utility { transform: translateY(0); }
body.bz-home-hero.is-hero-stuck .bz-header { top: var(--bz-utility-h, 33px); }

/* Language toggle carried by the header itself, for the landing state
   where the utility bar that normally holds it is off-screen. Hidden
   everywhere else — including once the utility bar has slid in, so the
   page never shows two of them. */
.bz-header__lang { display: none; }

/* Landing skin for the segmented pill (base: .bz-lang-toggle above). Over
   the video the capsule is frosted glass rather than a sage hairline, and
   the chip is separated from it by 3px of padding instead of filling it
   edge to edge — the design's own two treatments for the two backgrounds.
   The tint carries its own contrast so the control stays legible whatever
   frame of the footage is behind it, which a text-shadow on bare links
   never quite managed. */
body.bz-home-hero:not(.is-hero-stuck) .bz-header__lang {
  display: inline-flex;
  align-items: center;
  gap: 2px;
  padding: 3px;
  background: rgba(255, 253, 249, .14);
  border: 1px solid rgba(255, 253, 249, .3);
  border-radius: var(--radius-pill);
  backdrop-filter: blur(8px);
  overflow: visible;
  white-space: nowrap;
  color: var(--c-card);
  font-size: 11px;
}
body.bz-home-hero:not(.is-hero-stuck) .bz-header__lang a,
body.bz-home-hero:not(.is-hero-stuck) .bz-header__lang .is-active {
  padding: 5px 10px;
  border-radius: var(--radius-pill);
  color: rgba(255, 253, 249, .8);
  font-weight: 700;
  opacity: 1;
}
body.bz-home-hero:not(.is-hero-stuck) .bz-header__lang a:hover { color: var(--c-card); }
body.bz-home-hero:not(.is-hero-stuck) .bz-header__lang .is-active {
  background: var(--c-card);
  color: var(--c-text);
  font-weight: 800;
}

body.bz-home-hero .bz-header {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  z-index: 100;
  background: transparent;
  border-bottom-color: transparent;
  box-shadow: none;
  transition:
    transform .32s cubic-bezier(.22, .7, .2, 1),
    top .32s cubic-bezier(.22, .7, .2, 1),
    opacity .2s linear,
    background-color .3s ease,
    border-color .3s ease,
    box-shadow .3s ease,
    padding .3s ease;
}

/* --- state: transparent, over the video --- */

/* The logo artwork is dark, so it needs its own cream plate to stay legible
   against the footage (same treatment as the design's hero header). */
body.bz-home-hero:not(.is-hero-stuck) .bz-header .brand-logo {
  background: var(--c-card);
  border-radius: 12px;
  padding: 7px 13px;
  box-shadow: 0 4px 16px rgba(0, 0, 0, .18);
}
body.bz-home-hero:not(.is-hero-stuck) .bz-header__catalog-btn {
  background: rgba(255, 253, 249, .14);
  border: 1px solid rgba(255, 253, 249, .3);
  backdrop-filter: blur(8px);
  color: var(--c-card);
}
body.bz-home-hero:not(.is-hero-stuck) .bz-header__search input {
  background: rgba(255, 253, 249, .13);
  border-color: rgba(255, 253, 249, .26);
  backdrop-filter: blur(8px);
  color: var(--c-card);
}
body.bz-home-hero:not(.is-hero-stuck) .bz-header__search input::placeholder { color: rgba(255, 253, 249, .72); }
body.bz-home-hero:not(.is-hero-stuck) .bz-header .bz-search-btn { color: var(--c-card); }
/* Over the video the header carries ONE number, in one pill, with the
   caret inside it — the pre-2026-09-01 shape, restored on owner request
   after the all-numbers header shipped. Two pale capsules plus a detached
   ▾ is a lot of chrome to lay over a hero shot, and the landing's job is
   the footage, not the contact block. This is the LANDING-OVER-VIDEO state
   only: once the header settles into its solid state past the hero it is
   an ordinary header again and shows every number, like every other page.
   The extras are still in the markup here — only hidden — so the contacts
   popup this pill opens still lists them all. */
body.bz-home-hero:not(.is-hero-stuck) .bz-header__phone--extra { display: none; }
@media (max-width: 899px) {
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__mobile-cart,
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__mobile-actions [data-bz-action="search"],
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__more {
    display: none !important;
  }
}

@media (min-width: 900px) {
  /* The pill moves from the button to the GROUP, so the ✆, the number and
     the ▾ sit inside one pale capsule the way they did when the caret was
     still a child of the button. Left outside it, the caret rendered white
     on bright footage and read as a smudge beside the pill.
     Desktop only: below 900px the landing collapses the BUTTON itself to a
     39px icon circle (see the max-width block further down), and a second
     background wrapped around that would double it up. */
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__phones {
    background: var(--c-pillow);
    border-radius: var(--radius-pill);
    padding: 10px 18px;
    gap: 6px;
    color: var(--c-text);
  }
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__phones .bz-header__phone {
    background: none;
    padding: 0;
  }
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__phones-caret { color: var(--c-text); }
}

@media (max-width: 899px) {
  /* Mobile landing keeps the pill on the button, because there the button
     IS the pill — the 39px circle — and the group has no background. */
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__phone {
    background: var(--c-pillow);
    border-radius: var(--radius-pill);
    padding: 10px 18px;
    color: var(--c-text);
  }
}
body.bz-home-hero:not(.is-hero-stuck) .bz-header__icon-btn,
body.bz-home-hero:not(.is-hero-stuck) .bz-header__mobile-btn,
body.bz-home-hero:not(.is-hero-stuck) .bz-header .bz-cart-icon .dropdownCart-btn,
body.bz-home-hero:not(.is-hero-stuck) .bz-header .bz-cart-icon .dropdownCart-label { color: var(--c-card); }
body.bz-home-hero:not(.is-hero-stuck) .bz-header__icon-glyph,
body.bz-home-hero:not(.is-hero-stuck) .bz-header .bz-cart-icon .dropdownCart-icon { color: var(--c-card); }
body.bz-home-hero:not(.is-hero-stuck) .bz-header__icon-btn:hover,
body.bz-home-hero:not(.is-hero-stuck) .bz-header__mobile-btn:hover,
body.bz-home-hero:not(.is-hero-stuck) .bz-header .bz-cart-icon .dropdownCart-btn:hover { background: rgba(255, 253, 249, .16); }
/* The "more" menu itself is an ordinary opaque card regardless of hero
   state (it floats above the video, not on it), so its own item colour
   stays the plain --c-text/--c-coffee pair from .bz-header__more-menu-item
   -- only the round trigger button above needs the video tint. */

/* --- state: mid-handover, header out of the way --- */

body.bz-home-hero.is-hero-gone .bz-header {
  transform: translateY(-105%);
  opacity: 0;
  pointer-events: none;
}

/* --- state: compact cream bar --- */

body.bz-home-hero.is-hero-stuck .bz-header {
  background: var(--c-card);
  border-bottom-color: var(--c-line);
  box-shadow: 0 6px 20px rgba(58, 44, 32, .08);
}
body.bz-home-hero.is-hero-stuck .bz-header .bz-container {
  padding-top: var(--space-2);
  padding-bottom: var(--space-2);
}
/* Scoped to .bz-header specifically (unlike the two rules just above,
   which already were) — .brand-logo is reused verbatim by the mega-
   catalog overlay's own header (megacatalog.css/index.php), which sits on
   top of this one at z-index:500 and has nothing to do with the hero. A
   bare `.brand-logo img` here shrank that unrelated logo too the moment
   is-hero-stuck flipped on behind it — visible as the overlay's own
   header jumping smaller (see home.js's overOwnOverlay() for the other
   half of this bug: is-hero-stuck could flip on at all while an overlay
   had the hero fully covered). */
body.bz-home-hero.is-hero-stuck .bz-header .brand-logo img { height: 34px; }

@media (max-width: 899px) {
  /* Over the video the mobile header is one compact row (logo · ☰ · phone);
     the search field only appears once the cream bar takes over, exactly as
     in the design's phone frames. Everything in that row is shrunk enough
     that it fits a 360px screen without wrapping — .bz-header .bz-container
     is flex-wrap: wrap at this width, so anything that doesn't fit drops to
     a second line and the header stops being a thin bar over the video. */
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__search { display: none; }
  body.bz-home-hero .bz-header .bz-container { padding-top: var(--space-2); padding-bottom: var(--space-2); }
  body.bz-home-hero:not(.is-hero-stuck) .bz-header .bz-container { gap: var(--space-2); flex-wrap: nowrap; }
  body.bz-home-hero:not(.is-hero-stuck) .bz-header .brand-logo { flex: 0 1 auto; min-width: 0; padding: 5px 9px; }
  /* The logo is a 4.43:1 wordmark. A fixed `height` plus the `max-width:
     100%` this breakpoint puts on every logo does NOT scale it — it
     SQUASHES it: the width gets clamped to whatever the plate has left
     while the height stays put, and it was rendering 36×26 (i.e. 1.4:1,
     horizontally crushed to a third of its proper width). Both dimensions
     have to stay auto and be bounded by max-* instead, which is the only
     form that makes a browser preserve the intrinsic ratio. */
  body.bz-home-hero:not(.is-hero-stuck) .bz-header .brand-logo img {
    height: auto;
    width: auto;
    max-height: 30px;
    max-width: 100%;
  }
  /* The row is logo · ☰ · search · cart · ⋯ now (2026-09-04) -- see the
     general @media (max-width: 899px) block above for
     .bz-header__mobile-actions, which this hero state does not need to
     override: it already renders icon-only with no number to drop. */
  body.bz-home-hero:not(.is-hero-stuck) .bz-header__catalog-btn { padding: 8px 11px; }
}

/* ---------- Manufacturer-name-as-link (mockup screens 4/5/6/7) ----------
   Shared here (not per-page CSS) since it's used across product detail,
   category cards, cart line items, and the favourites/compare pages.
   Subtle by design: inherits the surrounding text colour (never its own
   accent colour) and underlines in the same quiet line tone the rest of
   the design already uses for hairlines/borders, not full-strength text
   colour — a manufacturer mention reads as a link on closer look, not as
   a competing call to action next to the product name/price. */
.bz-link-brand {
  color: inherit;
  text-decoration: underline;
  text-decoration-color: var(--c-line);
  text-underline-offset: 2px;
}
.bz-link-brand:hover { text-decoration-color: currentColor; }

/* Sibling of the rule above, and deliberately housed here rather than in
   productdetails.css even though it only ever applies on the product page:
   that file is rewritten wholesale by the importer tooling, which silently
   dropped this block three times over 2026-08-11 and left the links
   rendering as unstyled default-blue text. chrome.css is not on that path,
   and .bz-link-brand — the same kind of thing, a link treatment — already
   lives here, so this is a reasonable home, not just a hiding place.

   A Характеристики value whose custom field is also a live CustomFilters
   facet links back to the category filtered by it (see BzMegaCatalog::
   withCharacteristicFilterLinks()). Dotted rather than the solid underline
   above: inside a dense spec table only SOME rows are clickable, and the
   dotted rule reads as there is more behind this without making every
   other row look like dead text by comparison. Nothing is ever appended to
   the value — a result count printed here read as part of the spec itself
   (21 см14); it lives in the link's tooltip. */
.bz-specs-list__row dd .bz-spec-filter {
  color: inherit;
  text-decoration: underline dotted;
  text-decoration-color: var(--c-line);
  text-underline-offset: 3px;
}
.bz-specs-list__row dd .bz-spec-filter:hover,
.bz-specs-list__row dd .bz-spec-filter:focus-visible {
  color: var(--c-ginger);
  text-decoration-color: currentColor;
}
