/* ========================================================================== Burj Trades — WordPress / core-block integration ========================================================================== Everything here exists to make core Gutenberg blocks wear the theme's components. Where a core block can reuse an existing rule, the selector is grouped onto that rule in components.css or pages.css instead of being duplicated here. ========================================================================== */ /* ---- Site shell -------------------------------------------------------- */ .wp-site-blocks { position: relative; z-index: 2; } /* The header template part renders its own
wrapper around the theme's .header. base.css gives `main, header, footer` position:relative and z-index:2, so that wrapper becomes a stacking context at the SAME level as
— and .header's z-index:100 can then only compete inside it. Equal z-index means DOM order decides, so
painted straight over the fixed header: invisible at the top of the page, and unclickable wherever a transparent section let it show through. Raising the wrapper above
restores it. The footer never had the problem because it comes after
in the DOM. The static site never hit this: there, .header *was* the
, so its own position/z-index overrode the rule instead of nesting inside it. */ .wp-site-blocks > header { position: relative; z-index: 100; } /* The open mobile menu must clear everything, including the header itself. */ .wp-block-navigation__responsive-container.is-menu-open { z-index: 120; } /* The header is fixed; push it clear of the admin bar when logged in. */ .admin-bar .header { top: 32px; } @media (max-width: 782px) { .admin-bar .header { top: 46px; } } @media (max-width: 600px) { .admin-bar .header { top: 0; } } /* Core wraps template parts in
/