/*
 * Global site header — shared template part (parts/header.html).
 * WP-01C-R4: superficie dark (--smq-navy-950), la misma que L001/Hero — Header y Hero comparten
 * literalmente el mismo token de fondo para leerse como una única superficie de marca continua,
 * sin franja blanca ni borde separador entre ambos.
 * WP-01C-R5: causa raíz de las franjas blancas laterales identificada -- el fondo estaba en
 * `.smq-site-header`, que es también el contenedor CONSTREÑIDO (`width: min(1440px, ...)`,
 * `margin-inline: auto`). El `<header>` real (tagName del wp:template-part que envuelve esta
 * plantilla en cada página) no tenía ningún estilo propio -- a ancho completo y transparente,
 * dejaba ver el blanco de `body` a los lados en cualquier viewport donde el contenedor
 * constreñido no llegara al borde. Fix: la superficie (fondo/color) pasa al elemento `header`
 * (full-width por naturaleza, sin necesidad de 100vw/tricks); `.smq-site-header` deja de pintar
 * superficie propia y solo aporta layout/alineación del contenido interior, exactamente con el
 * mismo ancho/gutter de siempre. Selector de elemento (`header`), no una clase nueva, porque solo
 * existe un `<header>` de sitio por página -- no hace falta tocar los 4 templates que llaman al
 * template-part para lograrlo.
 * Mobile hamburger/overlay behaviour is core WordPress Navigation block functionality
 * (overlayMenu:"mobile") — no custom JS is introduced here.
 * WEB-INTEGRATION-03C.1: the same core overlay also serves as the compact header between 600px and the
 * desktop breakpoint. WEB-V1-HEADER-RESPONSIVE-V2 sets that breakpoint at 1260px (measured, see the RESPONSIVE
 * CONTRACT block at the end of this file) and turns the open overlay into a right-hand drawer.
 */
header {
	background: var(--smq-navy-950);
	color: var(--smq-white);
}
.smq-site-header {
	display: flex;
	align-items: center;
	justify-content: space-between;
	flex-wrap: wrap;
	gap: var(--smq-space-5);
	width: min(1440px, calc(100% - 48px));
	margin-inline: auto;
	padding: var(--smq-space-4) 0;
	font-family: var(--smq-font-text);
}

/* Logo lockup — assets/images/logo-cropped.png (transparent background, ~4.96:1 aspect ratio),
   copied verbatim from content/campaigns/public-launch-kit/assets/logo-cropped.png, sin ningún
   filtro/recolor/caja. Renders at its own aspect ratio via height + width:auto.
   WP-01C-R4: el header pasa a superficie dark (--smq-navy-950), la misma que este asset ya
   asume (wordmark blanco) — se retira por completo la técnica de contorno por drop-shadow de R3,
   que era un workaround exclusivamente para el header claro y deja de tener sentido. El logo
   conserva exactamente sus colores originales, sin ninguna manipulación CSS. */
.smq-site-header .smq-brand-logo {
	margin: 0;
	flex-shrink: 0;
}
.smq-site-header .smq-brand-logo a {
	display: block;
}
.smq-site-header .smq-brand-logo img {
	display: block;
	height: 52px;
	width: auto;
}

.smq-primary-nav {
	font-family: var(--smq-font-text);
	font-size: 0.98rem;
	font-weight: 500;
}
/* WEB-INTEGRATION-03C.1: horizontal item padding 8px -> 6px (font size/weight and item height
   unchanged; "Mi SMQuantum" keeps its own padding below). With the 03C items (Membership, Contacto)
   the full row measured 1140px, leaving 10px spare inside the 1440px header container; at 6px it is
   1108px, a 42px margin (measured with Insights, which has since left the primary menu, Q-04). The desktop
   breakpoint below relies on this padding. */
.smq-primary-nav .wp-block-navigation-item > a,
.smq-primary-nav .wp-block-navigation-item > .wp-block-navigation-item__content {
	color: var(--smq-white);
	text-decoration: none;
	padding: var(--smq-space-1) 6px;
}
.smq-primary-nav .wp-block-navigation-item > a:hover,
.smq-primary-nav .wp-block-navigation-item > a:focus-visible {
	color: var(--smq-blue-interactive);
}

/* "Mi SMQuantum" — WP-01C-R5: acción de acceso a producto/plataforma, no un botón WP genérico.
   Base --smq-blue-interactive-strong (acción; DS-A11Y-01, blanco 5.13:1; regla de discriminación DS-002 03-color-system.md);
   hover --smq-blue-brand (el mismo azul-cian del logo/H1/Magnitudes -- familia "azul tecnológico
   limpio", nunca navy/violeta). Icono de usuario decorativo (aria-hidden, ver parts/header.html)
   + flecha decorativa: el nombre accesible del enlace sigue siendo solo "Mi SMQuantum", sin
   redundancia para lectores de pantalla. Radio moderado (8px), no píldora. */
.smq-primary-nav .smq-nav-account > a {
	display: inline-flex;
	align-items: center;
	gap: var(--smq-space-2);
	color: var(--smq-white);
	background: var(--smq-blue-interactive-strong);
	border-radius: 8px;
	padding: var(--smq-space-2) var(--smq-space-4);
	font-weight: 600;
	transition: background-color 0.15s ease, transform 0.1s ease;
}
.smq-nav-account-icon {
	width: 16px;
	height: 16px;
	flex-shrink: 0;
}
.smq-nav-account-arrow {
	display: inline-block;
	transition: transform 0.15s ease;
}
/* color:white forzado explícitamente en hover/focus -- la regla genérica de arriba
   (.wp-block-navigation-item > a:hover) también coincide con este enlace y pondría el texto en
   blue-interactive, ilegible sobre el propio fondo azul del botón. */
.smq-primary-nav .smq-nav-account > a:hover {
	background: var(--smq-blue-brand);
	color: var(--smq-white);
}
.smq-primary-nav .smq-nav-account > a:hover .smq-nav-account-arrow {
	transform: translateX(2px);
}
.smq-primary-nav .smq-nav-account > a:focus-visible {
	background: var(--smq-blue-brand);
	color: var(--smq-white);
	outline: 2px solid var(--smq-white);
	outline-offset: 2px;
}
.smq-primary-nav .smq-nav-account > a:active {
	transform: translateY(1px);
}
@media (prefers-reduced-motion: reduce) {
	.smq-primary-nav .smq-nav-account > a {
		transition: background-color 0.15s ease;
	}
	.smq-primary-nav .smq-nav-account > a:hover .smq-nav-account-arrow,
	.smq-primary-nav .smq-nav-account > a:active {
		transform: none;
	}
}

/* "Carrito" — WEB-RC1-PREOPEN-P1-FIX-BATCH-01 (P1-CART-ACCESS-MEMBERSHIP-REFUSAL-UX): el camino visible al carrito
   desde cualquier página. Enlace estático a /cart/, sin contador ni bloque de WooCommerce: la cabecera sigue sin
   nada personal y cacheable (commerce-w3-ui A22). Es un enlace de navegación normal (colores heredados de la
   navegación, ya revisados), no un segundo botón. En la navegación en línea (>= 1260px) se ve el icono y el nombre
   "Carrito" queda solo para lectores de pantalla, para no desbordar la cabecera; en el menú desplegable se lee. */
.smq-primary-nav .smq-nav-cart > a {
	display: inline-flex;
	align-items: center;
	gap: var(--smq-space-2);
}
.smq-nav-cart-icon {
	width: 18px;
	height: 18px;
	flex-shrink: 0;
}

/* NAVIGATION & RESEARCH DISCOVERY V1 / V1.1 — dropdown submenus (Research/Formación/Estrategias). All
   open/close, hover, click, keyboard, Escape and focus-return behaviour is native WordPress core
   Navigation block functionality (wp-block-library view script + Interactivity API state, already
   loaded for any wp:navigation block) — nothing custom is added here, only CSS, scoped to
   .smq-primary-nav so no other navigation instance on the site is affected.
   V1.1 fix: core's own wp-includes/blocks/navigation/style.min.css already sets
   `.wp-block-navigation-item{position:relative}` and, for a background-colored navigation (this one
   has backgroundColor:"navy-950"), `.has-background .has-child .wp-block-navigation__submenu-container
   {left:0;top:100%}` on top of a base `position:absolute` — which should anchor each submenu directly
   under its OWN parent item. Sergio's visual review found it rendering detached/left-shifted instead.
   Rather than depend on that chain of cross-file selectors continuing to win the cascade, these rules
   restate the same anchoring explicitly and locally, with higher specificity/later cascade order, so
   the correct position is guaranteed here regardless of core CSS load order or version drift.

   V1.2 diagnosis (Sergio's second review — submenu still not appearing at all, not merely mispositioned):
   a rule-by-rule cascade trace of the ACTUAL rendered output (curl of http://127.0.0.1:8871/, compared
   line-by-line against the live wp-includes/blocks/navigation/style.min.css) found the visibility/reveal
   mechanism itself intact and unmodified by this file — core's own
   `.has-child:not(.open-on-click):hover>.wp-block-navigation__submenu-container{opacity:1;visibility:
   visible;height:auto;width:auto;overflow:visible}` (specificity 0,5,0) already outranks the collapsed
   base state (0,3,0), the submenu IS a direct child of its `.has-child` `<li>` so the `>` combinator
   matches, no ancestor between the submenu and the viewport sets overflow:hidden/clip or pointer-
   events:none, and no other loaded stylesheet (site.css, tokens.css, WooCommerce's 3 stylesheets) touches
   navigation/submenu selectors at all. No CSS logic defect was found in this trace.

   What WAS found and fixed in V1.2 first pass: `smquantum-theme/style.css`'s `Version` header (the
   cache-busting query string every theme stylesheet is enqueued with) had not been incremented since
   before this entire project phase. That fix (0.4.0 -> 0.4.1) was correct and necessary, but Sergio
   retested and the submenu still did not appear — proving cache was not the complete root cause.

   V1.2 RUNTIME ROOT CAUSE (proven via real headless-browser interaction — Chrome DevTools Protocol
   driving actual Edge, real Input.dispatchMouseEvent onto the Research item, getComputedStyle() read
   before/after): the reveal mechanism (opacity/visibility/height/width/overflow) was NEVER broken — a
   real hover correctly flips it to visible. The actual defect is POSITION, and the V1.1 "fix" above
   never took effect at all: this nav has `layout:{justifyContent:"right"}`, which core renders as the
   `items-justified-right` class, and core ships its OWN, much more specific override for exactly that
   case:
     .wp-block-navigation.items-justified-right .wp-block-navigation__container .has-child
       .wp-block-navigation__submenu-container { left: auto; right: 0 }
   That selector is 5 class-selectors deep (specificity 0,5,0). The rule below it, before this fix, was
   only `.smq-primary-nav .wp-block-navigation__submenu-container` — 2 class-selectors (0,2,0). Core's
   `right:0` rule always won, silently. Measured live: computed `left: -100.562px`, `z-index: 2` (core's
   base `.has-child .submenu-container{z-index:2}`, 0,3,0, also beat our old `z-index:100` at 0,2,0) —
   the submenu was rendering ~100px to the LEFT of "Research", right-edge-anchored to a 99px-wide
   trigger with a ~200px-wide panel, overlapping neighbouring nav items instead of appearing directly
   below its own parent. This is exactly what a real visual reviewer would report as "the dropdown
   doesn't appear" even though, technically, *a* dropdown was rendering somewhere else on the bar.

   Fix: raise this selector's specificity past core's 0,5,0 by mirroring its own DOM-chain shape (nav >
   container > has-child item > direct-child submenu) instead of relying on `.smq-primary-nav` alone,
   and scope it to the same >=600px breakpoint core itself uses to switch from the mobile modal to the
   horizontal bar — so this NEVER competes with core's separate `.is-menu-open ... {position:static}`
   mobile-overlay rule (which has its own, different specificity and must keep winning on mobile).

   V1.3 VISUAL PAINT ROOT CAUSE (real-browser screenshots via CDP, before/after hover): the submenu WAS
   opening and painting in the right place — it visibly covers the Hero's SG-01 blue line
   (`svg.smq-sg01`, z-index:0) under "Research" — but it was invisible as a surface. Because the nav block
   declares backgroundColor/textColor "navy-950"/"white", core stamps every submenu container with the
   preset classes `has-navy-950-background-color has-white-color`, whose global-styles rules are
   `!important`. That silently beat the `background: white` below (panel computed rgb(11,15,25), the same
   navy as Header and Hero), while the link rule forced `color: navy-950` directly on each <a> — navy text
   on a navy panel, contrast 1:1. Same link rule also blanked the submenu children in the mobile overlay.
   Fix: a dark panel that belongs to the Header (navy-900 + navy-700 border, existing tokens) — the
   `!important` is the only way to outrank core's `!important` preset class and is confined to the
   >=600px desktop rule — and white link text everywhere (17.3:1 on navy-900). Hover/focus keeps the text
   white on navy-700 with a blue-interactive accent bar: blue-interactive text on navy-900 would be
   4.48:1, just under WCAG AA. */
.smq-primary-nav .wp-block-navigation-item.has-child {
	position: relative;
}
/* The horizontal bar starts at 1260px (WEB-V1-HEADER-RESPONSIVE-V2; 1440px in WEB-V1-PRODUCTION-VISUAL-01A, 1488px
   in WEB-INTEGRATION-03C.1, see RESPONSIVE CONTRACT below), so the desktop dropdown panel is scoped to that same
   breakpoint; below it the submenus live in the core overlay and must never receive this absolute positioning. */
@media (min-width: 1260px) {
	.smq-primary-nav.wp-block-navigation .wp-block-navigation__container .wp-block-navigation-item.has-child > .wp-block-navigation__submenu-container {
		position: absolute;
		top: 100%;
		left: 0;
		right: auto;
		margin-top: var(--smq-space-2);
		background: var(--smq-navy-900) !important;
		border: 1px solid var(--smq-navy-700);
		border-radius: 8px;
		box-shadow: 0 12px 32px rgba(0, 0, 0, 0.45);
		padding: var(--smq-space-2) 0;
		min-width: 220px;
		z-index: 100;
	}
	/* V1.4 pointer bridge: the approved 8px visual gap (margin-top) was a dead hover zone — proven with a
	   real slow CDP pointer path, the parent <li> lost :hover at the first pixel below it and core closed
	   the submenu before the pointer reached the panel. This transparent pseudo-element belongs to the
	   submenu (a descendant of the <li>, so hovering it keeps the <li> hovered) and fills exactly the
	   margin + 1px top border, panel-wide. No visible pixels; it inherits the panel's visibility:hidden
	   while closed, so it never catches the pointer over neighbouring items. Core only uses ::before on
	   NESTED submenus, never on this top-level one. */
	.smq-primary-nav.wp-block-navigation .wp-block-navigation__container .wp-block-navigation-item.has-child > .wp-block-navigation__submenu-container::before {
		content: "";
		position: absolute;
		left: 0;
		right: 0;
		bottom: 100%;
		height: calc(var(--smq-space-2) + 1px);
		background: transparent;
	}
	/* Carrito: en la navegación en línea, solo el icono; el nombre queda para lectores de pantalla. */
	.smq-primary-nav .smq-nav-cart-label {
		position: absolute;
		width: 1px;
		height: 1px;
		margin: -1px;
		padding: 0;
		overflow: hidden;
		clip: rect(0 0 0 0);
		white-space: nowrap;
		border: 0;
	}
}
.smq-primary-nav .wp-block-navigation__submenu-container .wp-block-navigation-item > a,
.smq-primary-nav .wp-block-navigation__submenu-container .wp-block-navigation-item > .wp-block-navigation-item__content {
	color: var(--smq-white);
	padding: var(--smq-space-2) var(--smq-space-4);
	display: block;
}
.smq-primary-nav .wp-block-navigation__submenu-container .wp-block-navigation-item > a:hover,
.smq-primary-nav .wp-block-navigation__submenu-container .wp-block-navigation-item > a:focus-visible {
	color: var(--smq-white);
	background: var(--smq-navy-700);
	box-shadow: inset 3px 0 0 var(--smq-blue-interactive);
}
.smq-primary-nav .wp-block-navigation-submenu__toggle {
	color: inherit;
}
/* Native submenu toggle uses aria-expanded, already reflected correctly by WordPress core. */

/* Baseline responsive (WEB-014): 375 / 768 / 1440px */
@media (max-width: 768px) {
	.smq-site-header {
		width: calc(100% - 32px);
		padding: var(--smq-space-3) 0;
	}
}
/* WEB-V1-HEADER-RESPONSIVE-V2 — RESPONSIVE CONTRACT (measured in Chromium with the real assets, header row =
   logo + 32px gap + navigation row, inside a container 48px narrower than the layout viewport; a classic 17px
   desktop scrollbar is counted by the media query but not by the layout):
     >=1400px     the approved bar, unchanged (needs 1316px of container: wraps below 1381px with a scrollbar);
     1260-1399px  the same bar, denser: 40px logo, 0.92rem labels, 4px item padding (needs ~1189px: wraps below
                  ~1237px with a scrollbar; 1271px, the owner's Edge viewport, keeps 34px of slack);
     600-1259px   compact: the core overlay open button (03C.1), the drawer below;
     <600px       core mobile overlay, the same drawer.
   Core only swaps the bar for its overlay below 600px (overlayMenu:"mobile"); between 600px and 1259px this
   re-applies core's own mobile state: show the native open button, keep the closed container hidden. The overlay
   itself (open/close, focus trap, aria, Escape, body scroll lock, reduced motion) stays 100% core; no second
   menu, no custom JS. Specificity: one class above core's two >=600px rules (0,2,0 and 0,3,0). The two compact
   queries are paired with the desktop one (1259/1260): no gap, no overlap. */
@media (min-width: 1260px) and (max-width: 1399px) {
	.smq-site-header .smq-brand-logo img {
		height: 40px;
	}
	.smq-primary-nav {
		font-size: 0.92rem;
	}
	.smq-primary-nav .wp-block-navigation-item > .wp-block-navigation-item__content {
		padding-inline: 4px;
	}
	.smq-primary-nav .smq-nav-account > a {
		padding: 6px 12px;
	}
}
@media (min-width: 600px) and (max-width: 1259px) {
	.smq-primary-nav .wp-block-navigation__responsive-container-open:not(.always-shown) {
		display: flex;
	}
	.smq-primary-nav .wp-block-navigation__responsive-container:not(.hidden-by-default):not(.is-menu-open) {
		display: none;
	}
}
.smq-primary-nav .wp-block-navigation__responsive-container-open {
	color: var(--smq-white);
	border-radius: 8px;
	padding: var(--smq-space-2);
}
.smq-primary-nav .wp-block-navigation__responsive-container-open:hover,
.smq-primary-nav .wp-block-navigation__responsive-container-open:focus-visible {
	background: var(--smq-navy-700);
}

/* COMPACT NAVIGATION DRAWER (all widths below the bar). Core opens its overlay full-screen with the items pushed to
   the right (justifyContent:"right") and every row alike. Here the same overlay becomes a right-hand panel,
   min(400px, 100vw) wide: full width on phones, a drawer on tablets and narrow desktops, with a scrim over the
   page (a spread shadow: it paints, it does not catch clicks — core has no outside-click close, Escape and the
   close button stay core's). Content scrolls inside the panel; core locks the page scroll (html.has-modal-open).
   Hierarchy, without changing a single destination: every top-level entry is a row separated by a hairline; a
   group's own link (Research, Formación, Estrategias, Tecnología) reads as its section label — small, uppercase,
   muted, still a link — and its children as the links; the current page carries the blue accent bar. */
.smq-primary-nav .wp-block-navigation__responsive-container.is-menu-open:not(.disable-default-overlay) {
	left: auto;
	width: min(400px, 100vw);
	padding: 0;
	box-sizing: border-box;
	border-left: 1px solid var(--smq-navy-700);
	box-shadow: 0 0 0 100vmax rgba(3, 6, 12, 0.6);
	max-height: 100dvh;
	overflow-y: auto;
	overscroll-behavior: contain;
}
@media (max-width: 400px) {
	.smq-primary-nav .wp-block-navigation__responsive-container.is-menu-open:not(.disable-default-overlay) {
		border-left: 0;
	}
}
/* ONE scroll container: the drawer itself (fixed, overflow-y auto, never taller than the visible viewport: 100dvh, and
   core's top/bottom 0 where dvh is unknown). Its child never shrinks (flex-shrink 0, min-height left to core's auto):
   core makes the drawer a flex column, and a child allowed to shrink to the drawer's height leaves the menu overflowing
   that child; Chromium still scrolls to it, other engines need not (WEB-V1-HEADER-RESPONSIVE-V2 drawer scroll fix). */
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-close {
	flex-shrink: 0;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-dialog {
	position: relative;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-dialog::before {
	content: "";
	position: absolute;
	top: 72px;
	left: 0;
	right: 0;
	border-top: 1px solid var(--smq-navy-700);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-close {
	top: 16px;
	right: 16px;
	width: 40px;
	height: 40px;
	display: flex;
	align-items: center;
	justify-content: center;
	border-radius: 8px;
	color: var(--smq-white);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-close:hover,
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-close:focus-visible {
	background: var(--smq-navy-700);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-content {
	padding: 88px var(--smq-space-3) calc(var(--smq-space-5) + env(safe-area-inset-bottom, 0px));
	align-items: stretch;
	gap: 0;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__container,
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item {
	align-items: stretch;
	gap: 0;
	width: 100%;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .wp-block-navigation-item {
	border-top: 1px solid var(--smq-navy-700);
	padding-block: var(--smq-space-1);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .wp-block-navigation-item:first-child {
	border-top: 0;
	padding-top: var(--smq-space-2);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item > .wp-block-navigation-item__content {
	display: block;
	padding: 12px var(--smq-space-2);
	border-radius: 6px;
	font-size: 1rem;
	font-weight: 500;
	line-height: 1.4;
	text-align: left;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .wp-block-navigation-item.has-child > .wp-block-navigation-item__content {
	padding-block: 16px 8px;
	font-size: 0.75rem;
	font-weight: 600;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	color: var(--smq-gray-400);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-content .has-child .wp-block-navigation__submenu-container {
	padding: 0 0 var(--smq-space-1);
	min-width: 0;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__submenu-container .wp-block-navigation-item > .wp-block-navigation-item__content {
	padding: 11px var(--smq-space-2);
	font-weight: 400;
	color: var(--smq-gray-200);
}
.smq-primary-nav .is-menu-open .wp-block-navigation-item > .wp-block-navigation-item__content:hover,
.smq-primary-nav .is-menu-open .wp-block-navigation-item > .wp-block-navigation-item__content:focus-visible,
.smq-primary-nav .is-menu-open .wp-block-navigation-item > .wp-block-navigation-item__content[aria-current="page"] {
	color: var(--smq-white);
	background: var(--smq-navy-700);
	box-shadow: inset 3px 0 0 var(--smq-blue-interactive);
}
.smq-primary-nav .is-menu-open .wp-block-navigation-item > .wp-block-navigation-item__content:focus-visible,
.smq-primary-nav .is-menu-open .wp-block-navigation__responsive-container-close:focus-visible {
	outline: 2px solid var(--smq-blue-interactive);
	outline-offset: 1px;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .smq-nav-account {
	padding-top: var(--smq-space-3);
}
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .smq-nav-account > a.wp-block-navigation-item__content {
	display: flex;
	align-items: center;
	justify-content: center;
	gap: var(--smq-space-2);
	padding: 12px var(--smq-space-4);
	font-weight: 600;
	color: var(--smq-white);
	background: var(--smq-blue-interactive-strong);
	box-shadow: none;
}
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .smq-nav-account > a.wp-block-navigation-item__content:hover,
.smq-primary-nav .is-menu-open .wp-block-navigation__container > .smq-nav-account > a.wp-block-navigation-item__content:focus-visible {
	background: var(--smq-blue-brand);
}
@media (max-width: 375px) {
	.smq-site-header {
		gap: var(--smq-space-2);
	}
	.smq-site-header .smq-brand-logo img {
		height: 36px;
	}
}