/* CRESTIAL — the single product.
 *
 * ⚑ HAND-WRITTEN, like shop.css and unlike the other ten files here, which are GENERATED from
 * the mockups. There is no mockup for a product page. See the header of shop.css.
 *
 * It borrows the swatches, the card ground and the type scale from the archive, so moving from
 * the grid to a product does not feel like moving to a different site.
 */

/* ============================================================================
 * Layout
 *
 * Picture left, everything you can act on right. The PICTURE is the sticky one.
 *
 * ⚑ THE SUMMARY WAS STICKY FIRST AND IT WAS THE WRONG COLUMN. On a well-documented article the
 * summary is ~970px — a spec list of eleven bullets, five finishes, two documents and a button
 * — while the photograph is ~650px. A sticky box that fills its own grid area has nowhere to
 * travel, and the browser stopped clamping it to that area: it pinned itself to the viewport
 * and scrolled straight over "The rest of the series" below, with the product title printed
 * across four product cards.
 *
 * The short column is the one worth pinning anyway. Keeping the photograph in view while
 * someone reads down the specification is the thing a visitor actually wants; keeping the
 * specification in view while they look at nothing is not.
 * ========================================================================== */

.woocommerce div.product {
	max-width: var(--wrap);
	margin: 0 auto;
	padding: clamp(28px, 4vw, 56px) var(--gut) 0;
	display: grid;
	grid-template-columns: minmax(0, 54fr) minmax(0, 46fr);
	gap: clamp(28px, 5vw, 80px);
	align-items: start;
}

/* ⚑ THE TWO BLOCKS BELOW THE FOLD ARE NO LONGER IN THIS GRID AT ALL, and getting them out is
   what stopped the photograph scrolling over them. They used to be printed inside
   <div class="product"> and forced full width with `grid-column: 1 / -1`; inc/shop-layout.php
   now hooks them to `woocommerce_after_single_product`, which fires after that div closes.

   The reason is the sticky picture. A sticky GRID ITEM is supposed to be clamped to its grid
   area — row 1, which ends under the taller of the picture and the summary — and Chrome clamps
   it to the grid CONTAINER instead. Measured on /product/arc-shelf/, where the picture is 652px
   and the summary only 520px: the grid area ends at 872px and the picture travelled to 1831px,
   exactly the bottom of div.product, printing itself across "The rest of the series".

   ⚑ IT DEPENDED ON WHICH COLUMN WAS TALLER, which is why it was not caught when the sticky was
   put on this column. The note below is right that a well-documented article has a ~970px
   summary against a ~650px photograph — on those the picture has room to travel and stops
   looking wrong. An accessory with five spec lines does not, and 306 of the catalogue's
   articles are accessories. */

/* ============================================================================
 * The photograph
 * ========================================================================== */

/*
 * ⚑ THE !important IS LOAD-BEARING AND CANNOT BE AVOIDED.
 *
 * WooCommerce renders the gallery wrapper with `style="opacity:0; transition:opacity .25s"`
 * INLINE, and relies on wc-single-product.js to set it to 1 once flexslider has initialised.
 * inc/woocommerce.php removes all three gallery theme supports — a catalogue article has one
 * photograph and a drawing, which is not a gallery — and with them goes the script. Nothing
 * ever sets the opacity back.
 *
 * The result was the product photograph invisible on all 306 pages: no error, no 404, the
 * <img> present and correct in the DOM with the right src, and a blank cream square where the
 * one picture the page exists for should be. An inline style can only be beaten by
 * !important, so this is the exception rather than a shortcut.
 */
.woocommerce div.product div.images.woocommerce-product-gallery {
	opacity: 1 !important;
}

.woocommerce div.product div.images {
	width: auto;
	float: none;
	margin: 0;
}

/*
 * ⚑ THIS RULE MOVED INTO THE SLIDE ON 15 Nov 2026 — see "The gallery slides" below. It used to
 * sit on `div.images img`, which from today also matches the rail thumbnails, where 56px of
 * padding leaves a 76px button holding a 20px picture.
 */

.woocommerce div.product div.images {
	position: sticky;
	top: 106px; /* header 82 + air */
}

/* The gallery features are declared off in inc/woocommerce.php — a catalogue article has one
   photograph and a drawing, which is not a gallery. If a plugin re-enables them, this keeps the
   trigger from floating over the corner of the picture. */
.woocommerce div.product div.images .woocommerce-product-gallery__trigger {
	display: none;
}

/* ============================================================================
 * The gallery slides
 *
 * ⚑ Keith, 15 Nov 2026: "can it be done in a slider format instead … so the page wont keep
 * getting longer when more media is uploaded". Measured first: four photographs and a video
 * made the column 3698px and the page 5412px, growing 652px per upload.
 *
 * ⚑ EVERY RULE THAT HIDES SOMETHING IS BEHIND `.pg--ready`, which product.js §3 adds. The PHP
 * emits all slides visible and the controls hidden, so with the script blocked this is still
 * the readable column it was before — not one photograph with no way to the rest.
 *
 * ⚠ THE OLD `div.images img` RULE HAD TO BE SCOPED TO `.prod-slide`. It set aspect-ratio 1,
 * object-fit contain and up to 56px of padding on EVERY img inside the gallery — which from
 * today includes the rail thumbnails, where it would have left a 76px button holding a 20px
 * picture. Nothing about the old rule was wrong; it was written when the only img in there was
 * the photograph.
 * ========================================================================== */

.prod-gallery {
	--pg-thumb: 76px;
	--pg-gap: clamp(8px, 1vw, 14px);
	display: block;
	position: relative;
}

/*
 * ⚑ THE RAIL'S COLUMN IS ONLY RESERVED WHEN THERE IS A RAIL. Measured on 15 Nov 2026: with
 * this grid applied to every gallery, the single photograph on the 316 one-image articles went
 * from 652px to 562px — 76px of rail and 14px of gap taken out of a picture with no rail beside
 * it. `prod-gallery--many` is emitted by the PHP, which is the only place that knows.
 */
.prod-gallery--many.pg--ready {
	display: grid;
	grid-template-columns: var(--pg-thumb) minmax(0, 1fr);
	gap: var(--pg-gap);
	align-items: start;
}

/* ---- the stage ---------------------------------------------------------- */

.prod-stage-wrap {
	position: relative;
	min-width: 0;
	grid-column: 2;
	grid-row: 1;
}

/* Before the script: a plain stack, which is what the page has always shown. */
.prod-stage {
	display: grid;
	gap: var(--pg-gap);
	margin: 0;
}

.pg--ready .prod-stage {
	display: block;
	gap: 0;
}

.prod-slide {
	margin: 0;
	overflow: hidden;
	background: var(--card);
	border-radius: var(--rad);
}

.pg--ready .prod-slide {
	display: none;
}

.pg--ready .prod-slide.is-active {
	display: block;
}

.prod-slide a {
	display: block;
}

/*
 * The cut-out-on-card look the single photograph has always had: `contain`, because a spout
 * cropped at the top of a product page is the one picture the visitor came for, ruined.
 */
.prod-slide img {
	display: block;
	width: 100%;
	aspect-ratio: 1;
	object-fit: contain;
	padding: clamp(20px, 4vw, 56px);
}

/*
 * ⚑ A VIDEO SLIDE IS THE SAME BOX AS A PHOTOGRAPH SLIDE, and the clip letterboxes inside it.
 * The first version let the file decide its own height, which is right in isolation and wrong
 * in a slider: measured on C36917, whose installation clip is 1920x1080, the column went
 * 562px, 562px, 316px as you stepped along it — a 246px jump in the middle of the gallery, on
 * a column that is `position: sticky` beside a summary twice its length. Every slide holding
 * the same box is what makes stepping through the gallery feel like one object rather than
 * three.
 *
 * `contain` on a dark ground rather than `cover`: an installation video cropped to a square
 * loses the ends of the shot, and these clips are the one place the client shows how the thing
 * is fitted. No padding — the 56px that flatters a cut-out tap on a card would letterbox a
 * letterbox.
 */
.prod-slide--video {
	aspect-ratio: 1;
	background: var(--ink);
}

.prod-video {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: contain;
	border-radius: var(--rad);
	background: var(--ink);
}

/* ---- the arrows --------------------------------------------------------- */

.prod-nav {
	display: none;
	position: absolute;
	right: clamp(12px, 1.4vw, 18px);
	bottom: clamp(12px, 1.4vw, 18px);
	gap: 8px;
	z-index: 2;
}

.pg--ready .prod-nav {
	display: flex;
}

/*
 * ⚑ THE ARROWS LIFT CLEAR OF A VIDEO'S OWN CONTROLS. product.js §3 adds `pg--video` when the
 * slide showing is a clip; without this the Next arrow sits on top of the scrubber, and the
 * one place a visitor must be able to press accurately is the one we covered.
 */
.pg--video .prod-nav {
	bottom: calc(clamp(12px, 1.4vw, 18px) + 46px);
}

.prod-nav-btn {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 38px;
	height: 38px;
	padding: 0;
	border: 1px solid var(--line);
	border-radius: 50%;
	background: var(--paper);
	color: var(--ink);
	cursor: pointer;
	transition: background .18s ease, color .18s ease, border-color .18s ease;
}

.prod-nav-btn:hover,
.prod-nav-btn:focus-visible {
	background: var(--ink);
	color: var(--paper);
	border-color: var(--ink);
}

/* ---- the rail ----------------------------------------------------------- */

.prod-rail {
	display: none;
}

.pg--ready .prod-rail {
	display: flex;
	flex-direction: column;
	gap: var(--pg-gap);
	grid-column: 1;
	grid-row: 1;
	max-height: 100%;
	overflow: auto;
	scrollbar-width: none;
}

.pg--ready .prod-rail::-webkit-scrollbar {
	width: 0;
	height: 0;
}

.prod-thumb {
	position: relative;
	flex: 0 0 auto;
	width: var(--pg-thumb);
	height: var(--pg-thumb);
	padding: 0;
	overflow: hidden;
	border: 1px solid var(--line);
	border-radius: calc(var(--rad) / 2);
	background: var(--card);
	opacity: .62;
	cursor: pointer;
	transition: opacity .18s ease, border-color .18s ease;
}

.prod-thumb img,
.prod-thumb-video {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.prod-thumb-video {
	pointer-events: none;
	background: var(--ink);
}

.prod-thumb:hover,
.prod-thumb:focus-visible,
.prod-thumb.is-active {
	opacity: 1;
}

.prod-thumb.is-active {
	border-color: var(--ink);
}

/* The play badge, so a first frame is not mistaken for a photograph. */
.prod-thumb-play {
	position: absolute;
	inset: 0;
	margin: auto;
	width: 22px;
	height: 22px;
	border-radius: 50%;
	background: rgba(20, 18, 15, .62);
	pointer-events: none;
}

.prod-thumb-play::after {
	content: "";
	position: absolute;
	inset: 0;
	margin: auto;
	width: 0;
	height: 0;
	border-style: solid;
	border-width: 5px 0 5px 8px;
	border-color: transparent transparent transparent #fff;
	transform: translateX(1px);
}

/* ============================================================================
 * Click to enlarge
 *
 * Keith, 4 Nov 2026: the client clicked a photograph, left the site for a bare .jpg, and had
 * to press Back. The overlay is be.Bold's, ported — see product.js §2 for what was changed on
 * the way across and why.
 *
 * `is-zoomable` is added by the script, so the cursor only ever promises something that will
 * actually happen. The overlay itself is built on first click and is absent from the DOM
 * until then.
 * ========================================================================== */

.woocommerce div.product div.images.is-zoomable a {
	cursor: zoom-in;
	display: block;
}

.pzoom {
	position: fixed;
	inset: 0;
	z-index: 200;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: clamp(20px, 4vh, 56px);
	background: rgba(20, 18, 15, .93);
	/* The zoomed image is larger than this box on purpose; without this it spills over the
	   page behind. */
	overflow: hidden;
}

.pzoom[hidden] {
	display: none;
}

/*
 * The photograph fills whatever is left after the padding and no more. Bounds on BOTH axes
 * rather than `max-width:100%` alone, so a portrait on a short window is held by the height
 * and a landscape on a narrow one by the width, with no arrangement that overflows either.
 *
 * ⚑ `background` AND `padding`, UNLIKE be.Bold'S. These are cut-out articles on white: on the
 * near-black backdrop an unpadded chrome tap would sit in a hard white rectangle with its own
 * edge, which reads as a broken image rather than a photograph. The card ground from the page
 * behind carries over instead, so the enlarged view is the same object, bigger.
 */
.pzoom__img {
	display: block;
	width: auto;
	height: auto;
	max-width: 100%;
	max-height: 100%;
	object-fit: contain;
	background: var(--card);
	border-radius: var(--rad);
}

.pzoom__close {
	position: absolute;
	top: clamp(14px, 2vh, 26px);
	right: clamp(14px, 2vw, 26px);
	display: flex;
	align-items: center;
	justify-content: center;
	width: 44px;
	height: 44px;
	padding: 0;
	background: none;
	border: 0;
	color: var(--cream);
	cursor: pointer;
	border-radius: 50%;
	transition: background .25s var(--ease);
}

.pzoom__close:hover,
.pzoom__close:focus-visible {
	background: rgba(252, 251, 248, .16);
}

/*
 * ⛑ THE SECOND STEP: FIT, THEN THE PHOTOGRAPH'S OWN PIXELS. The zoomed image leaves the flex
 * centring and is positioned against the whole overlay, so it can use the padding too — that
 * padding exists to frame a fitted picture, not to spend screen on a zoomed one.
 *
 * No transition on the transform: panning follows the pointer, and an eased transform turns
 * direct manipulation into something that lags behind the hand.
 */
.pzoom.can-zoom .pzoom__img {
	cursor: zoom-in;
}

.pzoom.can-zoom.is-zoomed .pzoom__img {
	cursor: zoom-out;
}

.pzoom.is-zoomed .pzoom__img {
	position: absolute;
	left: 50%;
	top: 50%;
	max-width: none;
	max-height: none;
	border-radius: 0;
}

.pzoom__img:focus-visible {
	outline: 2px solid var(--cream);
	outline-offset: 3px;
}

/* The affordance, shown only where there is something to zoom into — the same rule the cursor
   follows. On today's 1000px originals a large monitor shows neither, which is correct. */
.pzoom__hint {
	position: absolute;
	left: 50%;
	bottom: clamp(12px, 2.4vh, 26px);
	transform: translateX(-50%);
	margin: 0;
	padding: 7px 15px;
	border-radius: 999px;
	background: rgba(20, 18, 15, .62);
	color: var(--cream);
	font-size: .72rem;
	font-weight: 600;
	letter-spacing: .1em;
	text-transform: uppercase;
	pointer-events: none;
	opacity: 0;
	transition: opacity .2s ease;
}

.pzoom.can-zoom .pzoom__hint {
	opacity: 1;
}

@media (prefers-reduced-motion: reduce) {
	.pzoom__hint,
	.pzoom__close {
		transition: none;
	}
}

/* The page behind is inert while the overlay is up; without this it scrolls under the
   backdrop. */
body.has-pzoom {
	overflow: hidden;
}

/* ============================================================================
 * The summary column
 * ========================================================================== */

.woocommerce div.product div.summary {
	width: auto;
	float: none;
	margin: 0;
}

.woocommerce div.product .pdp__series {
	margin: 0 0 14px;
	font-size: 11px;
	letter-spacing: .22em;
}

.pdp__series a {
	color: inherit;
}

.pdp__series a:hover {
	color: var(--ink);
}

/* ⚑ 38px WRAPPED EVERY COLLECTION NAME ONTO TWO LINES. Client, 30 Oct 2026: "this text is
   very big can it be smaller". Brought to the step the client already chose for the Contact Us
   heading on 6 Oct, so the page uses a size the system already has rather than a new one.

   ⚑ AND THE SECTION HEADINGS BELOW CAME DOWN WITH IT, which is the half nobody asked for. The
   product name is an h1 and `.t-sec` reaches 42px, so the title was ALREADY the smaller of the
   two; shrinking it alone would have left the article name visibly subordinate to "The rest of
   the Line Collection" underneath it. Fixing one complaint by making a worse one is not a fix.
   The sections keep their own scale everywhere else on the site — this is scoped to the
   product page. */
.woocommerce div.product .product_title {
	font-size: clamp(21px, 2.2vw, 30px);
	font-weight: 200;
	line-height: 1.18;
	letter-spacing: .01em;
	margin: 0;
	padding: 0;
	color: var(--ink);
}

.pdp__sku {
	margin: 14px 0 0;
	font-size: 13px;
	color: var(--taupe);
	font-variant-numeric: tabular-nums;
	letter-spacing: .06em;
}

/* ⚑ --taupe, NOT --stone-2, AND THE REASON IS THE SAME ONE AS THE FILTER PANEL. --stone-2 is
   Pantone 406, a rule-and-swatch colour: as 10.5px type it measures 1.57:1 on --paper and
   1.73:1 on --card, against the 4.5:1 AA asks for. These three labels — the article number,
   the finish heading and the documents heading — were all set in it, which is why the product
   page read as a page of missing words. --taupe is 4.62:1 / 5.10:1 and keeps them secondary to
   the content beside them, which is what the colour was reaching for.

   Only the hand-written files are changed. The GENERATED page sheets use --stone-2 as type in
   several places too, and those came out of mockups the client signed off — on the board for
   them to decide, not something to change here. */
.pdp__sku-label {
	font-size: 10.5px;
	font-weight: 500;
	letter-spacing: .2em;
	text-transform: uppercase;
	color: var(--taupe);
	margin-right: 8px;
}

/* ⚑ 13px, NOT 15px — THE SAME SIZE AS THE ARTICLE NUMBER ABOVE IT. Client, 3 Nov 2026:
   "Product description should not be so big vs the code numbers." Measured before changing
   anything: the description was 15px against .pdp__sku's 13px and .pdp__sku-label's 10.5px,
   so the secondary text under the title was the LARGEST thing in that column after the
   title itself, and read as the heading of the block rather than a note beside it.

   The line-height comes down with it. 1.85 was set for 15px; left alone at 13px it opens the
   paragraph up and undoes half of what the size change is for. */
.woocommerce div.product .woocommerce-product-details__short-description {
	margin: 22px 0 0;
	font-size: 13px;
	line-height: 1.75;
	color: var(--taupe);
}

.woocommerce div.product .woocommerce-product-details__short-description ul {
	margin: 1em 0 0;
	padding-left: 1.1em;
}

.woocommerce div.product .woocommerce-product-details__short-description li {
	margin-bottom: .45em;
}

/* ============================================================================
 * Finish selector
 * ========================================================================== */

.pdp__fin {
	margin-top: 28px;
	padding-top: 24px;
	border-top: 1px solid var(--line);
}

.pdp__fin-head,
.pdp__docs-head {
	margin: 0 0 14px;
	font-size: 10.5px;
	font-weight: 500;
	letter-spacing: .2em;
	text-transform: uppercase;
	color: var(--taupe);
}

.pdp__fin-name {
	margin-left: 10px;
	letter-spacing: .06em;
	text-transform: none;
	font-size: 13px;
	font-weight: 400;
	color: var(--taupe);
}

.pdp__fin ul {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	gap: 12px;
	flex-wrap: wrap;
}

/* The swatch itself is .fswatch, defined once in theme.css so the grid and the product page
   cannot render the same finish as two different metals. Only the button reset and the
   selected state belong here. */
.pdp__fin .fswatch {
	width: 30px;
	height: 30px;
	padding: 0;
	cursor: pointer;
	appearance: none;
}

.pdp__fin .fswatch.is-on {
	box-shadow: 0 0 0 1px var(--paper), 0 0 0 2px var(--ink);
}

/* ============================================================================
 * Technical documents
 * ========================================================================== */

.pdp__docs {
	margin-top: 26px;
	padding-top: 24px;
	border-top: 1px solid var(--line);
}

.pdp__docs ul {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
	gap: 10px;
}

/* A finish with no datasheet of its own hides that row; product.js sets the attribute. Nothing
   sets `display` on these items today, so the UA rule is enough — this is here because the
   attribute silently losing to a later `display` is how the site search and the cart drawer
   both broke, and the two lines are cheaper than finding it a third time. */
.pdp__docs li[hidden] {
	display: none;
}

.pdp__docs a {
	font-size: 14px;
	color: var(--ink);
	border-bottom: 1px solid var(--line);
	padding-bottom: 3px;
	transition: border-color .3s var(--ease);
}

.pdp__docs a:hover {
	border-color: var(--ink);
}

/* ============================================================================
 * Call to action
 * ========================================================================== */

.pdp__cta {
	margin: 30px 0 0;
}

.woocommerce div.product .pdp__cta .pill {
	font-size: 12px;
}

/* ============================================================================
 * Specification and the rest of the series
 * ========================================================================== */

.pdp__desc {
	margin-top: clamp(56px, 7vw, 104px);
	border-top: 1px solid var(--line);
	padding-top: clamp(40px, 5vw, 72px);
}

.pdp__desc .t-sec,
.pdp__more .t-sec {
	margin-bottom: 26px;
	font-size: clamp(19px, 2vw, 26px);
}

.pdp__desc-body {
	max-width: 68ch;
	font-size: 15px;
	line-height: 1.85;
	color: var(--taupe);
}

.pdp__desc-body ul {
	padding-left: 1.1em;
}

.pdp__desc-body li {
	margin-bottom: .5em;
}

.pdp__desc-body a {
	color: var(--ink);
	border-bottom: 1px solid var(--line);
}

.pdp__more {
	margin-top: clamp(48px, 6vw, 88px);
}

.pdp__more .head {
	margin-bottom: clamp(24px, 3vw, 42px);
}

/* The series strip reuses the archive's grid, at four across. .products is styled in shop.css,
   which is NOT loaded here — so the few rules it needs are repeated, deliberately and visibly,
   rather than loading a whole archive stylesheet on every product page. */
.pdp__more ul.products {
	list-style: none;
	margin: 0;
	padding: 0;
	display: grid;
	grid-template-columns: repeat(4, 1fr);
	gap: clamp(20px, 2.6vw, 36px);
}

.pdp__more ul.products li.product {
	width: auto;
	float: none;
	margin: 0;
	text-align: left;
}

.pdp__more ul.products li.product a img {
	display: block;
	width: 100%;
	aspect-ratio: 1;
	object-fit: contain;
	background: var(--card);
	border-radius: var(--rad);
	padding: 16px;
	margin: 0;
}

.pdp__more ul.products li.product h2 {
	font-size: 15px;
	font-weight: 300;
	margin: 12px 0 0;
	padding: 0;
	color: var(--ink);
}

.pdp__more .pcard__series {
	margin: 12px 0 2px;
	font-size: 10px;
	letter-spacing: .2em;
	color: var(--taupe);
}

.pdp__more .pcard__sku,
.pdp__more .pcard__fin,
.pdp__more .pcard__cta {
	display: none;
}

.pdp__more-all {
	margin: clamp(28px, 3.4vw, 46px) 0 0;
	text-align: center;
}

/* ============================================================================
 * Responsive
 * ========================================================================== */

@media (max-width: 980px) {
	/*
	 * ⚑ THE RAIL GOES UNDER THE PHOTOGRAPH, because beside it there is no room for both. The
	 * product page stacks to one column at this width, so the gallery has the full page to work
	 * with — and the rail was still taking 76px plus the gap out of it. Measured at 390px with
	 * the rail alongside: the photograph came out 262x262, which on the one screen where the
	 * picture IS the page is not a photograph, it is a thumbnail with arrows.
	 *
	 * It is kept rather than hidden, which is where this differs from be.Bold. be.Bold drops the
	 * rail on a phone and lets the stage swipe. Here the rail is the only thing that says a
	 * product HAS a video — the play badge is on the thumbnail, not on the stage — and a
	 * distributor looking for the installation clip would have no way to know it was there.
	 */
	.prod-gallery--many.pg--ready {
		grid-template-columns: minmax(0, 1fr);
	}

	.prod-stage-wrap {
		grid-column: 1;
		grid-row: 1;
	}

	.pg--ready .prod-rail {
		grid-column: 1;
		grid-row: 2;
		flex-direction: row;
		max-height: none;
		overflow-x: auto;
		/* A strip that can be flicked, with each thumbnail coming to rest under the finger. */
		scroll-snap-type: x proximity;
	}

	.prod-thumb {
		scroll-snap-align: start;
	}

	/*
	 * ⚑ display:block, NOT a one-column grid.
	 *
	 * `grid-template-columns: 1fr` left the picture and the summary overlapping by 78px at
	 * 375px — the product title printed across the bottom of the photograph. Between
	 * WooCommerce's own `float:left; width:48%; position:relative` on div.images and a sticky
	 * this file sets at the same specificity, the two items were not landing in separate rows,
	 * and chasing which declaration won was costing more than the layout was worth.
	 *
	 * Two block-level children stacking is what is actually wanted here, it is what `block`
	 * does, and no float or sticky can make two blocks overlap. The margin below replaces the
	 * grid gap the switch gives up.
	 */
	.woocommerce div.product {
		display: block;
	}

	.woocommerce div.product div.images {
		/*
		 * ⚑ `top` HAS TO BE UNSET TOO, NOT JUST `position`.
		 *
		 * The desktop rule is `position: sticky; top: 106px`. Setting only `position: static`
		 * here left the `top` in place — and WooCommerce's own `.woocommerce div.product
		 * div.images { position: relative }` then won the position declaration at equal
		 * specificity, so the gallery was `relative` with `top: 106px` and sat 82px BELOW where
		 * the layout had put it, while the summary stayed where the gallery should have been.
		 * The product title printed across the bottom of the photograph.
		 *
		 * It read exactly like a float bug and was not one: the giveaway was that the overlap
		 * was the SAME number every time, at every width. A float would have varied.
		 */
		position: static;
		top: auto;
		float: none;
		width: auto;
		margin-bottom: clamp(24px, 5vw, 40px);
	}

	/*
	 * ⚑ clear:both, because something inside the gallery still floats.
	 *
	 * With the parent as `block` and both children `float:none`, the summary still began 82px
	 * ABOVE the bottom of the picture — the product title printed across the photograph. Two
	 * static blocks cannot do that, so a float survives somewhere inside the gallery markup
	 * (WooCommerce floats the gallery figures for its own multi-image layout, which this build
	 * never reaches because the gallery features are off).
	 *
	 * Rather than hunt the declaration through woocommerce.css, clear it. `clear` is precisely
	 * the tool for "start below any float, wherever it came from", it costs nothing when there
	 * is no float, and it cannot be undone by a rule this theme has not seen.
	 */
	.woocommerce div.product div.summary {
		clear: both;
	}

	.pdp__more ul.products {
		grid-template-columns: repeat(2, 1fr);
	}
}

@media (max-width: 560px) {
	.pdp__more ul.products {
		grid-template-columns: 1fr;
	}
}


/* ⚑ THESE RULES LIVE HERE, NOT IN shop-system.css, AND THAT COST A ROUND TRIP. The four
 * checkout screens load assets/css/pages/shop-system.css; a product page loads THIS file,
 * because crestial_page_slug() returns 'product' for it. Putting the add-to-cart rules in
 * shop-system.css styled them perfectly on four pages that do not contain an add-to-cart
 * form, and left the form itself raw on all 317 products.
 */

/* ============================================================================
 * The add-to-cart form on a product
 *
 * ⚑ WooCommerce's OWN STYLESHEET IS DEQUEUED on product screens (inc/woocommerce.php), so
 * everything it used to do here is ours — including the parts that were never decoration.
 * The quantity field's <label> is one of them: WooCommerce prints "CRESTIAL Aerator assembly
 * — 08101 quantity" as a real label for screen readers and hides it with `.screen-reader-text`
 * from its own sheet. With the sheet gone it rendered as a line of body copy above the box,
 * on every priced product. Same shape as the Gravity Forms honeypot — see the COMPENSATION
 * note in assets/css/gravityforms.css.
 * ========================================================================== */

.woocommerce div.product form.cart {
	display: flex;
	align-items: center;
	gap: 14px;
	flex-wrap: wrap;
	margin: 26px 0 0;
}

.woocommerce div.product form.cart .quantity label,
.woocommerce .screen-reader-text {
	position: absolute !important;
	left: -9999px !important;
	width: 1px !important;
	height: 1px !important;
	overflow: hidden !important;
}

.woocommerce div.product form.cart .quantity input.qty {
	font: inherit;
	font-size: 15px;
	width: 74px;
	text-align: center;
	color: var(--ink);
	background: var(--cream);
	border: 1px solid var(--line);
	border-radius: 999px;
	padding: 13px 10px;
	transition: border-color .4s var(--ease);
}

.woocommerce div.product form.cart .quantity input.qty:focus {
	outline: none;
	border-color: var(--orange);
}

.woocommerce div.product form.cart button.single_add_to_cart_button {
	font: inherit;
	font-size: 11.5px;
	font-weight: 500;
	letter-spacing: .16em;
	text-transform: uppercase;
	color: var(--cream);
	background: var(--ink);
	border: 1px solid var(--ink);
	border-radius: 999px;
	padding: 15px 32px;
	cursor: pointer;
	transition: background .4s var(--ease), border-color .4s var(--ease);
}

.woocommerce div.product form.cart button.single_add_to_cart_button:hover {
	background: var(--orange);
	border-color: var(--orange);
}

