/* Corrections that every page wearing the site chrome over the theme's core.css needs.

   Loaded immediately after landing-chrome.css by _AdminSNEATAuth (sign-in and the seven other auth
   views) and by _Legal (/terms, /privacy). Those layouts keep core.css — their content is built
   from Bootstrap components — and take the public navbar and footer as .lp-chrome-scoped rules
   generated from the design prototype. landing-chrome.css is generated by tools/landing-port and is
   overwritten on every re-port, so nothing here may live in it.

   These rules started life at the foot of auth-skin.css, where they served the sign-in pages alone.
   They moved here on 2026-09-13 when the legal pages took the same chrome and immediately showed
   the first bug below — a squeezed navbar with the wordmark touching the first link. A fix that two
   layouts need does not belong in one layout's card stylesheet.
   -------------------------------------------------------------------------------------------- */

/* 1. Bootstrap also defines .navbar, and the shared header carries that class because the design
      prototype's markup does. The scoped landing rule sets only position/top/left/right/z-index,
      so Bootstrap's `display: flex` and padding come through — which turns .nav-container into a
      flex item that shrinks to its content (1128px instead of its 1220px max-width) and leaves the
      logo touching the first nav link. */
.lp-chrome .navbar {
  display: block;
  flex-wrap: nowrap;
  padding: 0;
}

/* 2. The page is a flex column so the footer sits at the foot of a short page instead of half way
      up it, and so a tall one still pushes it below the content. The layouts mark their own main
      block (.auth-wrapper, .legal-wrapper) `flex: 1 0 auto` to take the slack.

   3. The ambient blobs are absolutely positioned past the viewport edges by design. landing.css
      contains them with `body { overflow-x: hidden }`; core.css has no such rule, so on these
      pages they produced a real horizontal scrollbar. */
body {
  overflow-x: hidden;
  display: flex;
  flex-direction: column;
  min-height: 100vh;
}

/* The language switcher names every language in its own script (हिन्दी, ภาษาไทย, རྫོང་ཁ ...), on every
   page. In the text stacks those names would pull each self-hosted script face - about 1.3 MB, the
   Tibetan one alone 731 KB - into every visit, English included, defeating the unicode-range
   scoping in landing-fonts.css. Rendered in the system stack they cost nothing, and every OS a
   reader of that language uses ships a face for its own script. 2026-09-26. */
.lp-chrome .lang-dropdown .lang-option {
  font-family: system-ui, -apple-system, "Segoe UI", Roboto, sans-serif;
}