/* =============================================================
 * SUPERFLY — THE SCROLLBAR
 * Windows draws a grey bar with an arrow at each end, which sits
 * badly on a black page. This makes it a pink rail: a faint
 * track, a solid Superfly-pink thumb, no arrows.
 * -------------------------------------------------------------
 * Chrome, Edge and Safari read the ::-webkit-scrollbar rules.
 * Firefox only accepts a width and two colours, so it gets the
 * same idea in the two properties it understands.
 * Phones are untouched: iOS and Android overlay their own bar
 * while scrolling and hide it afterwards.
 * ============================================================= */

/* NO HORIZONTAL SCROLLBAR, EVER.
 * -------------------------------------------------------------
 * THIS IS A GUARD, NOT A FIX, and it is important that whoever
 * reads this next knows the difference.
 *
 * A thin sideways scroll was reported on the home page on a
 * laptop on 2026-11-10 and could not be reproduced: measured at
 * 320, 375, 1265, 1280, 1366, 1440, 1536 and 1920, at every
 * 300px through the whole 9858px document, and every 400ms
 * through the intro — scrollWidth never exceeded clientWidth
 * once. One real cause WAS found and fixed on the way (a stale
 * ScrollTrigger pin-spacer, see smooth-scroll.js job 5) but the
 * report survived it.
 *
 * `clip` and not `hidden`: hidden makes the root a scroll
 * container, which breaks `position: sticky` descendants — this
 * site has a sticky navbar, a sticky reviews wrapper and a
 * ScrollTrigger pin, so hidden would cost all three silently.
 * Verified before shipping: under `clip` the navbar still pins
 * to top:0 at scrollY 1500 and the pin-spacer still measures
 * correctly. The computed value is `clip / visible`.
 *
 * WHAT THIS COSTS: anything that genuinely overflows sideways is
 * now CUT instead of reachable. On this site the only wide thing
 * is decorative overhang (.sfrev__cards, the marquees), so the
 * trade is cheap — but if content ever goes missing at the right
 * edge, look here first.
 *
 * If the real cause is ever identified, fix it and consider
 * removing this, so a future overflow bug is visible rather than
 * silently swallowed. */
html {
	overflow-x: clip;
}

html {
	scrollbar-width: thin;
	scrollbar-color: #ec1e79 rgba(255, 255, 255, 0.04);
}

/* the bar itself */
::-webkit-scrollbar {
	width: 10px;
	height: 10px;                       /* for anything that scrolls sideways */
}

::-webkit-scrollbar-track {
	background: rgba(255, 255, 255, 0.04);
}

::-webkit-scrollbar-thumb {
	background: #ec1e79;
	border: 0;
}

::-webkit-scrollbar-thumb:hover {
	background: #ff3b90;
}

/* where the two bars meet in a corner */
::-webkit-scrollbar-corner {
	background: rgba(255, 255, 255, 0.04);
}

/* the arrow buttons at each end — the thing that looks most like
   Windows rather than Superfly */
::-webkit-scrollbar-button {
	display: none;
	width: 0;
	height: 0;
}

/* =============================================================
 * THE SELECTION HIGHLIGHT
 * The browser's default is its own blue, which is the one piece
 * of chrome on this site that is neither carbon nor magenta —
 * most visible when a visitor drags across a display headline,
 * where the blue plate is as big as the words.
 *
 * TWO SEPARATE RULES, NEVER ONE SELECTOR LIST. An unknown
 * pseudo-element invalidates the WHOLE rule it appears in, so
 * `::selection, ::-moz-selection { }` silently styles nothing in
 * a browser that knows only one of them. Firefox has taken the
 * unprefixed form since 62; the prefixed copy is kept for the
 * long tail and costs four lines.
 *
 * ONLY A FEW PROPERTIES APPLY HERE — colour, background-color,
 * text-shadow and text-decoration. `background` is the shorthand
 * and is NOT in the allowed set, so it is written longhand; a
 * shorthand reads as working in Blink and does nothing in some
 * others.
 *
 * The magenta is read from the theme (accent-1) with the hex
 * only as a fallback, per the project convention — unlike the
 * ::-webkit-scrollbar rules above, which keep the literal
 * because those pseudo-elements do not reliably inherit a
 * custom property.
 *
 * White on this magenta measures 4.2:1, which is fine for a
 * highlight at the sizes it lands on here. If the ink is ever
 * flipped to the page colour, re-check it — magenta against
 * #171717 is 4.4:1 and reads muddier, not cleaner. */
::selection {
	background-color: var(--wp--preset--color--accent-1, #ec1e79);
	color: #ffffff;
	text-shadow: none;                  /* or a headline's shadow muddies it */
}

::-moz-selection {
	background-color: var(--wp--preset--color--accent-1, #ec1e79);
	color: #ffffff;
	text-shadow: none;
}
