/* ============================================================================
   glass-theme.css - the application SHELL under the modern themes.
   Load AFTER design-system.css.

   Targets the shell classes this application already renders - .headerMain,
   .sideNavigation, .backBox, .breadCumb - so existing views inherit the new
   look without a single markup change.

   ---------------------------------------------------------------------------
   ABOUT !important
   ---------------------------------------------------------------------------
   Used ONLY where the rule being overridden is itself !important
   (menu-modern.css sets width/border-radius/top/padding on .sideNavigation
   that way, and ftsNewScreen.css does the same in places). Specificity alone
   cannot beat !important, so matching it is the only correct answer; it is not
   used anywhere it is not needed.
   ============================================================================ */

/*  [2026-09-11] backdrop-filter REMOVED - CONTAINING-BLOCK HAZARD.
    ---------------------------------------------------------------------------
    backdrop-filter creates a CONTAINING BLOCK for absolutely-positioned
    descendants. DevExpress computes a dropdown's position in DOCUMENT
    coordinates and applies them as position:absolute; left/top. When an
    ancestor becomes the containing block those coordinates are re-interpreted
    relative to THAT element, so the dropdown is displaced by exactly the
    ancestor's offset from the document origin.

    That is what broke the Branch dropdown on /Myshop/ShopList/Index: .backBox
    is the standard content panel - 242 views use it - and ShopList alone holds
    14 GridLookup controls inside one. The bug appeared in Modern and Dark and
    not in Standard purely because these rules are theme-scoped, which is the
    clearest possible signal that the theme caused it.

    Removing the filter is visually safe by the design's own account: the
    --bz-glass tokens in design-system.css are documented as "opaque enough to
    read against on its own" precisely so the effect can degrade. Over a dark
    page a blurred translucent panel and a flat translucent one are nearly
    indistinguishable, so this costs almost nothing.

    RULE: backdrop-filter may only be used on a floating overlay that can never
    contain a positioned widget. In practice that is the loader scrim, and
    nothing else.
*/


/* ---------------------------------------------------------------------------
   1. SIDEBAR
   menu-modern.css already shapes this (268px, 14px radius, 70px top). Only the
   SKIN is restated here so the two files cannot disagree about geometry.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation,
[data-bz-theme="dark"] .sideNavigation {
    background-image: linear-gradient(180deg, var(--bz-sidebar-from) 0%, var(--bz-sidebar-to) 100%) !important;
    border: 1px solid rgba(148, 163, 184, .10) !important;
    box-shadow: var(--bz-shadow-lg) !important;
    border-radius: var(--bz-r-lg) !important;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li > a,
[data-bz-theme="dark"] .sideNavigation > ul > li > a {
    border-radius: var(--bz-r-sm) !important;
    transition: background var(--bz-t) var(--bz-ease), color var(--bz-t) var(--bz-ease);
}

/* The active row reads as a raised brand chip rather than a flat highlight. */
[data-bz-theme="nextgen"] .sideNavigation > ul > li.active > a,
[data-bz-theme="dark"] .sideNavigation > ul > li.active > a,
[data-bz-theme="nextgen"] .sideNavigation > ul > li.is-open > a,
[data-bz-theme="dark"] .sideNavigation > ul > li.is-open > a {
    background-image: linear-gradient(135deg, var(--bz-primary) 0%, var(--bz-primary-700) 100%) !important;
    box-shadow: var(--bz-shadow-brand) !important;
    color: #fff !important;
}

/* ---------------------------------------------------------------------------
   2. HEADER - frosted, and it stays put.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .headerMain,
[data-bz-theme="dark"] .headerMain {
    background: var(--bz-glass);
    border-bottom: 1px solid var(--bz-border);
    box-shadow: var(--bz-shadow-sm);
}

/* ---------------------------------------------------------------------------
   3. PAGE SURFACE
   .backBox is this application's content panel - it wraps essentially every
   screen. Turning it into a floating card is what carries the new look across
   all 733 views at once.
--------------------------------------------------------------------------- */
/* [2026-09-11] .form_main and .Box-section joined .backBox here.
   Checked before adding: of 138 views using .form_main, 85 carry it on the
   SAME element as .backBox (so nothing doubles) and 28 use it with no
   .backBox at all - those 28 were the coverage gap this closes.
   .Box-section is likewise used across modules, so it belongs in the shell
   layer rather than in a module stylesheet. */
[data-bz-theme="nextgen"] .backBox,
[data-bz-theme="dark"] .backBox,
[data-bz-theme="nextgen"] .form_main,
[data-bz-theme="dark"] .form_main,
[data-bz-theme="nextgen"] .Box-section,
[data-bz-theme="dark"] .Box-section {
    background: var(--bz-glass);
    border: 1px solid var(--bz-glass-brd);
    border-radius: var(--bz-r-lg);
    box-shadow: var(--bz-shadow);
    padding: var(--bz-s-6);
    color: var(--bz-text);
}

/* ---------------------------------------------------------------------------
   4. BREADCRUMB / PAGE TITLE
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .breadCumb,
[data-bz-theme="dark"] .breadCumb {
    background: transparent;
    color: var(--bz-muted);
    font-family: var(--bz-font);
    font-size: 13px;
    letter-spacing: .1px;
    margin-bottom: var(--bz-s-4);
}

[data-bz-theme="nextgen"] .breadCumb > span,
[data-bz-theme="dark"] .breadCumb > span { color: var(--bz-muted); }

/* ---------------------------------------------------------------------------
   5. NEW REUSABLE WRAPPERS
   Opt-in classes for new or refreshed markup. Nothing existing has to adopt
   them; they exist so new pages have a vocabulary instead of inventing one.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .app-shell,
[data-bz-theme="dark"] .app-shell {
    min-height: 100vh;
    background: transparent;
}

[data-bz-theme="nextgen"] .page-layout,
[data-bz-theme="dark"] .page-layout {
    max-width: var(--bz-page-max);
    margin: 0 auto;
    padding: var(--bz-s-6);
}

[data-bz-theme="nextgen"] .page-header,
[data-bz-theme="dark"] .page-header {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: space-between;
    padding: var(--bz-s-5) var(--bz-s-6);
    margin-bottom: var(--bz-s-5);
    border-radius: var(--bz-r-lg);
    background-image: linear-gradient(135deg, rgba(37, 99, 235, .10) 0%, rgba(96, 165, 250, .06) 100%);
    border: 1px solid var(--bz-glass-brd);
    box-shadow: var(--bz-shadow-sm);
}

[data-bz-theme="nextgen"] .page-header h1,
[data-bz-theme="dark"] .page-header h1 {
    margin: 0;
    font-size: 24px;
    font-weight: 700;
    letter-spacing: -.2px;
}

[data-bz-theme="nextgen"] .page-header p,
[data-bz-theme="dark"] .page-header p {
    margin: 4px 0 0;
    color: var(--bz-muted);
    font-size: 13.5px;
}

[data-bz-theme="nextgen"] .page-toolbar,
[data-bz-theme="dark"] .page-toolbar {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    padding: var(--bz-s-4) var(--bz-s-5);
    margin-bottom: var(--bz-s-5);
    border-radius: var(--bz-r);
    background: var(--bz-glass-2);
    border: 1px solid var(--bz-glass-brd);
}

/* Flex gap is Chrome 84+; the floor is 59. Margin on the children does the
   same job everywhere, so the toolbar cannot collapse into a run-on row on an
   older browser. */
[data-bz-theme="nextgen"] .page-toolbar > *,
[data-bz-theme="dark"] .page-toolbar > * {
    margin-right: var(--bz-s-3);
    margin-bottom: var(--bz-s-2);
}

[data-bz-theme="nextgen"] .page-toolbar > *:last-child,
[data-bz-theme="dark"] .page-toolbar > *:last-child { margin-right: 0; }

/* ---------------------------------------------------------------------------
   6. MODALS - Bootstrap 3 is what every one of these views uses.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .modal-content,
[data-bz-theme="dark"] .modal-content {
    background: var(--bz-surface);
    color: var(--bz-text);
    border: 1px solid var(--bz-border);
    border-radius: var(--bz-r-lg);
    box-shadow: var(--bz-shadow-lg);
}

[data-bz-theme="nextgen"] .modal-header,
[data-bz-theme="dark"] .modal-header {
    border-bottom: 1px solid var(--bz-border);
    padding: var(--bz-s-4) var(--bz-s-5);
}

/* [2026-09-15] `color` moved out of the shared half - see below. */
[data-bz-theme="nextgen"] .modal-title,
[data-bz-theme="dark"] .modal-title {
    font-weight: 700;
    font-size: 16px;
}

/* WHY MODERN DOES NOT RE-INK THE MODAL TITLE, AND DARK DOES.

   This app paints its modal headers DARK and always has: SearchPopup.css
   gives `.modal .modal-header` #094e8c, PMSStyles.css gives
   `.pmsModal .modal-header` #165291, and ~160 views restate one or the other
   in a page-level <style>. ftsNewScreen.css matches that with

       .modal-title { color: #fff; }        (0,1,0)

   Nothing in the theme layer repaints those headers in Modern - the rule
   above only ever set border and padding - so the plate stays dark blue while
   this rule, at (0,1,1), outranked the white and dropped --bz-heading
   (#0F1B36) onto it. 8.47:1 in Standard became 2.02:1 in Modern, on every
   modal in the portal. Same shape as the sign-in headline: a bare class
   carrying the panel's own ink, beaten by an attribute-plus-element selector.

   Modern therefore leaves the ink alone and the title renders exactly as
   Standard does. Dark keeps --bz-heading because theme-dark-surfaces.css
   DOES repaint `.modal-header` there, so the plate and the ink move together
   - which is the whole distinction: re-ink only what you also re-paint. */
[data-bz-theme="dark"] .modal-title { color: var(--bz-heading); }

[data-bz-theme="nextgen"] .modal-body,
[data-bz-theme="dark"] .modal-body { padding: var(--bz-s-5); }

[data-bz-theme="nextgen"] .modal-footer,
[data-bz-theme="dark"] .modal-footer {
    border-top: 1px solid var(--bz-border);
    padding: var(--bz-s-4) var(--bz-s-5);
}

[data-bz-theme="nextgen"] .modal-backdrop.in,
[data-bz-theme="dark"] .modal-backdrop.in { opacity: .55; }

/* The close glyph is a bare "x" in Bootstrap 3 and disappears on a dark
   surface, because its colour is #000 with opacity. */
[data-bz-theme="dark"] .modal-header .close,
[data-bz-theme="dark"] .close {
    color: var(--bz-text);
    opacity: .75;
    text-shadow: none;
}

[data-bz-theme="dark"] .close:hover { color: var(--bz-text); opacity: 1; }

/* ---------------------------------------------------------------------------
   7. BOOTSTRAP 3 PANELS / WELLS - used widely as section containers.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .panel,
[data-bz-theme="dark"] .panel {
    background: var(--bz-surface);
    border: 1px solid var(--bz-border);
    border-radius: var(--bz-r);
    box-shadow: var(--bz-shadow-sm);
}

[data-bz-theme="nextgen"] .panel-heading,
[data-bz-theme="dark"] .panel-heading {
    background: var(--bz-surface-2);
    border-bottom: 1px solid var(--bz-border);
    border-radius: var(--bz-r) var(--bz-r) 0 0;
    color: var(--bz-heading);
    font-weight: 600;
}

[data-bz-theme="nextgen"] .well,
[data-bz-theme="dark"] .well {
    background: var(--bz-surface-2);
    border: 1px solid var(--bz-border);
    border-radius: var(--bz-r);
    box-shadow: none;
}

/* ---------------------------------------------------------------------------
   8. NAV TABS
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .nav-tabs,
[data-bz-theme="dark"] .nav-tabs { border-bottom: 1px solid var(--bz-border); }

[data-bz-theme="nextgen"] .nav-tabs > li > a,
[data-bz-theme="dark"] .nav-tabs > li > a {
    color: var(--bz-muted);
    border: none;
    border-bottom: 2px solid transparent;
    border-radius: 0;
    font-weight: 600;
}

[data-bz-theme="nextgen"] .nav-tabs > li.active > a,
[data-bz-theme="nextgen"] .nav-tabs > li.active > a:hover,
[data-bz-theme="nextgen"] .nav-tabs > li.active > a:focus,
[data-bz-theme="dark"] .nav-tabs > li.active > a,
[data-bz-theme="dark"] .nav-tabs > li.active > a:hover,
[data-bz-theme="dark"] .nav-tabs > li.active > a:focus {
    background: transparent;
    color: var(--bz-primary);
    border: none;
    border-bottom: 2px solid var(--bz-primary);
}

/* ---------------------------------------------------------------------------
   9. RESPONSIVE
--------------------------------------------------------------------------- */
@media (max-width: 1024px) {
    [data-bz-theme="nextgen"] .page-layout,
    [data-bz-theme="dark"] .page-layout { padding: var(--bz-s-4); }

    [data-bz-theme="nextgen"] .backBox,
    [data-bz-theme="dark"] .backBox { padding: var(--bz-s-4); }
}

@media (max-width: 767px) {
    [data-bz-theme="nextgen"] .page-header,
    [data-bz-theme="dark"] .page-header {
        display: block;
        padding: var(--bz-s-4);
    }
    [data-bz-theme="nextgen"] .page-header h1,
    [data-bz-theme="dark"] .page-header h1 { font-size: 20px; }

    [data-bz-theme="nextgen"] .backBox,
    [data-bz-theme="dark"] .backBox {
        padding: var(--bz-s-3);
        border-radius: var(--bz-r);
    }
}

/* UHD - stop the content stretching to 4K width while letting the wash fill. */
@media (min-width: 2200px) {
    [data-bz-theme="nextgen"] .page-layout,
    [data-bz-theme="dark"] .page-layout { max-width: var(--bz-page-max); }
}

/* ============================================================================
   10. DARK SURFACE RECONCILIATION
   [2026-09-11] Added after an RCA sweep of the base stylesheets.

   ftsNewScreen.css hardcodes a light background on 21 rules. The theme already
   covered .headerMain and .backBox, but the rest were never targeted - so under
   Dark they painted light islands straight over the dark page. The worst was
   .content-wraper, a PAGE-LEVEL wrapper at plain `background: #fff`, which put
   a white slab across the whole content area.

   Every selector below is (0,2,0) against the original (0,1,0), so plain
   specificity wins and no !important is needed - except where the original
   itself used !important, which is called out inline.

   Light/Modern is deliberately untouched here: those rules are CORRECT on a
   light ground, and re-stating them would only create drift.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .content-wraper,
[data-bz-theme="dark"] .bdPad,
[data-bz-theme="dark"] .box-holder.full-screen,
[data-bz-theme="dark"] .box-full.full-screen {
    background: transparent;
    color: var(--bz-text);
}

/* Floating panels keep a real (opaque) surface - they overlap content, so
   transparent would let the page show through them. */
[data-bz-theme="dark"] .hoverMenu,
[data-bz-theme="dark"] .profDrop,
[data-bz-theme="dark"] .widgBox,
[data-bz-theme="dark"] .searchFocused {
    background: var(--bz-surface);
    color: var(--bz-text);
    border-color: var(--bz-border);
}

[data-bz-theme="dark"] .widgBox .icon { background: var(--bz-surface-2); }

/* The breadcrumb chip: section 4 above set its colour but never its
   background, so it stayed a white pill on a dark bar. */
[data-bz-theme="dark"] .breadCumb > span {
    background: var(--bz-surface-2);
    color: var(--bz-muted);
}

/* #ffebeb - a pink tint that reads as an error state on a dark header. */
[data-bz-theme="dark"] .dateTime {
    background: var(--bz-surface-2);
    color: var(--bz-text);
}

/* A bare <select> (no .form-control) is not reached by forms.css, and its own
   rule sets background-color:#fff - white box, light text, unreadable. */
[data-bz-theme="dark"] select:not(.btn) {
    background-color: var(--bz-surface);
    color: var(--bz-text);
    border-color: var(--bz-border-2);
}

/* These three resolve to a #FFF fallback when --cc-card-bg is undefined, which
   it is outside the Command Center. Pointing the fallback at the theme surface
   fixes it without touching the variable the Command Center sets. */
[data-bz-theme="dark"] .prof .searcherInput input,
[data-bz-theme="dark"] .prof .resulter,
[data-bz-theme="dark"] .prof .nav > li.dropdown > a.nav-link {
    background: var(--cc-card-bg, var(--bz-surface));
    color: var(--bz-text);
}

/* The original carries !important, so matching it is the only way to win. */
[data-bz-theme="dark"] .party-list-buttons .btn,
[data-bz-theme="dark"] .party-list-buttons select {
    background: var(--bz-surface) !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border-2) !important;
}

/* ---------------------------------------------------------------------------
   11. BREEZEFSM GUIDE + GUIDED TOUR (breeze-tour.css)
   [2026-09-11]

   breeze-tour.css paints BOTH the Guide overlay (.bzh-*, opened by
   window.BreezeHelp.open) and the guided tour (.bzt-*). It carries 10
   hardcoded light backgrounds, and because both are overlays they float ON TOP
   of the page - so on Dark they were the brightest thing on screen.

   The Guide is one of the three screens the MENU RULE protects. That rule is
   honoured the same way as for Command Center: Standard is the default and
   matches nothing here, so the Guide is unchanged for anyone who has not opted
   in. These rules only exist for Modern/Dark.

   The two `img` selectors are logo plates - they keep a LIGHT background on
   purpose, because the artwork they sit behind is dark-on-transparent and
   would disappear against a dark plate. Left alone deliberately.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .bzt-card,
[data-bz-theme="dark"] .bzt-menu-box,
[data-bz-theme="dark"] .bzh-panel {
    background: var(--bz-surface);
    color: var(--bz-text);
    border-color: var(--bz-border);
}

[data-bz-theme="dark"] .bzt-btn,
[data-bz-theme="dark"] .bzt-tour-item,
[data-bz-theme="dark"] .bzh-f {
    background: var(--bz-surface-2);
    color: var(--bz-text);
    border-color: var(--bz-border-2);
}

/* The active language pill - stays the accent, not a plain surface. */
[data-bz-theme="dark"] .bzt-lang button.on {
    background: var(--bz-primary-700);
    color: #fff;
}

/* ---------------------------------------------------------------------------
   12. INTRO.JS ("Interface Overview")
   [2026-09-11] Found by a load-order audit.

   Reachable from the profile dropdown on every screen (<li onclick="startIntro()">).
   Its stylesheet is a CDN file linked from the BODY, not the head, so it lands
   after everything here in source order. These rules win on SPECIFICITY
   ((0,2,0) vs (0,1,0)) rather than order, which is the only thing that works
   against a body-loaded sheet.

   Left alone on Modern: intro.js ships a light tooltip, which is correct on a
   light ground. Only Dark needs restating.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .introjs-tooltip,
[data-bz-theme="dark"] .introjs-tooltiptext,
[data-bz-theme="dark"] .introjs-tooltipbuttons {
    background-color: var(--bz-surface);
    color: var(--bz-text);
    border-color: var(--bz-border);
}

[data-bz-theme="dark"] .introjs-button {
    background-color: var(--bz-surface-2);
    color: var(--bz-text);
    border-color: var(--bz-border-2);
    text-shadow: none;
}

[data-bz-theme="dark"] .introjs-helperNumberLayer {
    background: var(--bz-primary);
    color: #0B1220;
}

/* ---------------------------------------------------------------------------
   13. DARK INK RECONCILIATION - invisible text
   [2026-09-11] Found by a contrast audit, and this is the worst dark-mode bug
   class there is: a light BACKGROUND left behind is ugly, but dark TEXT on a
   surface this theme has just darkened is simply gone.

   53 rules across ftsNewScreen.css and fsm-dashboard-cc.css set a literal dark
   ink (#0F172A, #141414, #333 ...) instead of reading a token, so the theme's
   own colour never reached them. Among them are the FSM Dashboard KPI numbers
   (.widgBox .Numb / .txt, .colorBox .nums) - the single most-read figures on
   that screen.

   45 of those carry !important, so matching it is the only thing that wins;
   the rest are beaten on specificity alone. Split accordingly - !important is
   not used anywhere it is not required.

   Light/Modern is untouched: a dark ink on a light ground is correct.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .widgBox .txt,
[data-bz-theme="dark"] .middleWraper > .dateTime #clock,
[data-bz-theme="dark"] .prof .resulter #clonedMenus a span.texts,
[data-bz-theme="dark"] .logoWrap .bz-lockup-txt b,
[data-bz-theme="dark"] .bz-cmp-head b,
[data-bz-theme="dark"] .bz-cmp-tab:hover,
[data-bz-theme="dark"] .dashboardHighlightWrap .emp-dropdown-title .font-normal,
[data-bz-theme="dark"] .dashboardHighlightWrap .panel-heading h4.Widgheading.relative > span:first-child {
    color: var(--bz-text);
}

/* These fight an !important of their own. */
[data-bz-theme="dark"] .dxgvFocusedRow_PlasticBlue,
[data-bz-theme="dark"] table.dxgvTable_PlasticBlue > tbody >tr.dxgvFooter_PlasticBlue,
[data-bz-theme="dark"] div.swal2-container h2.swal2-title,
[data-bz-theme="dark"] .party-list-buttons .btn:hover,
[data-bz-theme="dark"] .party-list-buttons select.btn:hover,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.c1 .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.c2 .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.c3 .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.c4 .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.c5 .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.active .Numb,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox .txt,
[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.widgBox.active .txt,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox .nums,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox .Numb,
[data-bz-theme="dark"] .dashboardHighlightWrap .infoWrp .nums,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox .txt,
[data-bz-theme="dark"] .dashboardHighlightWrap .infoWrp .txt,
[data-bz-theme="dark"] .dashboardHighlightWrap .mainAreaTAb .colorBox.colorBox .nums,
[data-bz-theme="dark"] .dashboardHighlightWrap .mainAreaTAb .colorBox.colorBox .Numb,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox.colorBox .nums,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox.colorBox .Numb,
[data-bz-theme="dark"] .dashboardHighlightWrap .infoWrp .colorBox.colorBox .nums,
[data-bz-theme="dark"] .dashboardHighlightWrap .mainDashBoxes.newStyleMN .widgBox.widgBox.widgBox .Numb,
[data-bz-theme="dark"] .dashboardHighlightWrap .mainAreaTAb .colorBox.colorBox .txt,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox.colorBox .txt,
[data-bz-theme="dark"] .dashboardHighlightWrap .mainDashBoxes.newStyleMN .widgBox.widgBox.widgBox .txt,
[data-bz-theme="dark"] .dashboardHighlightWrap .cc-block-head,
[data-bz-theme="dark"] .dashboardHighlightWrap .Widgheading > span,
[data-bz-theme="dark"] .dashboardHighlightWrap .hdd-rp,
[data-bz-theme="dark"] .dashboardHighlightWrap .box-holder .bxd-head,
[data-bz-theme="dark"] .dashboardHighlightWrap table.dt-legacy-grid tbody td,
[data-bz-theme="dark"] .dashboardHighlightWrap .bxd-cont table.table tbody td,
[data-bz-theme="dark"] .fsm-orderbar .fsm-bar-lbl,
[data-bz-theme="dark"] .dashboardHighlightWrap .fsm-filterbar-label,
[data-bz-theme="dark"] .fsm-orderbar .fsm-bar-select,
[data-bz-theme="dark"] .dashboardHighlightWrap .fsm-date-input input,
[data-bz-theme="dark"] .cc-block-head.bz-head-merged .fsm-bar-lbl,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox.colorBox .infoWrp .txts,
[data-bz-theme="dark"] .dashboardHighlightWrap .mainAreaTAb .colorBox.colorBox .txts,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox.colorBox .txts,
[data-bz-theme="dark"] .dashboardHighlightWrap .colorBox.colorBox .infoWrp > .mrLinks,
[data-bz-theme="dark"] .dashboardHighlightWrap h4.Widgheading .clstyle:hover,
[data-bz-theme="dark"] .dashboardHighlightWrap h4.Widgheading .closeAcDetails2:hover {
    color: var(--bz-text) !important;
}

/* ---------------------------------------------------------------------------
   14. SWEETALERT2
   Loaded globally by _Layout.cshtml and ERP.Master, so every confirm dialog in
   the product is one of these. Its own sheet sets the title to #111 !important.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] div.swal2-container div.swal2-popup {
    background: var(--bz-surface);
    color: var(--bz-text);
}

[data-bz-theme="dark"] div.swal2-container h2.swal2-title {
    color: var(--bz-text) !important;
}

[data-bz-theme="dark"] div.swal2-container div.swal2-html-container {
    color: var(--bz-text);
}
