/* =================================================================
   TimeAdjuster / StockOnHand shared theme overrides
   Include AFTER distribution-design.css and marketplace.css on any
   page that wants the navy/orange portal shell.
   ================================================================= */

/* ── House tokens, re-asserted after marketplace.css ────────────────
   marketplace.css (:195-256) re-declares the whole token ramp so that
   standalone (Layout=null) pages which load ONLY marketplace.css still
   get a complete set. That copy is deliberately kept — deleting it
   would leave ~20 pages (BlastFreezer*, Support, Contact, CreateOrders,
   UserManagement, PODsub, PackagingReceipt, ReturnsDisposal …) with
   `var()` resolving nowhere, and per distribution-design.css:38-46 an
   unresolved var makes the WHOLE declaration invalid at computed-value
   time — a silently missing background or shadow, not a fallback.

   But because marketplace.css is linked after distribution-design.css
   (_Layout.cshtml:12-13) at equal specificity, its values win on the
   ~90 pages that load both. That is why those pages render cream
   (#FFFBF0) rather than the house mint (#eef5f3), and why `--text-mute`
   resolves to rgba(11,47,94,.18) — about 1.4:1 on white, effectively
   invisible.

   This file loads LAST (line 14), so re-asserting the ramp here wins
   the cascade on every page that links it — including the ~25
   standalone pages that link ta-theme.css but not distribution-design.css.
   Values are byte-identical to distribution-design.css:8-58, so pages
   that already load that file render exactly as before; the change is
   confined to the tokens marketplace.css was shadowing.

   Same trick, same reason, as the `.dash-main` padding mirror below. */
:root {
    --bg:        #eef5f3;
    --bg-2:      #e2efeb;
    --surface:   #ffffff;
    --surface-2: #f8fbfb;
    --border:    rgba(11,47,94,.14);
    --border-2:  rgba(245,130,32,.24);
    --text-1:    #0B2F5E;
    --text-2:    #1e3a5f;
    --text-3:    #F58220;
    --text-mute: #7ba8a1;
    --teal:      #F58220;
    --teal-b:    #FF9F4D;
    --teal-d:    #083057;
    --teal-dim:  rgba(245,130,32,.08);
    --teal-grad: linear-gradient(135deg, #F58220 0%, #FF9F4D 50%, #FFD84D 100%);
    --amber:     #d97706;
    --red:       #dc2626;
    --green:     #059669;
    --blue:      #2563eb;
    --orange:    #F58220;
    --pink:      #E4032E;
    --ink-900:   #020617;
    --font-b:    'Roboto', system-ui, -apple-system, sans-serif;
    --font-h:    'Roboto', system-ui, -apple-system, sans-serif;
    --ease:      cubic-bezier(.22,1,.36,1);
    --sh-xs:     0 1px 2px rgba(8,41,37,.05);
    --sh-sm:     0 2px 6px rgba(245,130,32,.07);
    --sh-md:     0 6px 22px rgba(245,130,32,.09);
    --sh-lg:     0 14px 44px rgba(8,41,37,.12);
    --r-sm:      8px;
    --r-md:      12px;
    --r-lg:      18px;
    --r-xl:      24px;

    /* ── Rail engraving (dark face) ──────────────────────────────────
       The side-nav rail's buttons are cut from the navy rail the same way
       the top bar's links are cut from the white bar, but they cannot
       share that recipe, and the three reasons are all silent failures:

       - The `--neu-*` pair is declared in THREE places — distribution-
         design.css:47-53, the layout's own inline <style> (_Layout.cshtml:
         83-89) and PlanningManager.cshtml:57-63. The layout's copy is
         emitted AFTER this file (links at :11-14, the page's Styles at
         :20, that <style> at :22), so redefining those names here would
         lose on source order and do nothing at all.
       - The `--engrave-*` ramp and its `--pressed-dark` live in
         login-shared.css, which exactly one page links (LoginPage.cshtml:
         16) — they resolve nowhere on any page that carries this rail.
       - `--neu-lo` is navy `rgba(11,47,94,…)`. On a navy rail the shade
         would be invisible, so the recipe as written renders as nothing.
         The rail is a DARK face: the shade has to go darker than the
         surface and the highlight has to carry the form. login-shared.css
         :48-50 reached the same conclusion for its navy submit button —
         "a white inset highlight on navy reads as a smudge, so the shade
         and the light swap roles instead".

       Rest → hover grows the geometry, not the alpha, exactly as
       --neu-raised → --neu-raised-hi does, so both bars stay one family. */
    --rail-hi:    rgba(255, 255, 255, 0.30);
    --rail-lo:    rgba(0, 0, 0, 0.45);
    --rail-plate:     -2px -2px 4px var(--rail-hi), 2px 2px 6px var(--rail-lo);
    --rail-plate-hov: -3px -3px 6px var(--rail-hi), 3px 3px 8px var(--rail-lo);
    --rail-pressed:   inset 2px 2px 8px rgba(0, 0, 0, 0.55),
                      inset -2px -2px 5px rgba(255, 255, 255, 0.10);
    --rail-ink:    rgba(255, 255, 255, 0.72);
    --rail-ink-hi: rgba(255, 255, 255, 0.95);
    --rail-inlay:  #F58220;

    /* ── Checkbox engraving (light face) ─────────────────────────────
       New names, not the --neu-* ones. Two reasons, both silent:

       - --neu-* is declared in three places (distribution-design.css:47-53,
         the layout's inline <style> at _Layout.cshtml:83-89, and
         PlanningManager.cshtml:57-63). On TimeAdjuster the page re-links
         distribution-design.css and marketplace.css inside its own Styles
         section (TimeAdjuster.cshtml:11-13), which _Layout renders at :20 —
         AFTER the ta-theme.css link at :14. So re-asserting an existing
         name from this file loses on source order there and does nothing.
         A later :root only overrides the names it declares, so a NEW name
         resolves correctly on both pages.

       - --neu-raised-xs and --rail-plate are calibrated for a 26px pill and
         a 72x64 rail item. At 16px their 2px offsets and 3-8px blurs are
         12-50% of the control's height, which detaches the shade into a
         drop shadow floating under the box rather than depth in it.

       --neu-lo-deep (0.20 navy) rather than --neu-lo (0.15): at this size
       the box needs a deeper shade than a chip-sized plate to read off a
       near-white ground. The HI is kept for family consistency but does
       almost nothing here — every light face on these two pages is within
       ~8 units of white, so --neu-hi measures ~0 lit pixels, the same
       result the top-bar pass recorded. The SHADE carries the form on a
       light face and the HI carries it on navy; that asymmetry is why the
       dark pair below exists at all. */
    --cbx-rest:      -1px -1px 2px var(--neu-hi), 1px 1px 3px var(--neu-lo-deep);
    --cbx-pressed:   inset -1px -1px 2px var(--neu-hi),
                     inset 1px 1px 2px var(--neu-lo-deep);
    --cbx-well:      rgba(11, 47, 94, 0.07);  /* light-face recess wash */
    --cbx-tick:      #c2410c;  /* NOT #F58220 — that is 2.45:1 on the
                                  #fff7f0 checked chip, under the 3:1 a
                                  state graphic needs; #c2410c is the same
                                  orange at a readable weight (4.9:1). */

    /* ── Checkbox engraving (dark face — the navy filter panels) ─────
       Same dark-face swap the rail documents above: the shade has to go
       darker than the surface and the light has to carry the form. The
       geometry is re-derived at 1-2px rather than borrowed from --rail-*,
       whose 6-8px blur is 33-44% of an 18px box. */
    --cbx-dark-rest:  -1px -1px 2px rgba(255, 255, 255, 0.34),
                       1px 1px 2px rgba(0, 0, 0, 0.50);
    --cbx-dark-press: inset 1px 1px 2px rgba(0, 0, 0, 0.55),
                      inset -1px -1px 2px rgba(255, 255, 255, 0.10);
    --cbx-dark-lip:   rgba(255, 255, 255, 0.34);
    --cbx-dark-well:  rgba(0, 0, 0, 0.22);
    --cbx-tick-dark:  #F58220;  /* 5.1:1 on navy — fine on a dark face,
                                   and its mirror image of --cbx-tick. */
}

/* ── Page ground ─────────────────────────────────────────────────────
   Re-asserting --bg is not enough on its own: marketplace.css:67-72
   paints the ground of `.dash-main.mp-theme` from a hardcoded
   `var(--mp-cream)` plus two yellow radial gradients, without ever
   consulting --bg. Leaving that in place would have repainted the
   token ramp while the page stayed visibly cream.

   --mp-cream stays defined and is still correct for marketplace
   component imagery at marketplace.css:376, :424 and :900 — only the
   page ground moves to the house value. Same specificity (0,2,0) as
   the rule it replaces, resolved by load order: this file is last. */
.dash-main.mp-theme {
    background: var(--bg);
}

/* ── Layout shell ───────────────────────────────────────────────── */
.ta-dash-shell { display: grid; grid-template-columns: 84px 1fr; min-height: 100vh; }

/* ── Side-nav rail (icon + label, vertical) ─────────────────────── */
.ta-side-nav {
    width: 84px; min-width: 84px;
    height: calc(100vh - 60px);
    position: sticky; top: 60px;
    display: flex; flex-direction: column;
    align-items: center; gap: 6px;
    padding: 16px 0;
    background: #0B2F5E;
    border-right: 1px solid rgba(245,130,32,.30);
    z-index: 10;
}
/* ── The plate ───────────────────────────────────────────────────────
   Engraved pass: the item is a plate cut out of the rail rather than a
   rounded rectangle that lights up. Same grammar as the top bar's links
   (_Layout.cshtml:287-330), where the selected control is the one pushed
   INTO the surface rather than merely tinted — so `:hover` grows the
   shading and `.active` becomes `--rail-pressed`.

   `background: transparent` at rest is the house rule, not a shortcut:
   nothing on this portal has a flat surface colour, so a fill "would show
   as a painted patch sitting on the surface instead of a plate cut from
   it" (_Layout.cshtml:58-66). The form comes from the shading alone.

   No `transform` in the transition — a carved control that slides on hover
   drags its own shading with it, which is the one thing the illusion
   cannot survive (_Layout.cshtml:294-298). */
.ta-side-nav .ta-nav-item {
    width: 72px; min-height: 64px;
    display: flex; flex-direction: column;
    align-items: center; justify-content: center;
    gap: 4px; padding: 6px 4px;
    border-radius: 12px;
    background: transparent;
    box-shadow: var(--rail-plate);
    color: var(--rail-ink);
    text-decoration: none;
    transition: box-shadow .18s ease, color .18s ease, background-color .18s ease;
}
.ta-side-nav .ta-nav-item i { font-size: 1.1rem; }
.ta-side-nav .ta-nav-item .nav-label {
    font-size: .62rem; font-weight: 600;
    text-align: center; line-height: 1.1;
    color: inherit;
}
.ta-side-nav .ta-nav-item:hover {
    background: transparent;
    box-shadow: var(--rail-plate-hov);
    color: var(--rail-ink-hi);
}
/* Selected: pressed into the rail. The shallow dark face is what makes the
   press read as depth rather than as shading, and the 3px orange inlay is
   the at-a-glance position cue the solid orange fill used to carry — colour
   in a groove fill and an icon halo rather than in the whole button. */
.ta-side-nav .ta-nav-item.active {
    background: rgba(0, 0, 0, 0.18);
    box-shadow: var(--rail-pressed);
    color: var(--rail-ink-hi);
    position: relative;
}
.ta-side-nav .ta-nav-item.active::before {
    content: '';
    position: absolute;
    left: 6px; top: 12px; bottom: 12px;
    width: 3px; border-radius: 2px;
    background: var(--rail-inlay);
    box-shadow: 0 0 6px rgba(245,130,32,.55), 0 1px 0 rgba(255,255,255,.10);
}
.ta-side-nav .ta-nav-item.active i { color: var(--rail-inlay); }
/* Debossed glyphs, on the active item only so resting labels stay crisp.
   The dark shadow sits ABOVE the glyph — the recess lip the surface
   occludes — and the faint light line below is the catch. This is the only
   text-shadow in the app's stylesheets outside the print resets, so it is
   the piece to settle by eye rather than by argument. */
.ta-side-nav .ta-nav-item.active i,
.ta-side-nav .ta-nav-item.active .nav-label {
    text-shadow: 0 -1px 0 rgba(0, 0, 0, .45), 0 1px 0 rgba(255, 255, 255, .12);
}
.ta-side-nav .ta-nav-item:active { box-shadow: var(--rail-pressed); }

/* ── Legacy rails (the 2 pages whose rail is `side-nav` alone) ────────
   A sweep of all 90 rail containers finds exactly two whose nav carries no
   `ta-side-nav`: DeliveryCompletion.cshtml and DemandTracking.cshtml. Their
   anchors miss every rule above, so they get the plate from here. Same
   material and same press, and deliberately NOT the geometry — those items
   are 40px squares (DeliveryCompletion:43) and 72x64 already
   (DemandTracking:61), so resizing them is a different change.

   `body` is not decoration; it is the whole reason this block works. Both
   pages style their own rail's hover/active in a page-level block:
       DemandTracking.cshtml:63      .side-nav a:hover, .side-nav a.active
       DeliveryCompletion.cshtml:47  .side-nav a:hover, .side-nav a.active
   That is (0,2,1), which TIES with `.side-nav > a:hover`, and a tie is
   settled by source order. DemandTracking links this file last — its own
   <style> closes at :415 and the <link> is at :416 — so this file wins there
   unaided. DeliveryCompletion puts its rail rules in `@section Styles`,
   which _Layout.cshtml renders at :20, i.e. AFTER all four linked sheets, so
   the page wins and the plate would never appear. The extra ancestor takes
   this to (0,2,2), beating it on element count with no `.cshtml` edit.

   It also fixes what that page's rule does: its hover is
   `background:#0B2F5E; color:#0B2F5E` — navy on navy, so the icon disappears
   on hover. This file loads after marketplace.css at equal specificity too,
   so the same block supersedes that file's `--mp-orange-dim` hover (:34-38). */
body .side-nav > a {
    background: transparent;
    box-shadow: var(--rail-plate);
    color: var(--rail-ink);
    transition: box-shadow .18s ease, color .18s ease, background-color .18s ease;
}
body .side-nav > a:hover {
    background: transparent;
    box-shadow: var(--rail-plate-hov);
    color: var(--rail-ink-hi);
}
body .side-nav > a.active {
    background: rgba(0, 0, 0, 0.18);
    box-shadow: var(--rail-pressed);
    color: var(--rail-ink-hi);
    text-shadow: 0 -1px 0 rgba(0, 0, 0, .45), 0 1px 0 rgba(255, 255, 255, .12);
    /* Not decoration: these two rails need their own, because the only other
       `position: relative` on these anchors is marketplace.css:32, and
       DemandTracking (Layout = null) never loads that file — without it the
       inlay below would anchor to the nearest positioned ancestor and draw
       against the page instead of against the item. */
    position: relative;
}
/* Parity with the main block: same 3px inlay, same orange icon. A legacy rail
   that got the press but not the position cue would be the one rail in the app
   where "which item am I on?" is unanswerable. */
body .side-nav > a.active::before {
    content: '';
    position: absolute;
    left: 6px; top: 12px; bottom: 12px;
    width: 3px; border-radius: 2px;
    background: var(--rail-inlay);
    box-shadow: 0 0 6px rgba(245,130,32,.55), 0 1px 0 rgba(255,255,255,.10);
}
body .side-nav > a.active i { color: var(--rail-inlay); }
body .side-nav > a:active { box-shadow: var(--rail-pressed); }

/* A machined groove: the cut is the dark line, the lit lip below it is the
   edge of the surface catching the light. Same treatment the Quick Links
   pass settled on for a 1px hairline groove. */
.ta-side-nav .side-divider,
.side-nav > .side-divider {
    width: 28px; height: 1px;
    background: rgba(0, 0, 0, .45);
    box-shadow: 0 1px 0 rgba(255, 255, 255, .10);
    margin: 6px 0;
}
/* For standalone pages with no top nav, override height/top inline or
   add the .ta-side-nav-full class to the rail. */
.ta-side-nav.ta-side-nav-full { height: 100vh; top: 0; }

/* Collapse at 991px to match the System A boundary (distribution-design.css
   @media max-width:991px) so the rail disappears at the SAME width on every
   page. Left at 768px, a System B page still showed an 84px rail at widths
   where a System A page had already stacked — the chrome changed shape as you
   navigated between them, which is the "app seems off on mobile" report. */
@media (max-width: 991px) { .ta-side-nav { display: none !important; } }

/* ── Standalone shell completeness ────────────────────────────────
   .ta-dash-shell pages get the grid + rail from this file, but the
   .dash-main padding normally comes from distribution-design.css,
   which standalone (Layout=null) pages don't load — mirror it here.
   Same values, and this file loads last, so pages that DO load
   distribution-design.css render identically. */
.ta-dash-shell > .dash-main {
    padding: 28px 40px 64px;
    max-width: 1640px;
    margin: 0 auto;
    width: 100%;
}

/* The rail hides below 991px — collapse its grid column so no empty 84px
   gutter stays between the screen edge and the content. This breakpoint must
   stay equal to the .ta-side-nav rule above and to distribution-design.css's
   991px: all three describe the same moment in the layout. */
@media (max-width: 991px) {
    .ta-dash-shell { grid-template-columns: 1fr; }
    .ta-dash-shell > .dash-main { padding: 16px; }
}

/* ── Hero re-skin (remove marketplace campaign image) ─────────────── */
.mp-theme .page-hero,
.mp-theme .mp-hero {
    background: #ffffff;
    border: 1px solid rgba(0,0,0,.12);
    color: #0B2F5E;
    box-shadow: 0 1px 3px rgba(0,0,0,.08), 0 1px 2px rgba(0,0,0,.04);
}
.mp-theme .page-hero::before,
.mp-theme .mp-hero::before {
    background: radial-gradient(circle at 90% 30%, rgba(245,130,32,.12), transparent 50%);
}
.mp-theme .page-hero::after,
.mp-theme .mp-hero::after { display: none; }

.mp-theme .hero-title { color: #0B2F5E; }
.mp-theme .hero-sub  { color: rgba(0,0,0,.55); }
.mp-theme .hero-sub i { color: #F58220; }
.mp-theme .hero-icon {
    background: rgba(245,130,32,.15);
    border: 1px solid rgba(245,130,32,.30);
    color: #F58220;
}

/* ── Modal overlay (modern popup chrome) ────────────────────────── */
.modal-overlay {
    display: none; position: fixed; inset: 0;
    background: rgba(11,47,94,.65);
    backdrop-filter: blur(6px);
    z-index: 1000; align-items: flex-start; justify-content: center;
    padding: 30px 10px; overflow-y: auto;
    animation: ta-fade .2s var(--ease, cubic-bezier(.22,1,.36,1));
}
.modal-overlay.show { display: flex; }
.modal-box {
    background: #fff; border-radius: 20px;
    width: 90%; max-width: 950px; padding: 28px;
    box-shadow: 0 25px 80px rgba(0,0,0,.25);
    animation: ta-modal-in .3s var(--ease, cubic-bezier(.22,1,.36,1));
    margin: auto;
}
.modal-hdr {
    display: flex; align-items: center; justify-content: space-between;
    margin-bottom: 18px; padding-bottom: 14px;
    border-bottom: 2px solid #f0faf8;
}
.modal-title {
    font-size: 1.1rem; font-weight: 800;
    color: #0B2F5E;
    display: flex; align-items: center; gap: 8px;
}
.modal-close {
    background: #f3f4f6; border: none;
    width: 36px; height: 36px; border-radius: 50%;
    cursor: pointer; font-size: 1rem;
    display: flex; align-items: center; justify-content: center;
    color: #6b7280; transition: all .15s;
}
.modal-close:hover { background: #fde8eb; color: #E4032E; transform: rotate(90deg); }

/* Modal info bar */
.modal-info-bar {
    display: grid; grid-template-columns: repeat(auto-fill, minmax(180px, 1fr)); gap: 12px;
    margin-bottom: 16px; padding: 14px;
    background: linear-gradient(135deg, #fff7f5, #fff);
    border-radius: 12px; border-left: 4px solid #F58220;
    box-shadow: 0 4px 14px rgba(0,0,0,.06);
}
.modal-info-item { display: flex; flex-direction: column; gap: 2px; }
.modal-info-item .lbl {
    font-size: .68rem; font-weight: 700; text-transform: uppercase; letter-spacing: .05em;
    color: #94a3b8;
}
.modal-info-item .val { font-size: .95rem; font-weight: 800; color: #0B2F5E; }

/* Modal scrollable table */
.modal-table-scroll {
    max-height: 60vh; overflow-y: auto;
    border-radius: 12px; border: 1px solid #e5e7eb;
}
.modal-table-scroll .data-table,
.modal-table-scroll .dtbl { border-radius: 12px; }

/* Modal footer */
.modal-footer-bar {
    margin-top: 14px; padding-top: 14px;
    border-top: 1px solid #e5e7eb;
    display: flex; align-items: center; gap: 8px; flex-wrap: wrap;
}

/* Empty / error states inside modals */
.modal-empty {
    text-align: center; padding: 48px 20px; color: #9ca3af;
    background: #f9fafb; border-radius: 12px;
}
.modal-empty i { font-size: 2.5rem; display: block; margin-bottom: 12px; opacity: .55; }
.modal-empty p { font-weight: 600; margin: 0; }
.modal-error {
    padding: 16px; border-radius: 12px;
    background: #fde8eb; color: #E4032E;
    border-left: 4px solid #E4032E;
    font-weight: 600;
}
.modal-error pre {
    margin-top: 10px; max-height: 200px; overflow: auto;
    background: #fff; padding: 10px; border-radius: 8px;
    font-size: .75rem; color: #374151;
}
.modal-body-pad { padding: 4px 2px; }

/* ── Loading overlay & spinner ──────────────────────────────────── */
.loading-overlay {
    display: none; position: fixed; inset: 0;
    background: rgba(11,47,94,.65); backdrop-filter: blur(4px);
    z-index: 2000; align-items: center; justify-content: center;
}
.loading-overlay.show { display: flex; }
.loading-box {
    background: #fff; border-radius: 20px; padding: 36px 50px;
    text-align: center; box-shadow: 0 20px 60px rgba(0,0,0,.2); min-width: 280px;
}
.spinner {
    width: 52px; height: 52px;
    border: 5px solid #f0faf8;
    border-top-color: #F58220;
    border-radius: 50%; margin: 0 auto 18px;
    animation: ta-spin .9s linear infinite;
}
@keyframes ta-spin { to { transform: rotate(360deg); } }
.loading-title { font-size: 1.15rem; font-weight: 800; color: #0B2F5E; margin-bottom: 4px; }
.loading-sub { font-size: .88rem; color: #9ca3af; }

/* ── Animations ─────────────────────────────────────────────────── */
@keyframes ta-fade { from { opacity: 0; } to { opacity: 1; } }
@keyframes ta-modal-in { from { opacity: 0; transform: translateY(-30px); } to { opacity: 1; transform: translateY(0); } }

/* ── Reduced motion ─────────────────────────────────────────────── */
@media (prefers-reduced-motion: reduce) {
    .modal-overlay, .modal-box, .spinner {
        animation: none !important;
    }
}

/* ═════════════════════════════════════════════════════════════════════
   Checkbox engraving — StockOnHand + TimeAdjuster
   ─────────────────────────────────────────────────────────────────────
   The filter checkboxes on these two pages were the last controls still
   drawn by the OS and merely tinted with `accent-color`: flat, browser-
   drawn, unrelated to the carved language the top bar, the rail and the
   Quick Links strip already use. They become one control here — cut from
   the surface at rest, pushed INTO it when checked, with the orange inlay
   left in the recess. Same grammar as .ta-nav-item.active: in this
   language the selected control is the one pushed into the surface.

   Four DOM shapes on two faces. The first three are 16px inputs on a
   near-white ground and share one block; the fourth is an 18px span on
   navy and is shaped too differently to join them.

     .cb-item input                      StockOnHand locations + categories
     .ta-type-chip input                 TimeAdjuster transaction type
     .ta-filter-cbx input                TimeAdjuster missing/has-delivery
     .mp-checkbox-list-panel … > span    navy supplier/customer/product

   All four selectors are page-scoped and appear on no other page, so
   nothing here reaches the ~40 other pages that link this file.
   ═════════════════════════════════════════════════════════════════════ */

/* ── §1 The light-face box ──────────────────────────────────────────── */
.cb-item input[type=checkbox],
.ta-type-chip input[type=checkbox],
.ta-filter-cbx input[type=checkbox] {
    /* appearance:none is what makes a checkbox styleable at all — without
       it the UA paints its own box AND its own tick underneath ours. The
       prefix is not redundant: unprefixed `appearance` reached Safari only
       at 15.4, and older WebKit would draw a second mark. */
    appearance: none; -webkit-appearance: none;

    /* min-height:0 looks redundant and is load-bearing. mobile.css:113 is
       `input, select, textarea, button { min-height: 44px }` with NO media
       query around it, and mobile.css is linked on both pages — so every
       input here carries a 44px floor. min-height beats height when it is
       larger, so without this line the box is 16px wide and 44px tall. */
    width: 16px; height: 16px; min-height: 0;

    /* The box is a flex child of .cb-item and .ta-filter-cbx. Under
       appearance:none it has no intrinsic content, so min-width:auto
       resolves to 0 and a squeezed chip can squash it below 16px — a
       non-square plate, which the carve cannot survive. */
    flex-shrink: 0;

    margin: 0; border: 0; border-radius: 4px;

    /* Transparent, not a fill: nothing on this portal has a flat surface
       colour, so a fill would read as a painted patch sitting on the
       surface instead of a plate cut from it. */
    background-color: transparent;
    box-shadow: var(--cbx-rest);

    cursor: pointer;

    /* No transform. A carved control that slides on hover drags its own
       shading with it, which is the one thing the illusion cannot survive.
       box-shadow and background-color are the only properties that move.
       The tick is a background-image and is NOT animatable, so it snaps
       while the carve eases — accepted deliberately; a mask-based tick
       would smooth it at the cost of a prefix chain.

       There is no hover state on the box, on purpose: the chip already
       carries hover (.cb-item:hover, .ta-filter-cbx:hover) and still does.
       The box owns rest / checked / :active / :focus-visible, so one
       interaction gets one response. */
    transition: box-shadow .15s ease, background-color .15s ease;
}

/* Checked = pressed. The faint wash is what makes it read as DEPTH rather
   than only as inverted shading — the same move .ta-nav-item.active makes
   with its rgba(0,0,0,.18) well on the rail.

   The tick rides in the same block. ::before/::after do NOT render on
   <input> (it is a replaced element) and none of these three shapes has a
   spare sibling to draw on — .ta-filter-cbx's <span> wraps its label text,
   .cb-item has bare text after the input, .ta-type-chip has an <i> plus
   text. So it goes on the input itself as a background image, and all four
   sub-properties are required: the initial values are `repeat` and `0% 0%`,
   so a bare background-image tiles the tick from the top-left corner.
   background-size is px and not em because mobile.css:112 pins
   font-size:16px on inputs below 768px.

   The # in the tick colour is %23-escaped — written literally it
   terminates the data URI, which yields a broken image and therefore NO
   TICK on any checked box, with no console error. */
.cb-item input[type=checkbox]:checked,
.ta-type-chip input[type=checkbox]:checked,
.ta-filter-cbx input[type=checkbox]:checked {
    box-shadow: var(--cbx-pressed);
    background-color: var(--cbx-well);
    background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='none' stroke='%23c2410c' stroke-width='2.6' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M3.5 8.4l3.2 3.2L12.5 4.8'/%3E%3C/svg%3E");
    background-repeat: no-repeat;
    background-position: center;
    background-size: 12px 12px;
}

.cb-item input[type=checkbox]:active,
.ta-type-chip input[type=checkbox]:active,
.ta-filter-cbx input[type=checkbox]:active {
    box-shadow: var(--cbx-pressed);
}

/* Focus is an OUTLINE, never a ring appended to the carve. You cannot
   append to a box-shadow in CSS, so `carve + ring` in every state would
   mean a six-entry matrix per group (:focus-visible, :checked:focus-visible,
   :active, :checked:active, :active:focus-visible, :checked:active:focus-visible)
   — and ordering :active after :focus-visible makes the ring vanish while
   the key is held. An outline satisfies "never replace the carve" by
   construction, needs no matrix, is never clipped by an ancestor's
   overflow, and is what every other :focus-visible in this repo uses
   (login-shared.css:341, AdminAccess.cshtml:653, LoginPage.cshtml:722).

   The colour has to be face-dependent, exactly like the tick: #c2410c is
   4.9:1 on the light chips but only 2.56:1 on navy, and #F58220 is 5.1:1 on
   navy but 2.54:1 on the light chips. Neither clears the 3:1 a focus
   indicator needs on both. */
.cb-item input[type=checkbox]:focus-visible,
.ta-type-chip input[type=checkbox]:focus-visible,
.ta-filter-cbx input[type=checkbox]:focus-visible {
    outline: 2px solid var(--cbx-tick);
    outline-offset: 2px;
}

/* .ta-type-chip's wrapper is a bare <div>, not a flex row, so a 16px
   inline-level input would sit on the baseline of a ~36px chip instead of
   centred with it. The box is resized here, which makes the misalignment
   legible, so centre it. No markup edit. */
.ta-type-chip > div { display: flex; align-items: center; gap: 6px; }

/* ── §2 The navy panels — an 18px span on #0B2F5E ─────────────────────
   Shaped differently from the three above: the input is hidden and the box
   is a <span> inside the label, so this group keeps the span + Font Awesome
   glyph tick that already worked rather than converting to a background
   image. It is the repo's own idiom for a span-based box (Warehousing.cshtml
   :312-327, DemandTracking.cshtml:165-170), and FA failing to load breaks
   the whole portal's iconography anyway, so it is not a group-specific
   failure mode. What changes is the material.

   The input's own rule on the page is untouched ON PURPOSE — do not give it
   a size or a display. filterCbList() (TimeAdjuster.cshtml:934-943) writes
   an inline `style.display = 'block'` onto every MATCHED input on every
   keystroke in the panel's search box, and an inline style beats any
   non-!important rule. Give this input a carve and a size and matched rows
   grow a stray second line while unmatched rows stay one line — a bug that
   appears only while typing.

   The 18px size must stay EXPLICIT: the span holds only the ::after glyph
   and the universal reset (distribution-design.css:60) zeroes padding, so
   without a width and height it collapses to nothing. box-sizing is
   border-box, so reducing the border from 2px shifts nothing else — unlike
   QuickLinks.cshtml:698-702, which had to grow padding by the border it
   lost because that pill has no explicit width. */
.mp-checkbox-list-panel input[type=checkbox] + label > span {
    /* The flex declarations are not decoration: without them the span is
       `display: inline`, an 18px width/height does not apply to it, and the
       ::after glyph is not centred. They moved here with the rest of the box
       so that this file owns it whole — a box split across two files is how
       the tick colour ended up losing to source order in the first place. */
    display: flex; justify-content: center; align-items: center; flex-shrink: 0;
    width: 18px; height: 18px;
    border: 1px solid var(--cbx-dark-lip);
    border-radius: 4px;
    background: transparent;
    box-shadow: var(--cbx-dark-rest);
    /* `color` is in this list and not in §1's because the tick here is a
       glyph, not an image — it is the one property that changes. */
    transition: box-shadow .15s ease, background-color .15s ease,
                border-color .15s ease, color .15s ease;
}

.mp-checkbox-list-panel input[type=checkbox]:checked + label > span {
    box-shadow: var(--cbx-dark-press);
    background: var(--cbx-dark-well);
    border-color: rgba(255, 255, 255, 0.14);
}

.mp-checkbox-list-panel input[type=checkbox]:checked + label > span::after {
    content: "\f00c"; font-family: "Font Awesome 6 Free"; font-weight: 900;
    font-size: .65rem; color: var(--cbx-tick-dark);
}

/* The panel input is 0x0 and opacity:0, so its own outline draws nothing —
   the ring has to go on the label. Worth noting this is a NEW signal rather
   than a restyle: keyboard focus in these navy panels is invisible today,
   because the rule that would have shown it targets input[type=radio] on a
   page that contains no radio at all. */
.mp-checkbox-list-panel input[type=checkbox]:focus-visible + label {
    outline: 2px solid var(--cbx-tick-dark);
    outline-offset: 1px;
    border-radius: 6px;
}

/* ── §3 Forced colours ────────────────────────────────────────────────
   With appearance:none the checked state is carried entirely by a
   background-image and by shadows, and forced-colours mode strips BOTH —
   so checked and unchecked would become identical, which the native
   accent-color checkbox this replaces did not do. The first forced-colours
   block in this repo; it exists to avoid a real accessibility regression,
   not as a style choice. Unchecked keeps a CanvasText edge so the box has
   a boundary at all, since border:0 in §1 leaves it with none. */
@media (forced-colors: active) {
    .cb-item input[type=checkbox],
    .ta-type-chip input[type=checkbox],
    .ta-filter-cbx input[type=checkbox] {
        border: 1px solid CanvasText;
    }
    .cb-item input[type=checkbox]:checked,
    .ta-type-chip input[type=checkbox]:checked,
    .ta-filter-cbx input[type=checkbox]:checked {
        background-color: Highlight;
        border-color: Highlight;
    }
    .mp-checkbox-list-panel input[type=checkbox] + label > span {
        border-color: CanvasText;
    }
    .mp-checkbox-list-panel input[type=checkbox]:checked + label > span {
        background: Highlight;
        border-color: Highlight;
    }
}
