/*
 * Baseline for the 2026 chrome on the legacy pages.
 *
 * On the 2026 pages the chrome renders on top of Tailwind preflight: every tag
 * starts with no margin, no padding, no list marker and inherited typography,
 * and the component CSS only declares what it actually needs. On a legacy page
 * preflight sits in chrome.css's @layer base, and style-en.css styles p, a, ul
 * and friends with plain tag selectors - a direct declaration always beats an
 * inherited one, so the header and footer picked up the legacy font, colours
 * and spacing.
 *
 * With style-en.css moved into @layer legacy (see allot_styles_and_scripts),
 * this file is unlayered and therefore outranks all of it without needing a
 * single !important. It loads before chrome.css, so the component rules that
 * follow still win on top of this baseline - the same relationship they have
 * with preflight on the 2026 pages.
 */
.site-header,
.site-header *,
.site-header *::before,
.site-header *::after,
.site-footer,
.site-footer *,
.site-footer *::before,
.site-footer *::after {
  box-sizing: border-box;
  margin: 0;
  padding: 0;
  border: 0 solid;
  border-radius: 0;
  box-shadow: none;
  background: transparent;
  font: inherit;
  color: inherit;
  letter-spacing: normal;
  text-align: inherit;
  text-decoration: none;
  text-transform: none;
  min-width: 0;
  max-width: none;
}

/* preflight drops the marker on lists only, not on every tag. */
.site-header ul,
.site-header ol,
.site-header menu,
.site-footer ul,
.site-footer ol,
.site-footer menu {
  list-style: none;
}

/* The typography the 2026 body rule would have provided, colour included -
   otherwise the chrome inherits the legacy body colour (#212529). */
.site-header,
.site-footer {
  font-family: var(--font-primary);
  font-size: 1rem;
  font-weight: 400;
  line-height: 145%;
  /* Fallback is not decoration: Tailwind 4 drops theme tokens nothing in the
     bundle references, and chrome.css uses no text-text-body utility, so the
     custom property genuinely does not exist here. Without the literal the
     var() is invalid at computed-value time and colour falls back to the
     legacy body's #212529. Upstream fix would be `@theme static` in
     base/tokens.css so the token is always emitted. */
  color: var(--color-text-body, #454545);
}

/* preflight's media defaults, which the logos and icons rely on. */
.site-header img,
.site-header svg,
.site-footer img,
.site-footer svg {
  display: block;
  max-width: 100%;
  height: auto;
}