/* Legacy compatibility layer. * Canonical global primitives are owned by assets/css/design-system.css. * Rules retained here are restricted to existing body/page/component hooks. */ /* Canonical Liquid Glass dark palette tokens */ :root { --hq-dark-bg: #0b0a0a; /* neutral charcoal */ --hq-dark-rgb: 11, 10, 10; } /* ===================== scoped shell stacking compatibility ===================== */ /* ============================================================================ PART 1 — Z-INDEX CLIP FIX (mega-menu + header clipped BEHIND page content) ---------------------------------------------------------------------------- DIAGNOSIS (verified via CDP getComputedStyle + elementFromPoint): The whole nav chrome lives INSIDE
: header#masthead └ nav#hq-main-nav position:fixed; z-index:50 ├ #mega-menu-dropdown position:absolute; z-index:40 (Index panel) └ #hq-acct-menu position:absolute; z-index:40 (account panel) └ #mobile-menu / #search-modal (full-screen overlays) _foundation.css added `main, header, footer{ position:relative; z-index:1 }` (so the hero canvas .hq-hero-lanes at z:0 can sit under content). That pins BOTH
AND
at the SAME z-index:1, as sibling stacking contexts inside #page (z:10). With equal z-index the LATER element in the DOM wins, and
comes after
— so main's content paints OVER the entire header subtree, burying the fixed nav (z:50) and the mega-menu panel (z:40). CDP proof: with the panel open, elementFromPoint at the panel's centre returned a content

, not the panel. FIX: lift the header's OWN stacking context above content (z:60), and give the nav + dropdown panels an explicitly high z-index so nothing traps them. The hero canvas (.hq-hero-lanes, fixed z:0) is untouched and stays BELOW content. ============================================================================ */ /* (a) Un-trap the header stacking context — this is THE fix. The header wrapper must outrank

/