/* Baseline emoji rendering across machines (2026-08-28, user-reported).
   Native color emoji glyphs come from the OS's own font (Segoe UI Emoji on Windows,
   Apple Color Emoji on Mac, etc.), and those fonts draw the SAME character with
   genuinely different colour/art -- plain CSS `color` cannot override this, since
   colour-emoji glyphs are pre-coloured art, not recolourable text.

   Fix: self-host Google's Noto Color Emoji (SIL Open Font License -- free to embed/
   redistribute), restricted via `unicode-range` to just the emoji code-point blocks.
   This site has no single global font-family rule to append a fallback to -- font
   names are declared per-selector all over the CSS ('araboto', 'araboto-Normal',
   'Arial, sans-serif', 'system-ui', ...). Registering the SAME emoji font under each
   of those exact family names (one @font-face block per name, all unicode-range
   scoped) means whichever font an element already resolves to, the browser
   automatically swaps in this font ONLY for the emoji characters it declares --
   every other character keeps rendering from that element's normal font, completely
   unaffected. This covers every current emoji use (ESOADashboard, EshipmentTracking
   Dashboard, etc.) and any future one, from a single shared file, with no per-element
   edits and no risk to existing typography.

   Fix (2026-08-28, "success ticks/error/warning icons broke"): U+2600-27BF also contains
   U+2714 (HEAVY CHECK MARK, the success-icon glyph) and U+26A0 (WARNING SIGN, the error-icon
   AND warning-icon glyph) -- both used sitewide (_Layout.cshtml's #success-popup/#error-popup/
   #warning-popup) as plain CSS-colored text glyphs (color:#28a745/#dc3545/#d1a800 in
   CustomLayout.css), not as decorative color emoji. Catching them here silently broke that
   coloring, since a color-emoji glyph can't be recolored by CSS (this file's own point above).
   Split U+2600-27BF around those two code points so the real decorative-emoji symbols in that
   block (✂✅⚡☀ etc.) keep the color-emoji treatment, while ✔ and ⚠ fall through to each
   element's own font and CSS color, unaffected. */

@font-face {
    font-family: 'araboto';
    src: url('../fonts/NotoColorEmoji.ttf') format('truetype');
    unicode-range: U+2190-21FF, U+2600-269F, U+26A1-2713, U+2715-27BF, U+2B00-2BFF, U+1F300-1F5FF, U+1F600-1F64F, U+1F680-1F6FF, U+1F900-1F9FF, U+1FA70-1FAFF, U+FE0F;
    font-display: swap;
}

@font-face {
    font-family: 'araboto-Normal';
    src: url('../fonts/NotoColorEmoji.ttf') format('truetype');
    unicode-range: U+2190-21FF, U+2600-269F, U+26A1-2713, U+2715-27BF, U+2B00-2BFF, U+1F300-1F5FF, U+1F600-1F64F, U+1F680-1F6FF, U+1F900-1F9FF, U+1FA70-1FAFF, U+FE0F;
    font-display: swap;
}

@font-face {
    font-family: 'Arial';
    src: url('../fonts/NotoColorEmoji.ttf') format('truetype');
    unicode-range: U+2190-21FF, U+2600-269F, U+26A1-2713, U+2715-27BF, U+2B00-2BFF, U+1F300-1F5FF, U+1F600-1F64F, U+1F680-1F6FF, U+1F900-1F9FF, U+1FA70-1FAFF, U+FE0F;
    font-display: swap;
}

@font-face {
    font-family: 'sans-serif';
    src: url('../fonts/NotoColorEmoji.ttf') format('truetype');
    unicode-range: U+2190-21FF, U+2600-269F, U+26A1-2713, U+2715-27BF, U+2B00-2BFF, U+1F300-1F5FF, U+1F600-1F64F, U+1F680-1F6FF, U+1F900-1F9FF, U+1FA70-1FAFF, U+FE0F;
    font-display: swap;
}

@font-face {
    font-family: 'system-ui';
    src: url('../fonts/NotoColorEmoji.ttf') format('truetype');
    unicode-range: U+2190-21FF, U+2600-269F, U+26A1-2713, U+2715-27BF, U+2B00-2BFF, U+1F300-1F5FF, U+1F600-1F64F, U+1F680-1F6FF, U+1F900-1F9FF, U+1FA70-1FAFF, U+FE0F;
    font-display: swap;
}