/* The site's one informational message (modal_badge.jpg + modal_badge_mobile.jpg): "added to cart",
   every WooCommerce success notice, and anything raised through window.chrysalisMessage().
   Markup is built by assets/js/toast.js, copy comes from there or from inc/toast.php.
   Phones get the export's bottom sheet over a blurred scrim with the site's 34px close circle;
   from 640 up it is the export's card in the bottom-right corner, with no scrim and no close circle
   (the desktop export draws neither - "Close" under the button is the dismiss there). */
#clab-msg{position:fixed;inset:0;z-index:70;display:none}
#clab-msg[data-show]{display:block}
#clab-msg .clab-msg-scrim{position:absolute;inset:0;background:rgba(1,4,11,.45);-webkit-backdrop-filter:blur(15px);backdrop-filter:blur(15px);opacity:0;transition:opacity .3s ease}
#clab-msg[data-open] .clab-msg-scrim{opacity:1}
#clab-msg .clab-msg-card{position:absolute;left:0;right:0;bottom:0;background:#fff;border-radius:17px 17px 0 0;padding:28px 24px calc(38px + env(safe-area-inset-bottom));transform:translateY(100%);transition:transform .35s cubic-bezier(.4,0,.2,1)}
#clab-msg[data-open] .clab-msg-card{transform:none}
#clab-msg .clab-msg-card:focus{outline:none}
#clab-msg .clab-msg-x{position:absolute;top:24px;right:24px;display:flex;width:34px;height:34px;align-items:center;justify-content:center;border:0;border-radius:9999px;background:#f0f0f0;color:#01040b;cursor:pointer}
#clab-msg .clab-msg-x:hover{background:#e6e6e6}
#clab-msg .clab-msg-title{margin:0;padding-right:44px;font-family:inherit;font-size:24px;line-height:1;font-weight:500;letter-spacing:-.02em;color:#01040b}
#clab-msg .clab-msg-text{margin:24.5px 0 0;font-size:16.3px;line-height:20px;color:rgba(1,4,11,.55)}
#clab-msg .clab-msg-ok{margin-top:23.5px;display:flex;height:48px;width:100%;align-items:center;justify-content:center;gap:10px;border:0;border-radius:9999px;background:#01040b;color:#fff;font-family:inherit;font-size:15.5px;line-height:1;text-transform:uppercase;cursor:pointer;transition:opacity .2s ease}
#clab-msg .clab-msg-ok:hover{opacity:.85}
#clab-msg .clab-msg-close{display:block;margin:29px auto 0;padding:6px 12px;border:0;background:none;color:#01040b;font-family:inherit;font-size:15.5px;line-height:1;text-transform:uppercase;cursor:pointer;transition:opacity .2s ease}
#clab-msg .clab-msg-close:hover{opacity:.6}
@media (max-width:639px){html.clab-msg-open,html.clab-msg-open body{overflow:hidden}}
@media (min-width:640px){
#clab-msg{inset:auto;right:20px;bottom:20px;width:435px;max-width:calc(100vw - 40px)}
#clab-msg .clab-msg-scrim,#clab-msg .clab-msg-x{display:none}
#clab-msg .clab-msg-card{position:relative;left:auto;right:auto;bottom:auto;border-radius:17px;padding:32px 32px 28.7px;box-shadow:0 24px 60px rgba(1,4,11,.18);opacity:0;transform:translateY(16px);transition:opacity .3s ease,transform .35s cubic-bezier(.4,0,.2,1)}
#clab-msg[data-open] .clab-msg-card{opacity:1;transform:none}
#clab-msg .clab-msg-title{padding-right:0}
#clab-msg .clab-msg-text{margin-top:12.5px;font-size:15.3px;line-height:19px}
#clab-msg .clab-msg-ok{margin-top:34.5px;font-size:14.5px}
/* the desktop export writes this one in sentence case where the phone export shouts it */
#clab-msg .clab-msg-close{margin-top:11px;font-size:15.3px;text-transform:none}
}
@media (prefers-reduced-motion:reduce){#clab-msg .clab-msg-scrim,#clab-msg .clab-msg-card{transition:none}}
a.added_to_cart.wc-forward{display:none!important}
/* notices: WC prepends the group into form.checkout (a grid), so it must span both columns */
.woocommerce-NoticeGroup,.woocommerce-notices-wrapper{grid-column:1/-1;width:100%}
.woocommerce-error,.woocommerce-message,.woocommerce-info{list-style:none;margin:0 0 16px;padding:0;display:flex;flex-direction:column;gap:0;border-radius:14px;background:#fff;border:1px solid #e6e6e6;font-size:15px;line-height:20px;color:#01040b}
.woocommerce-error>li,.woocommerce-message,.woocommerce-info{position:relative;padding:14px 16px 14px 44px}
.woocommerce-error>li+li{border-top:1px solid #f0f0f0}
.woocommerce-error>li::before,.woocommerce-message::before,.woocommerce-info::before{content:"!";position:absolute;left:14px;top:14px;width:20px;height:20px;border-radius:9999px;background:#ce1126;color:#fff;font-size:12px;font-weight:600;line-height:20px;text-align:center}
.woocommerce-message::before,.woocommerce-info::before{background:#01040b}
.woocommerce-error a{text-decoration:underline}

/* WC's attribution element sits first in the column and makes space-y push the first card down */
wc-order-attribution-inputs{display:none}
wc-order-attribution-inputs+*{margin-top:0!important}

/* build-stack layout: exactly 3 card columns + the 331px panel (arbitrary Tailwind values are not in the prebuilt main.css) */
@media (min-width:1024px){
.stack-layout{grid-template-columns:minmax(0,1fr) 331px;align-items:start}
.stack-cards{grid-template-columns:repeat(3,minmax(0,1fr));align-items:start}
.stack-layout>.stack-panel{grid-column:2;grid-row:1}
}
.woocommerce-message:focus,.woocommerce-error:focus,.woocommerce-info:focus{outline:none}
.pol > h1 + p{margin-top:17px}

/* home hero video. The wrapper is the box: full height, on the hero's bottom edge, centred, and as
   wide as --hero-vw (Theme Options > Home > Hero > Video width). With no width set it falls back to
   the video's own 4:3 shape at full height, clamped to at least the full width so a window wider
   than 4:3 does not show bg-night down both sides.
   The side fades live in here, so they follow the video's edges instead of the screen's.
   None of this can be Tailwind: assets/css/main.css is a copy of the static build, so an arbitrary
   width, a custom property and these gradients would not be generated in it. */
/* The frame is the whole hero by default. With a width set (.is-contained, sm and up) it becomes the
   page container - .wrap's 1300px frame minus its own gutters (20 / 40 / 64px) - so the admin's
   width, and a px value too, are measured against the content column rather than the screen. The
   inner box is what the absolutely placed video is positioned in: an absolute child is placed in
   its parent's padding box, so the gutters have to sit outside the box it is measured against. */
.hero-video-frame{position:absolute;inset:0;pointer-events:none}
.hero-video-box{position:relative;height:100%}
.hero-video-frame.is-contained{left:50%;right:auto;transform:translateX(-50%);width:100%;max-width:1300px;padding:0 16px}
@media (min-width:640px){.hero-video-frame.is-contained{padding:0 20px}}
@media (min-width:768px){.hero-video-frame.is-contained{padding:0 40px}}
@media (min-width:1280px){.hero-video-frame.is-contained{padding:0 64px}}
.hero-video-wrap{position:absolute;bottom:5%;left:50%;transform:translateX(-50%);height:100%;width:100%;max-width:100%;pointer-events:none}
.hero-video{display:block;height:100%;width:100%;object-fit:cover}
/* With a width set in the admin the video is really that wide: the box stops being the whole hero
   and takes its height from the file's own shape, sitting on the hero's bottom edge. (Keeping the
   full height and cropping instead would mean a smaller number showed *less* of the picture rather
   than a smaller picture.) All three fades live in this box, so they travel with it. */
/* Phones keep the full-bleed hero: a percentage that reads well on a desktop leaves a postage
   stamp at 390 (60% is 234px wide), and home_mob.jpg draws the hero full-bleed anyway. */
/* every width, phones included: 100% of the container, whole picture, on the bottom edge */
.hero-video-wrap.is-sized{width:100%;height:auto}
.hero-video-wrap.is-sized .hero-video{height:auto;object-fit:contain}
/* phones and tablets (up to 1024, the tailwind `mobile:` range): lifted off the hero's bottom edge by a tenth
   of the hero's height */
@media (max-width:1024px){.hero-video-wrap{bottom:15%}}
/* Tablets: the three proof pills wrap onto two rows below ~890px and fit one row above it. On a
   short window the hero is content-height, so that one row of difference (68px) changed the hero's
   height and the bottom-anchored video jumped with it. The row is reserved at two rows' height
   (2 x 56 + the 12px gap) and one row sits at its bottom, so the hero - and the video - no longer
   move at the wrap point. */
@media (min-width:640px) and (max-width:1024px){
#hero [data-marquee-group]{min-height:124px;align-content:flex-end}
}
/* Vertical placement, unlike the width, runs at EVERY size: a percentage of the hero's height is
   the same share of the picture at 390 as at 1440, so it does not have the postage-stamp problem
   that gated .is-sized to sm and up. Both rules come after .is-sized on purpose - same specificity
   (0,2,0), so source order is what lets a crop override the height the width implied. */
.hero-video-wrap.is-lifted{bottom:var(--hero-vb)}
/* A fixed band + `cover` is what frees the height from the width: the picture fills the box and
   the overflow is cut instead of letterboxed, so the admin can place a strip of the video between
   the button and the pills without the width dictating how tall it lands. */
.hero-video-wrap.is-cropped{height:var(--hero-vh)}
.hero-video-wrap.is-cropped .hero-video{height:100%;object-fit:cover;object-position:center var(--hero-vpos,center)}
/* max-width keeps the box on screen, which is what makes the side fades visible: left at 0 and
   right at 0 of a box wider than the window would hang half of each band outside it. `cover`
   means this costs nothing at full width - the picture is scaled by the hero's height either way,
   so a 1300 box and a 1417 one clipped by the section's overflow-hidden show the same pixels. */
.hero-fade-left,.hero-fade-right{position:absolute;top:0;bottom:0;width:10%;pointer-events:none}
/* these two fade to the section's own bg-night (#05070d), not to .hero-fade's #0f0f11: the side
   edges sit next to the real background whenever the video is narrower than the window, and a
   fade that stops 10 levels short of it reads as a hard vertical line rather than a gradient. */
.hero-fade-left{left:0;background:linear-gradient(90deg,rgba(5,7,13,1) 0%,rgba(5,7,13,0) 100%)}
.hero-fade-right{right:0;background:linear-gradient(270deg,rgba(5,7,13,1) 0%,rgba(5,7,13,0) 100%)}
/* mirrors .hero-fade at the other end, and fades to bg-night for the same reason as the side pair:
   at full width its top edge is under the announcement + header, but once a width is set the video
   is shorter than the hero and that edge meets the section's plain background. */
.hero-fade-top{background:linear-gradient(180deg,rgba(5,7,13,1) 0%,rgba(5,7,13,0) 100%)}

/* The two overlays that are direct children of <body> get a stacking level of their own.
   They are display:none until opened, so the page-in fade below never runs on them at load -
   it starts on the click that shows them, and for its 600ms the element has opacity < 1 and
   therefore forms a stacking context. Their own fixed panels (z-40/z-50) are then trapped
   inside an element whose z-index is auto, which paints UNDER the header wrapper's z-30: the
   cart opened *behind* the bar and jumped in front of it the moment the fade finished. A real
   z-index here means that context, whenever one forms (the fade in, the fade out on leaving),
   still sits above the header. position:relative does not capture their fixed children - only
   a transform/filter/will-change ancestor would - so nothing moves. Below #clab-msg's 70. */
#minicart,#search{position:relative;z-index:60}

/* The minicart fades, both ways, off its own [data-open] - and it is taken OUT of the page-in
   animation above, or that animation would own its opacity for the first 600ms after the click
   that shows it and this transition would never be seen on opening.
   Before this there was no close animation at all: main.js drops [data-open] at the click and
   re-adds the `hidden` class on a 520ms timer, so nothing moved for half a second and then the
   panel vanished on one frame - "задержка потом резкое исчезновение". Now the fade starts on
   the click itself and is over well before that timer fires; the timer only does the display
   switch, which cannot be transitioned.
   pointer-events goes off with [data-open] for the same reason .mnav does it: for the rest of
   that 520ms the panel is still display:block over the whole page and would go on eating clicks
   while invisible. A reopen inside that window turns the fade around from wherever it is. */
#minicart{opacity:0;transition:opacity .3s ease}
#minicart[data-open]{opacity:1}
#minicart:not([data-open]){pointer-events:none}

/* page transition: the whole page - header, content, footer - fades in on load and out on an internal link */
@keyframes clab-page-in{from{opacity:0}to{opacity:1}}
body>*:not(script):not(style):not(link):not(#clab-msg):not(#clab-preloader):not(#clab-age-gate):not(#minicart){animation:clab-page-in .6s ease backwards}
body.clab-leave>*:not(script):not(style):not(link):not(#clab-preloader):not(#clab-age-gate){opacity:0;transition:opacity .4s ease;animation:none}
@media (prefers-reduced-motion:reduce){body>*{animation:none}body.clab-leave>*{transition:none}#minicart{transition:none}}

/* block reveal (assets/js/reveal.js): slides up 16px and fades in together, near-linear and easing out only at the very end */
.rv{opacity:0;transform:translateY(16px);transition:opacity .25s cubic-bezier(.5,.5,.5,1),transform .25s cubic-bezier(.5,.5,.5,1)}
.rv.rv-in{opacity:1;transform:none}

/* header: static bar at the top of the page, a fixed copy of it (no announcement strip) that slides in on
   scroll up (assets/js/header-scroll.js) */
.site-header[data-hdr="fixed"]{position:fixed;top:0;left:0;right:0;z-index:30;transform:translateY(0);visibility:visible;transition:transform .3s cubic-bezier(.4,0,.2,1)}
.site-header[data-hdr="fixed"][data-hidden]{transform:translateY(-100%);visibility:hidden;transition:transform .3s cubic-bezier(.4,0,.2,1),visibility 0s linear .3s}
.site-header[data-notrans]{transition:none!important}
/* The phone menu (#mobile-nav, position:fixed; inset:0) lives INSIDE the header. A transform on an
   ancestor makes that ancestor the containing block for fixed descendants, and the fixed bar carries
   translateY(0) - so once the page had scrolled past the static bar, the "full-screen" sheet was laid
   out in the bar's own 390x64 box and looked like the menu had not opened ("не всегда открывается";
   at the top of the page the bar is static, no transform, and it worked). While the sheet is in the
   layout (.hidden comes off on open and goes back on only after the fade-out) the bar drops its
   transform. The bar is on screen at that moment (its own toggle was just clicked) so nothing shifts. */
.site-header[data-hdr="fixed"]:has(.mnav:not(.hidden)){transform:none;transition:none}
/* the transparent About bar needs a body of its own once it floats over the page */
[data-header="over"] .site-header[data-hdr="fixed"]{background-color:rgba(0,0,0,.35);-webkit-backdrop-filter:blur(15px);backdrop-filter:blur(15px)}
@media (max-width:1024px){[data-header="over"] .site-header[data-hdr="fixed"]{background-color:rgba(0,0,0,.25)}}
@media (prefers-reduced-motion:reduce){.site-header[data-hdr="fixed"],.site-header[data-hdr="fixed"][data-hidden]{transition:none}}

/* shop format tabs (archive-product.php): the pressed look follows aria-pressed, since the three
   buttons are written with fixed classes. Attribute selector outranks the utilities on them. */
[data-format-tabs] button[data-format][aria-pressed="true"]{background-color:#01040b;color:#fff}
[data-format-tabs] button[data-format][aria-pressed="false"]{background-color:rgba(1,4,11,.05);color:#01040b}
