/* On production, itself carries the dark background (it's the * true page root there). Our .newsite-scope wrapper sits one level * *inside* body instead (so the scoping trick doesn't leak onto the * rest of the legacy site), which left the real transparent. * That's harmless while a section is covering the full viewport, but * once .hero-base-auto/section boundaries scroll past the fixed * header, whatever's below shows through instead of a solid backdrop * -- which reads as page content "colliding" with the header text. * Hardcoding the same color here (not by var(), since --bg--black is * only defined inside .newsite-scope) fixes it for every ported page. */ /* normalize.css's "html, body { margin: 0; }" reset was scoped to * ".newsite-scope { margin: 0; }" along with everything else (see the * html/body/:root special-casing note in the migration docs), which * left the real tag still carrying the browser's default 8px * margin on all four sides. Harmless-looking on its own, but it made * every ported page's main content and footer render ~16px narrower * than production at any given viewport width (the fixed-position * header is unaffected, since fixed elements are positioned against * the viewport, not body -- so the header lined up fine while * everything below it didn't, which is what made this noticeable). */ body { margin: 0; background-color: #030304; } /* Header/nav are transparent at rest by design (lets the hero background * bleed up behind the logo at the very top of the page, matching * production). On production, page content never actually reaches the * header because every section has its own generous top spacing -- * that's not guaranteed on a page that's just a long list of rows * (e.g. media.html's 57 press-mention entries), so a row can end up * scrolled to exactly behind the header with nothing to hide it. * nav.js toggles this class once window.scrollY > 4px. */ .newsite-scope .header.header--scrolled { background-color: #030304; } /* Small corrections on top of the ported new-site CSS. * * The live site's actual boilerplate includes an inline Webflow reset * (`a, .w-dropdown-btn, .w-dropdown-toggle, .w-dropdown-link { color: * inherit; text-decoration: inherit; font-size: inherit; }`) that our * copied components.css/superantispyware-dev.css don't carry, since we * only extracted the