/* ============================================================================
   theme-shell.css - the application SHELL under Modern / Dark.
   [2026-09-11]

   ---------------------------------------------------------------------------
   WHY THIS FILE EXISTS
   ---------------------------------------------------------------------------
   The first cut of the theme layer restyled a Bootstrap vocabulary (.btn,
   .form-control, .table, .card). That vocabulary is real but it is not what a
   user looks at: the frame around it - the sidebar, the header strip, the
   page ground - was left exactly as Standard paints it. The result was a
   "Modern" theme that most screens rendered almost identically to Standard,
   because the large majority of the viewport that is chrome never moved.

   This file themes the chrome. It is the difference between a token swap and
   a redesign.

   ---------------------------------------------------------------------------
   WHY !important IS CORRECT HERE (and is not laziness)
   ---------------------------------------------------------------------------
   menu-modern.css sets .sideNavigation with !important on nearly every
   declaration. An !important declaration beats ANY specificity, so
   [data-bz-theme="nextgen"] .sideNavigation { background: ... } - despite being
   far more specific - would silently lose. Matching !important is the only way
   to win without editing menu-modern.css, and editing that file would change
   STANDARD, which is the one thing this feature must never do.

   Every !important here sits inside a [data-bz-theme="nextgen"|"dark"]
   selector, so it is unreachable in Standard.

   [2026-09-11] SCOPED BACK. !important now appears ONLY in sections 1-3 - the
   page ground, the sidebar and the header - where a known !important or a
   later-loading rule genuinely has to be beaten. Sections 5-6 (generic
   components) carry none, so a page that ships its own design and defends it
   with !important keeps winning. See the note on section 5 for why that
   mattered: fsm-dashboard-cc.css was being overridden by this file.

   ---------------------------------------------------------------------------
   WHAT THIS FILE DELIBERATELY NEVER SETS
   ---------------------------------------------------------------------------
   No width, height, float, display or position. Colour, radius, border and
   shadow only.

   And never a whole-page CONTAINER. Section 4 records the rule that broke
   this: .dashboardHighlightWrap was themed as a title banner on the strength
   of its name, when it actually wraps @RenderBody() for every page in the
   portal - and its height is read back by JavaScript to size the sidebar.
   Read the markup before trusting a class name. DevExpress measures grid geometry in JavaScript at render time;
   a theme that moves box metrics desynchronises header and data columns. That
   restraint is what makes this safe to apply application-wide.

   ASCII-only (Docs/UI-Design-System.md): IIS serves static assets as Latin-1.
   No :has(), no flex gap, no color-mix - Chrome 59 floor.
   ============================================================================ */

/* ---------------------------------------------------------------------------
   1. PAGE GROUND
   The tinted wash. Fixed attachment so it does not slide under long grids and
   band visibly at the scroll seam.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] body,
[data-bz-theme="dark"] body {
    background-image: var(--bz-page-grad) !important;
    background-attachment: fixed !important;
    background-repeat: no-repeat !important;
    background-size: cover !important;
    color: var(--bz-text);
}

[data-bz-theme="nextgen"] .content-wraper,
[data-bz-theme="dark"] .content-wraper {
    background: transparent !important;
}

/* ---------------------------------------------------------------------------
   2. SIDEBAR
   Standard ships a slate column (#0F172A -> #1E293B). Modern moves it to the
   saturated blue of the brief; Dark keeps a near-black blue so the sidebar
   does not glow brighter than the content it frames.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation,
[data-bz-theme="dark"] .sideNavigation {
    background: var(--bz-sidebar-grad) !important;
    border: 1px solid var(--bz-hairline) !important;
    border-radius: 20px !important;
    box-shadow: var(--bz-shadow-lg) !important;
}

/* Resting menu row. */
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a,
[data-bz-theme="dark"] .sideNavigation > ul > li > a {
    color: var(--bz-sidebar-dim) !important;
    border-radius: 12px !important;
    margin: 2px 10px !important;
    transition: background var(--bz-t) var(--bz-ease),
                color var(--bz-t) var(--bz-ease) !important;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li > a .flText,
[data-bz-theme="dark"] .sideNavigation > ul > li > a .flText {
    color: inherit !important;
    font-weight: 500 !important;
    letter-spacing: .1px !important;
}

/* Hover. */
[data-bz-theme="nextgen"] .sideNavigation > ul > li:hover > a,
[data-bz-theme="dark"] .sideNavigation > ul > li:hover > a {
    background: var(--bz-sidebar-hover-bg) !important;
    color: var(--bz-sidebar-ink) !important;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li:hover .flText,
[data-bz-theme="dark"] .sideNavigation > ul > li:hover .flText {
    color: var(--bz-sidebar-ink) !important;
}

/* Open / active row - the solid brand pill from the brief.
   Separate from :hover on purpose: if active and hover shared one fill, the
   pointer would erase the "you are here" signal the moment it entered the
   menu - the single most common regression in a sidebar restyle. */
[data-bz-theme="nextgen"] .sideNavigation > ul > li.is-open > a,
[data-bz-theme="dark"] .sideNavigation > ul > li.is-open > a {
    background: var(--bz-sidebar-active-grad) !important;
    color: #FFFFFF !important;
    box-shadow: var(--bz-shadow-brand) !important;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li.is-open > a .flText,
[data-bz-theme="dark"] .sideNavigation > ul > li.is-open > a .flText {
    color: #FFFFFF !important;
    font-weight: 600 !important;
}

/* Icons follow the row ink. :not(.bz-menu-caret) mirrors how menu-modern.css
   addresses these, so the disclosure chevron keeps its own treatment. */
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a > i:not(.bz-menu-caret),
[data-bz-theme="dark"] .sideNavigation > ul > li > a > i:not(.bz-menu-caret),
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a > span[class*="lnr"],
[data-bz-theme="dark"] .sideNavigation > ul > li > a > span[class*="lnr"] {
    color: inherit !important;
    opacity: .92 !important;
}

/* Flyout submenus - these float over CONTENT, so they need an opaque surface
   of their own, not the sidebar gradient. */
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl,
[data-bz-theme="dark"] .sideNavigation .submenu-fl {
    background: var(--bz-surface) !important;
    border: 1px solid var(--bz-border) !important;
    border-radius: 14px !important;
    box-shadow: var(--bz-shadow-lg) !important;
}

[data-bz-theme="nextgen"] .sideNavigation .submenu-fl > li > a,
[data-bz-theme="dark"] .sideNavigation .submenu-fl > li > a {
    color: var(--bz-text) !important;
    border-radius: 9px !important;
}

/* --bz-primary-fill, NOT --bz-primary. In Dark --bz-primary is the LIGHTENED
   text blue (#60A5FA); white on it measures 2.54:1, which fails even the 3:1
   non-text minimum. The fill/ink pair is AA in both themes - see the note in
   design-system.css. */
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl > li:hover > a,
[data-bz-theme="dark"] .sideNavigation .submenu-fl > li:hover > a {
    background: var(--bz-primary-fill) !important;
    color: var(--bz-on-primary) !important;
}

/* ---------------------------------------------------------------------------
   3. HEADER
--------------------------------------------------------------------------- */
/* [2026-09-11] backdrop-filter REMOVED from the header, deliberately.

   It used to carry
       backdrop-filter: saturate(160%) blur(var(--bz-blur));
   for a glass effect. backdrop-filter creates a CONTAINING BLOCK for
   absolutely-positioned descendants, and the header hosts the menu-search
   results panel - a JavaScript-positioned popup. DevExpress and the search
   script both compute popup coordinates against the document, so introducing
   a new containing block silently relocates the panel away from its input.
   A dropdown landing in the wrong place was reported on this build; whether or
   not this header was the cause, a glass effect is not worth that hazard on
   the one element present on every screen.

   The header is now an opaque gradient, which also reads better: a blurred
   translucent bar over a dark page is nearly indistinguishable from a flat
   one, so the effect was costing risk for almost no visual return.
   backdrop-filter is still used, but only on floating layers that contain no
   positioned widgets - see theme-dark-polish.css section 5. */
[data-bz-theme="nextgen"] .headerMain,
[data-bz-theme="dark"] .headerMain {
    background: var(--bz-surface) !important;
    border-bottom: 1px solid var(--bz-hairline) !important;
    box-shadow: var(--bz-shadow-sm) !important;
    color: var(--bz-text) !important;
}

[data-bz-theme="nextgen"] .headerMain .dateTime,
[data-bz-theme="dark"] .headerMain .dateTime,
[data-bz-theme="nextgen"] .bds-user-name,
[data-bz-theme="dark"] .bds-user-name,
[data-bz-theme="nextgen"] .bds-welcome-word,
[data-bz-theme="dark"] .bds-welcome-word {
    color: var(--bz-text) !important;
}

/* The header search pill. */
[data-bz-theme="nextgen"] .headerMain .inputcontainer,
[data-bz-theme="dark"] .headerMain .inputcontainer,
[data-bz-theme="nextgen"] .middleWraper .input-group,
[data-bz-theme="dark"] .middleWraper .input-group {
    background: var(--bz-surface) !important;
    border: 1px solid var(--bz-border) !important;
    border-radius: var(--bz-r-pill) !important;
    box-shadow: var(--bz-shadow-sm) !important;
}

[data-bz-theme="nextgen"] .middleWraper .form-control,
[data-bz-theme="dark"] .middleWraper .form-control {
    background: transparent !important;
    border: 0 !important;
    box-shadow: none !important;
    color: var(--bz-text) !important;
}

/* Profile dropdown. */
[data-bz-theme="nextgen"] .profDrop,
[data-bz-theme="dark"] .profDrop,
[data-bz-theme="nextgen"] .dropdown-menu,
[data-bz-theme="dark"] .dropdown-menu {
    background: var(--bz-surface) !important;
    border: 1px solid var(--bz-border) !important;
    border-radius: 14px !important;
    box-shadow: var(--bz-shadow-lg) !important;
    color: var(--bz-text) !important;
}

[data-bz-theme="nextgen"] .dropdown-menu > li > a,
[data-bz-theme="dark"] .dropdown-menu > li > a,
[data-bz-theme="nextgen"] .dropdown-item,
[data-bz-theme="dark"] .dropdown-item {
    color: var(--bz-text) !important;
    border-radius: 8px !important;
}

[data-bz-theme="nextgen"] .dropdown-menu > li > a:hover,
[data-bz-theme="dark"] .dropdown-menu > li > a:hover,
[data-bz-theme="nextgen"] .dropdown-item:hover,
[data-bz-theme="dark"] .dropdown-item:hover {
    background: var(--bz-bg-2) !important;
    color: var(--bz-primary) !important;
}

/* ---------------------------------------------------------------------------
   4. PAGE-TITLE PLATE - REMOVED [2026-09-11], AND WHY IT MUST NOT COME BACK
   ---------------------------------------------------------------------------
   This section used to target .dashboardHighlightWrap as if it were the wide
   gradient title banner from the design brief:

       [data-bz-theme="nextgen"] .dashboardHighlightWrap {
           background-image: var(--bz-hero-grad) !important;
           border: 1px solid ...; border-radius: var(--bz-r-xl) !important;
           box-shadow: ...; color: var(--bz-hero-ink) !important;
           overflow: hidden !important;
       }

   That was inferred from the CLASS NAME and is wrong. In
   ~/Views/Shared/_Layout.cshtml it is:

       <section class="content-wraper">
           <div class="dashboardHighlightWrap">
               @RenderBody()
           </div>
       </section>

   It is the MAIN CONTENT CONTAINER for every page in the portal, not a banner.
   The rule therefore:

     * painted a hero gradient across the whole page body, which is the large
       empty coloured slab that appeared above the dashboard content;
     * wrapped every screen in a 22px-radius border;
     * forced `color` on everything that inherits, dragging unrelated text to
       the heading ink;
     * set `overflow: hidden`, which CLIPS any flyout, dropdown or popup that
       extends past the content box;
     * changed the element's height - and _Layout.cshtml measures exactly that
       height in JavaScript to size the sidebar:
           var menuHeight = $('.dashboardHighlightWrap').height() + 8;
           $('.sideNavigation').css({'min-height': menuHeight + 'px'});
       so a purely cosmetic rule silently moved a JS-computed layout value.

   fsm-dashboard-cc.css already says what this element is - it resets it to a
   flat page canvas with `background-image: none !important`. That was the
   clue, and it was there before this rule was written.

   THE LESSON: never infer an element's ROLE from its class name in this
   codebase. Read the markup that uses it first. There is no generic
   "page title banner" class in the portal - the banner in the brief is
   Command Center markup, and Command Center is deliberately excluded from
   this stylesheet by the menu rule.
--------------------------------------------------------------------------- */

/* ---------------------------------------------------------------------------
   5. GENERIC SURFACES
   ---------------------------------------------------------------------------
   [2026-09-11] NO !important FROM HERE DOWN - this is deliberate.

   The first revision marked every declaration in this file !important. That
   was right for the sidebar (menu-modern.css uses !important, which beats any
   specificity) but wrong for generic components, because it also beat pages
   that ship their OWN complete design and defend it with !important -
   fsm-dashboard-cc.css being the clearest case: it deliberately restyles the
   FSM dashboard to match the Command Center, and it is linked through
   @RenderSection("HeadResources") at _Layout.cshtml line 191, while this file
   is linked at line 795. Loading later AND carrying !important meant a
   generic theme rule silently outranked a purpose-built page design.

   Without !important these rules are [attribute + class] = (0,2,0). That
   still beats a plain .panel (0,1,0), so the theme reaches everything that
   has no opinion - but any page that states an opinion with !important keeps
   it. The theme cooperates instead of steamrolling.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .panel,
[data-bz-theme="dark"] .panel,
[data-bz-theme="nextgen"] .well,
[data-bz-theme="dark"] .well,
[data-bz-theme="nextgen"] .card,
[data-bz-theme="dark"] .card {
    background-image: var(--bz-surface-grad);
    background-color: var(--bz-surface);
    border: 1px solid var(--bz-border);
    border-radius: var(--bz-r-lg);
    box-shadow: var(--bz-shadow);
    color: var(--bz-text);
}

[data-bz-theme="nextgen"] .panel-heading,
[data-bz-theme="dark"] .panel-heading,
[data-bz-theme="nextgen"] .card-header,
[data-bz-theme="dark"] .card-header {
    background: transparent;
    border-bottom: 1px solid var(--bz-border);
    color: var(--bz-heading);
    font-weight: 700;
}

[data-bz-theme="nextgen"] .modal-content,
[data-bz-theme="dark"] .modal-content {
    background: var(--bz-surface);
    border: 1px solid var(--bz-border);
    border-radius: var(--bz-r-lg);
    box-shadow: var(--bz-shadow-lg);
    color: var(--bz-text);
}

[data-bz-theme="nextgen"] .modal-header,
[data-bz-theme="dark"] .modal-header,
[data-bz-theme="nextgen"] .modal-footer,
[data-bz-theme="dark"] .modal-footer {
    border-color: var(--bz-border);
}

/* ---------------------------------------------------------------------------
   6. NAV / TABS / PAGINATION
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .nav-tabs > li > a,
[data-bz-theme="dark"] .nav-tabs > li > a {
    color: var(--bz-muted);
    border: 0;
    border-radius: var(--bz-r-pill);
}

[data-bz-theme="nextgen"] .nav-tabs > li.active > a,
[data-bz-theme="dark"] .nav-tabs > li.active > a {
    background: var(--bz-btn-grad);
    color: #FFFFFF;
    box-shadow: var(--bz-shadow-brand);
}

[data-bz-theme="nextgen"] .pagination > li > a,
[data-bz-theme="dark"] .pagination > li > a,
[data-bz-theme="nextgen"] .pagination > li > span,
[data-bz-theme="dark"] .pagination > li > span {
    background: var(--bz-surface);
    border: 1px solid var(--bz-border);
    color: var(--bz-text);
    border-radius: 10px;
    margin: 0 3px;
}

/* [2026-09-11] Same guard as tables.css: a pager member with no content must
   not become a box. Bootstrap's own pagination does give resting items a
   border in Standard, so this rule is consistent with it - but an EMPTY one is
   invisible on white and would not be on a themed ground. */
[data-bz-theme="nextgen"] .pagination > li > a:empty,
[data-bz-theme="dark"] .pagination > li > a:empty,
[data-bz-theme="nextgen"] .pagination > li > span:empty,
[data-bz-theme="dark"] .pagination > li > span:empty {
    background: transparent;
    border-color: transparent;
    box-shadow: none;
    padding: 0;
    margin: 0;
}

[data-bz-theme="nextgen"] .pagination > .active > a,
[data-bz-theme="dark"] .pagination > .active > a,
[data-bz-theme="nextgen"] .pagination > .active > span,
[data-bz-theme="dark"] .pagination > .active > span {
    background: var(--bz-btn-grad);
    border-color: transparent;
    color: #FFFFFF;
}

/* ===========================================================================
   [2026-09-18] MODERN / DARK SIDEBAR - GLASS RAIL

   A redesign of the rail to the supplied reference: a saturated blue column,
   rounded rows, a lit pill on the active item, a soft wave at the foot and a
   glass collapse bar. Modern and Dark BOTH take it; Standard is named in no
   selector here and is untouched.

   EVERY COLOUR COMES FROM THE SIDEBAR TOKENS that design-system.css already
   defines per theme, which is what makes one block serve both appearances:

       --bz-sidebar-grad         the column          Modern #0B2F8E -> #041640
                                                     Dark   #101C36 -> #070E1D
       --bz-sidebar-ink          full-strength label
       --bz-sidebar-dim          resting label
       --bz-sidebar-hover-bg     the hover wash
       --bz-sidebar-active-grad  the active pill

   Nothing here invents a hex for a surface. The two literals that ARE here are
   white at low alpha - glass highlights and the wave - and white over either
   gradient is the same effect in both themes, which is the point of using it.

   THE WAVE IS GRADIENTS, NOT AN SVG DATA URI. An inline SVG would draw a
   crisper crest, but it has to be URL-encoded and a single unescaped '#' or '<'
   makes the whole declaration invalid and silently draws nothing. Two stacked
   radial gradients cannot fail that way and read as the same soft swell. This
   is section 77's rule: when you cannot look at the result, take the
   construction with no failure mode.

   ::before and ::after on .sideNavigation were both free - checked; the only
   pseudo-elements in menu-modern.css sit on one anchor for the Custom chip.

   backdrop-filter is Chrome 76 and the floor here is 59, so it is used as
   PROGRESSIVE ENHANCEMENT only: every surface that carries it also carries a
   real background, so an older browser loses the blur and nothing else. The
   same pattern menu-modern.css already uses on .bz-menu-toggle.
   =========================================================================== */

/* ---- the column ---------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation,
[data-bz-theme="dark"] .sideNavigation {
    position: relative;
    overflow-x: hidden;               /* the wave must not widen the rail */
    /* A lit top edge and a darker foot, over the token gradient. The inset
       hairline is what reads as "glass" rather than "painted panel". */
    /* Four layers, each doing one job: a lit top edge, a lit right edge, a
       DARK floor so the column has a bottom rather than fading out, and the
       cast shadow onto the page. The floor is what was missing - a gradient
       that only ever gets lighter reads as flat no matter how saturated it is. */
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .12),
                inset -1px 0 0 rgba(255, 255, 255, .06),
                inset 0 -70px 60px -60px rgba(2, 8, 23, .75),
                0 18px 45px rgba(2, 8, 23, .40) !important;
}

/* Ambient light from the top-left, so the column is not a flat fill. */
[data-bz-theme="nextgen"] .sideNavigation::before,
[data-bz-theme="dark"] .sideNavigation::before {
    content: "";
    position: absolute;
    left: 0;
    right: 0;
    top: 0;
    height: 320px;
    pointer-events: none;
    z-index: 0;
    background:
        radial-gradient(120% 70% at 12% 0%, rgba(255, 255, 255, .13), transparent 62%),
        radial-gradient(80% 50% at 96% 6%, rgba(125, 211, 252, .10), transparent 70%);
}

/* The swell at the foot of the rail. */
[data-bz-theme="nextgen"] .sideNavigation::after,
[data-bz-theme="dark"] .sideNavigation::after {
    content: "";
    position: absolute;
    left: -10%;
    right: -10%;
    bottom: 0;
    height: 230px;
    pointer-events: none;
    z-index: 0;
    background:
        radial-gradient(60% 88px at 28% 100%, rgba(255, 255, 255, .11), transparent 72%),
        radial-gradient(70% 104px at 78% 100%, rgba(255, 255, 255, .08), transparent 74%),
        radial-gradient(120% 150px at 50% 118%, rgba(255, 255, 255, .06), transparent 70%);
}

/* Content rides above both decorations. Without this the list would sit
   underneath them and the whole rail would look hazed. */
[data-bz-theme="nextgen"] .sideNavigation > ul,
[data-bz-theme="dark"] .sideNavigation > ul {
    position: relative;
    z-index: 1;
}

/* ---- rows ---------------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a,
[data-bz-theme="dark"] .sideNavigation > ul > li > a {
    position: relative;
    margin: 3px 12px !important;
    padding: 10px 12px !important;
    border-radius: 12px !important;
    /* A resting row now sits very slightly INTO the column. Against that, the
       active pill reads as raised rather than merely a different colour -
       depth from two directions instead of one. */
    background: rgba(2, 8, 23, .10) !important;
    border: 1px solid rgba(255, 255, 255, .04) !important;
    font-weight: 500 !important;
    -webkit-transition: background .16s ease, color .16s ease,
                        border-color .16s ease, left .16s ease;
    transition: background .16s ease, color .16s ease,
                border-color .16s ease, left .16s ease;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li:hover > a,
[data-bz-theme="dark"] .sideNavigation > ul > li:hover > a {
    background: var(--bz-sidebar-hover-bg) !important;
    border-color: rgba(255, 255, 255, .12) !important;
    color: var(--bz-sidebar-ink) !important;
    /* `left`, NOT transform: the containing-block audit is right that a
       transform on a menu row would make it the anchor for any fixed or
       absolute descendant - a DevExpress dropdown opened from inside the rail
       would then be positioned against the row instead of the viewport. The
       row is already position:relative, so this is the same 2px nudge with
       none of that. */
    left: 2px;
}

/* ---- the active pill ------------------------------------------------------ */
[data-bz-theme="nextgen"] .sideNavigation > ul > li.active > a,
[data-bz-theme="nextgen"] .sideNavigation > ul > li.is-open > a,
[data-bz-theme="dark"] .sideNavigation > ul > li.active > a,
[data-bz-theme="dark"] .sideNavigation > ul > li.is-open > a {
    background: var(--bz-sidebar-active-grad) !important;
    border-color: rgba(255, 255, 255, .20) !important;
    color: #FFFFFF !important;
    font-weight: 600 !important;
    /* lit top edge + cast glow: the pill sits ON the column, not in it */
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .28),
                0 8px 20px rgba(2, 8, 23, .34) !important;
}

/* ---- icons --------------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a > i,
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a > span[class*="lnr"],
[data-bz-theme="dark"] .sideNavigation > ul > li > a > i,
[data-bz-theme="dark"] .sideNavigation > ul > li > a > span[class*="lnr"] {
    opacity: .85 !important;
    -webkit-transition: opacity .16s ease;
    transition: opacity .16s ease;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li:hover > a > i,
[data-bz-theme="nextgen"] .sideNavigation > ul > li.active > a > i,
[data-bz-theme="dark"] .sideNavigation > ul > li:hover > a > i,
[data-bz-theme="dark"] .sideNavigation > ul > li.active > a > i {
    opacity: 1 !important;
}

/* ---- chevron ------------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a .bz-menu-caret,
[data-bz-theme="dark"] .sideNavigation > ul > li > a .bz-menu-caret {
    opacity: .55;
    -webkit-transition: opacity .16s ease, left .16s ease;
    transition: opacity .16s ease, left .16s ease;
}

[data-bz-theme="nextgen"] .sideNavigation > ul > li:hover > a .bz-menu-caret,
[data-bz-theme="dark"] .sideNavigation > ul > li:hover > a .bz-menu-caret {
    opacity: 1;
    position: relative;
    left: 2px;
}

/* ---- divider ------------------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation > ul > li.bz-menu-divider,
[data-bz-theme="dark"] .sideNavigation > ul > li.bz-menu-divider {
    height: 1px !important;
    margin: 10px 18px !important;
    border: 0 !important;
    /* fades out at both ends instead of stopping dead against the edge */
    background: linear-gradient(90deg,
                rgba(255, 255, 255, 0) 0%,
                rgba(255, 255, 255, .18) 22%,
                rgba(255, 255, 255, .18) 78%,
                rgba(255, 255, 255, 0) 100%) !important;
}

/* ---- the collapse bar ----------------------------------------------------- */
/* menu-modern.css pins this to a fixed #0F172A. On the blue column that reads
   as a black strip glued to the foot; it should be part of the glass. */
[data-bz-theme="nextgen"] .bz-menu-toggle,
[data-bz-theme="dark"] .bz-menu-toggle {
    background: rgba(255, 255, 255, .08) !important;
    border-top: 1px solid rgba(255, 255, 255, .14) !important;
    color: var(--bz-sidebar-ink) !important;
    /* No backdrop-filter here: menu-modern.css already blurs this element, and
       restating it would make the theme layer responsible for a containing
       block it does not need. The glass is the translucent fill above. */
    -webkit-transition: background .16s ease;
    transition: background .16s ease;
}

[data-bz-theme="nextgen"] .bz-menu-toggle:hover,
[data-bz-theme="dark"] .bz-menu-toggle:hover {
    background: rgba(255, 255, 255, .14) !important;
}

/* ---- motion preference ----------------------------------------------------- */
@media (prefers-reduced-motion: reduce) {
    [data-bz-theme="nextgen"] .sideNavigation > ul > li > a,
    [data-bz-theme="dark"] .sideNavigation > ul > li > a,
    [data-bz-theme="nextgen"] .sideNavigation > ul > li > a .bz-menu-caret,
    [data-bz-theme="dark"] .sideNavigation > ul > li > a .bz-menu-caret {
        -webkit-transition: none;
        transition: none;
    }
    [data-bz-theme="nextgen"] .sideNavigation > ul > li:hover > a,
    [data-bz-theme="dark"] .sideNavigation > ul > li:hover > a,
    [data-bz-theme="nextgen"] .sideNavigation > ul > li:hover > a .bz-menu-caret,
    [data-bz-theme="dark"] .sideNavigation > ul > li:hover > a .bz-menu-caret {
        left: 0;
    }
}


/* ===========================================================================
   [2026-09-18] (A) THE FLYOUTS JOIN THE RAIL

   Reported with an X across the submenu: level 2 came out blue and level 3
   white, so the menu read as two unrelated things bolted together.

   The earlier fix made every flyout var(--bz-surface) - white in Modern - to
   get it out of the dark-on-dark state. That solved legibility and created
   this: a white card hanging off a blue glass column.

   They are now the SAME material as the rail, stated as a pair so the surface
   and the ink can never again be decided by different files:

       surface  --bz-sidebar-from   Modern #061B55   Dark #0A1633
       ink      --bz-sidebar-ink    light in both

   A SOLID colour is the base, with the translucency and blur layered ON TOP as
   enhancement. That order matters: backdrop-filter is Chrome 76 and this app's
   floor is 59, so an older browser must still get an opaque panel over page
   content rather than a see-through one. Same discipline menu-modern.css uses.

   Specificity is above every legacy rule, including the (0,4,2) !important
   stage-3 background in menu-modern.css - see the note further up this file.
   =========================================================================== */
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl,
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl.stage3,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl.stage3 {
    background-color: var(--bz-sidebar-from) !important;
    /* Order matters, top layer first: the lit top edge, then the diamond
       lattice, then a floor shadow that gives the panel a bottom. Without that
       last stop the panel is a flat rectangle of one colour - which is what
       "depth of colour missed" was pointing at. */
    background-image:
        linear-gradient(180deg, rgba(255, 255, 255, .09) 0%, rgba(255, 255, 255, 0) 38%),
        repeating-linear-gradient(45deg,
            rgba(255, 255, 255, .05) 0, rgba(255, 255, 255, .05) 1px,
            transparent 1px, transparent 38px),
        repeating-linear-gradient(-45deg,
            rgba(255, 255, 255, .05) 0, rgba(255, 255, 255, .05) 1px,
            transparent 1px, transparent 38px),
        linear-gradient(180deg, rgba(2, 8, 23, 0) 55%, rgba(2, 8, 23, .30) 100%) !important;
    /* 38px on a panel against 54px on the rail. The lattice is the same motif
       at the same angle, but a 268px column and a 240px flyout are different
       canvases - at 54px a flyout shows barely two crossings and reads as a
       stray scratch rather than a pattern. Geometry is per surface. */
    border: 1px solid rgba(255, 255, 255, .16) !important;
    border-radius: 14px !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .16),
                inset 0 -1px 0 rgba(2, 8, 23, .35),
                0 22px 52px rgba(2, 8, 23, .55) !important;
    /* No backdrop-filter. The containing-block audit is right: it would make
       the flyout the anchor for any fixed or absolute descendant, and a
       DevExpress dropdown opened from a menu row would position against the
       panel instead of the viewport. The glass here is the solid base plus
       the top-light gradient, the hairline border and the cast shadow -
       which is the whole effect on a floor that has no blur anyway. */
}

/* Level 3 is ELEVATED above level 2, not painted the same. Two panels of one
   colour touching at an edge read as a single shape with a line through it;
   a lighter face and a deeper shadow read as one lying on the other. The
   selector already outranks the level-2 rule above it - (0,5,0) against
   (0,4,0) - so this is a refinement of it, not a fight with it. */
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl.stage3,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl.stage3 {
    background-color: var(--bz-sidebar-to) !important;
    background-image:
        linear-gradient(180deg, rgba(255, 255, 255, .13) 0%, rgba(255, 255, 255, 0) 34%),
        repeating-linear-gradient(45deg,
            rgba(255, 255, 255, .055) 0, rgba(255, 255, 255, .055) 1px,
            transparent 1px, transparent 34px),
        repeating-linear-gradient(-45deg,
            rgba(255, 255, 255, .055) 0, rgba(255, 255, 255, .055) 1px,
            transparent 1px, transparent 34px),
        linear-gradient(180deg, rgba(2, 8, 23, 0) 58%, rgba(2, 8, 23, .34) 100%) !important;
    border-color: rgba(255, 255, 255, .22) !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .20),
                inset 0 -1px 0 rgba(2, 8, 23, .38),
                0 28px 64px rgba(2, 8, 23, .62) !important;
}

[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl > li > a,
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl.stage3 > li > a,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl > li > a,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl.stage3 > li > a {
    color: var(--bz-sidebar-ink) !important;
    border-radius: 9px !important;
    border-left: 2px solid transparent !important;
}

[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl > li:hover > a,
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl.stage3 > li:hover > a,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl > li:hover > a,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl.stage3 > li:hover > a {
    background: var(--bz-sidebar-active-grad) !important;
    border-left-color: rgba(255, 255, 255, .55) !important;
    color: #FFFFFF !important;
}

/* The muted second line inside a flyout row. */
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl > li > a .dpvsl,
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl.submenu-fl.stage3 > li > a .dpvsl,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl > li > a .dpvsl,
[data-bz-theme="dark"] .sideNavigation .submenu-fl.submenu-fl.stage3 > li > a .dpvsl {
    color: var(--bz-sidebar-dim) !important;
}


/* ===========================================================================
   [2026-09-18] (B) THE DIAMOND TEXTURE, ON THE MENU AND ON EVERY PAGE

   Asked for: the diamond motif from the sign-in hero, carried through the menu
   and all pages, in Modern and Dark. Standard is in no selector here.

   WHY A LATTICE AND NOT THE HERO'S OWN SVG. .bz-ng-tex--panel is a 1600x900
   URL-encoded SVG: specific diamonds at specific coordinates, composed for one
   large panel. Stretched down a 268px rail it crops to a fragment, and behind a
   full page it scales into something unrecognisable. A 45-degree crosshatch IS
   the diamond lattice that artwork is built from, it tiles at any size, and -
   the decisive part - it cannot fail the way a data URI can. One unescaped '#'
   in an encoded SVG and the whole declaration is invalid and silently draws
   nothing. Section 77: prefer the construction with no failure mode.

   THE LINE COLOUR CANNOT BE SHARED between the two hosts. The rail is a dark
   column, so the lattice is white at low alpha. The page ground in Modern is a
   near-white wash, where white lines are invisible - it gets a blue-tinted
   dark line instead. Dark's page is dark, so it goes back to white. Three
   declarations, each measured against what is actually behind it.
   =========================================================================== */

/* ---- the rail: lattice folded into the ambient-light layer it already owns */
[data-bz-theme="nextgen"] .sideNavigation::before,
[data-bz-theme="dark"] .sideNavigation::before {
    height: auto;
    bottom: 0;
    background:
        radial-gradient(120% 70% at 12% 0%, rgba(255, 255, 255, .13), transparent 62%),
        radial-gradient(80% 50% at 96% 6%, rgba(125, 211, 252, .10), transparent 70%),
        repeating-linear-gradient(45deg,
            rgba(255, 255, 255, .055) 0, rgba(255, 255, 255, .055) 1px,
            transparent 1px, transparent 54px),
        repeating-linear-gradient(-45deg,
            rgba(255, 255, 255, .055) 0, rgba(255, 255, 255, .055) 1px,
            transparent 1px, transparent 54px);
}

/* ---- every page: the wrapper is already transparent, so the tinted body
        wash still reads through the lattice rather than being covered by it */
[data-bz-theme="nextgen"] .content-wraper {
    background-color: transparent !important;
    background-image:
        repeating-linear-gradient(45deg,
            rgba(37, 99, 235, .050) 0, rgba(37, 99, 235, .050) 1px,
            transparent 1px, transparent 62px),
        repeating-linear-gradient(-45deg,
            rgba(37, 99, 235, .050) 0, rgba(37, 99, 235, .050) 1px,
            transparent 1px, transparent 62px) !important;
    /* fixed, so the lattice does not slide under long grids and band at the
       scroll seam - the same reason body carries fixed attachment */
    background-attachment: fixed !important;
}

[data-bz-theme="dark"] .content-wraper {
    background-color: transparent !important;
    background-image:
        repeating-linear-gradient(45deg,
            rgba(255, 255, 255, .035) 0, rgba(255, 255, 255, .035) 1px,
            transparent 1px, transparent 62px),
        repeating-linear-gradient(-45deg,
            rgba(255, 255, 255, .035) 0, rgba(255, 255, 255, .035) 1px,
            transparent 1px, transparent 62px) !important;
    background-attachment: fixed !important;
}


/* ===========================================================================
   [2026-09-18] (C) MATCHING THE SUPPLIED REFERENCE - NEXTGEN + DARK

   A clean, standalone reference (not a composite) showed four concrete
   differences from what section 3 built, corrected here. All four apply to
   BOTH nextgen and dark, per instruction - only Standard is out of scope, and
   no selector below can reach it: menu-modern.css owns Standard's own
   .sideNavigation entirely and nothing here touches that file.

   REVERSES A PRIOR MISTAKE: an earlier pass (now deleted, it never shipped
   past this file) gave Command Center / Report Center / BreezeFSM Guide a
   white card and a coloured icon badge, read off an earlier COMPOSITE
   screenshot. The clean reference shows them as PLAIN rows - same ink, same
   icon treatment, same everything as Dashboard onward, no card. Deleting that
   section restores them to the shared row rule below by itself; nothing
   further was needed for that part.

   (1) RESTING ROWS GO FLAT. The reference has no background box and no
       border on a resting row - bare icon + text + chevron directly on the
       gradient. Section 3's shared rule (nextgen AND dark, one declaration)
       cannot be edited in place without moving both, so this overrides it
       for both, after it, at equal specificity - the standard way a later
       declaration in the same file beats an earlier one of the same weight.

   (2) THE CHEVRON GETS A COLOUR, NOT JUST AN OPACITY. menu-modern.css sets
       .bz-menu-caret and the nested .dpvsl arrow to #475569 (line ~286) -
       a slate grey chosen for ITS OWN dark-slate rail, with !important, and
       nothing before this ever gave nextgen or dark a colour of their own -
       section 3 only ever touched opacity. #475569 on a blue rail is close
       to the same luminance as the rail itself: functionally invisible,
       independent of whether a given row actually has a submenu. Reusing
       --bz-sidebar-ink (the same token the row's own hover/active text
       already uses) makes it visible and keeps it consistent with the rest
       of the rail's ink.

   (3) THE BASE BLUE LIFTS AT THE TOP. --bz-sidebar-grad's top stop is
       redeclared brighter, scoped to .sideNavigation - checked first: this
       custom property has exactly ONE consumer anywhere in the CSS
       (theme-shell.css's own ".sideNavigation { background: var(...) }",
       section 3 above), so redeclaring it here cannot reach anything else,
       and design-system.css's own definition is untouched. Each theme keeps
       ITS OWN --bz-brand-600 as the new top stop - nextgen's #1340BE, dark's
       #2049A8 - already-defined tokens in the same palette family, not an
       invented colour, and dark's own value stays the more muted of the two
       on purpose: this file's own established rule for dark (see the hover
       note elsewhere in this stylesheet) is that a light UI can take a bright
       fill where a dark one reads it as glare, so dark is lifted by the same
       token step, never pushed as bright as nextgen.

   (4) THE COLLAPSE BAR GETS TEXTURE, NOT A FLAT WASH, AND KEEPS ITS OWN
       GEOMETRY. Checked before writing this: .bz-menu-toggle is a <body>
       child, position:fixed to the WINDOW (main.js's own 2026-08-01 comment
       explains why - .sideNavigation's backdrop-filter would otherwise make
       IT the containing block). The wave decoration section (B) built lives
       on .sideNavigation::after instead, and .sideNavigation itself is a
       fixed-height, max-height:82vh, overflow-y:auto panel (menu-modern.css
       line ~152) - so that decoration sits at the bottom of the INTERNAL
       SCROLL, not the visible bottom of the screen, and is only reachable by
       scrolling the menu list itself past every item. That is why no wave
       ever appeared near Collapse: the two were never the same physical
       region of the page. Repainting the texture directly onto .bz-menu-toggle
       - which IS reliably fixed at the visible bottom - fixes the position
       for good along with the visibility. Two stacked radial gradients again
       (section 77: no SVG data-URI, nothing here can fail to render), plus a
       circular chip around the existing <i class="fa fa-angle-double-left">
       icon - the same element main.js already builds, no markup touched.
   =========================================================================== */

/* ---- (1) flat resting rows ------------------------------------------------ */
[data-bz-theme="nextgen"] .sideNavigation > ul > li > a,
[data-bz-theme="dark"] .sideNavigation > ul > li > a {
    background: transparent !important;
    border: 1px solid transparent !important;
}

/* ---- (2) visible chevron -------------------------------------------------- */
[data-bz-theme="nextgen"] .sideNavigation .bz-menu-caret,
[data-bz-theme="nextgen"] .sideNavigation .submenu-fl > li > a .dpvsl,
[data-bz-theme="dark"] .sideNavigation .bz-menu-caret,
[data-bz-theme="dark"] .sideNavigation .submenu-fl > li > a .dpvsl {
    color: var(--bz-sidebar-ink) !important;
}

/* ---- (3) brighter top stop, scoped to the one consumer -------------------- */
[data-bz-theme="nextgen"] .sideNavigation {
    --bz-sidebar-grad: linear-gradient(180deg, #1340BE 0%, #072265 46%, #041640 100%);
}
[data-bz-theme="dark"] .sideNavigation {
    --bz-sidebar-grad: linear-gradient(180deg, #2049A8 0%, #0B1426 52%, #070E1D 100%);
}

/* ---- (4) the Collapse bar: texture, fixed to the real viewport bottom ---- */
[data-bz-theme="nextgen"] .bz-menu-toggle,
[data-bz-theme="dark"] .bz-menu-toggle {
    background:
        radial-gradient(140% 100% at 30% -20%, rgba(255, 255, 255, .22), transparent 60%),
        radial-gradient(120% 90% at 85% 120%, rgba(255, 255, 255, .12), transparent 65%),
        var(--bz-sidebar-active-grad) !important;
    border-top-color: rgba(255, 255, 255, .18) !important;
}

[data-bz-theme="nextgen"] .bz-menu-toggle:hover,
[data-bz-theme="dark"] .bz-menu-toggle:hover {
    background:
        radial-gradient(140% 100% at 30% -20%, rgba(255, 255, 255, .30), transparent 60%),
        radial-gradient(120% 90% at 85% 120%, rgba(255, 255, 255, .16), transparent 65%),
        var(--bz-sidebar-active-grad) !important;
}

[data-bz-theme="nextgen"] .bz-menu-toggle i,
[data-bz-theme="dark"] .bz-menu-toggle i {
    display: inline-flex !important;
    align-items: center !important;
    justify-content: center !important;
    width: 24px !important;
    height: 24px !important;
    flex: 0 0 24px !important;
    border-radius: 50% !important;
    background: rgba(255, 255, 255, .22) !important;
    font-size: 11px !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .35) !important;
}

/* ===========================================================================
   (H) PAGE HERO - the Sales Order header, on every page   [2026-09-26]
   ---------------------------------------------------------------------------
   Nextgen + Dark only. `.breadCumb` is the one page-title element nearly
   every page already renders (226 MyShop views, 64 ERP.UI pages; its title
   is the direct <span>, a few use <h3><span>). This turns that bar into the
   Sales Order hero - glass card, glossy icon tile, large title, layered wave
   hills on the right - with NO markup change on any page.

   Construction, chosen so nothing can mis-render:
     * Waves are hard-stopped radial-gradient ELLIPSES (Theme-System.md 78.2:
       a crisp edge is fine where the curve IS the design). Each hill is an
       ellipse centred below the card, so only its crest shows; the card's
       own border-radius clips every hill - no overflow:hidden, so nothing a
       page puts inside the bar (close button, help ring) can be clipped.
     * The icon tile is the BAR's ::before. Checked before using it: no rule
       anywhere styles .breadCumb::before/::after (the existing decoration is
       on the SPAN's pseudo-elements - the a.png corner wings - retired here
       for both themes, as theme-dark-polish.css section 15 already does for
       Dark).
     * No transform / filter / backdrop-filter (containing-block audit).

   Specificity: theme-dark-polish.css pins the bar
   (`[dark] .breadCumb { background..none !important; border:0 !important }`)
   and theme-dark-surfaces.css / section 14 pin the span, all at (0,2,0) or
   (0,2,1). The `html[...]` prefix below is one element more specific, and
   !important is used only on the properties those rules pin.

   The Sales Order page keeps its own hero (order-entry.css hides its
   breadCumb via .so-page-breadcrumb) - there is never a hero on a hero.
   =========================================================================== */
html[data-bz-theme="nextgen"] .breadCumb,
html[data-bz-theme="dark"] .breadCumb {
    position: relative;
    min-height: 84px;
    padding: 18px 24px 18px 90px;
    margin-top: 14px;
    margin-bottom: 18px;
    border-radius: 18px;
    font-size: 13px;
}

html[data-bz-theme="nextgen"] .breadCumb {
    background-color: rgba(255, 255, 255, .80);
    background-image:
        radial-gradient(60% 316% at 80% 170%, rgba(255, 255, 255, 0) 49.3%, rgba(255, 255, 255, .9) 49.6%, rgba(255, 255, 255, 0) 50.1%),
        radial-gradient(64% 250% at 70% 205%, rgba(37, 99, 235, .50) 49.6%, rgba(37, 99, 235, 0) 50%),
        radial-gradient(60% 316% at 80% 170%, rgba(59, 130, 246, .78) 49.6%, rgba(59, 130, 246, 0) 50%),
        radial-gradient(70% 240% at 98% 150%, rgba(165, 180, 252, .55) 49.6%, rgba(165, 180, 252, 0) 50%),
        radial-gradient(38% 140% at 0% 0%, rgba(255, 255, 255, .85), rgba(255, 255, 255, 0) 70%),
        linear-gradient(100deg, #F0F3FF 0%, #E8EDFF 50%, #E0EAFF 100%);
    border: 1px solid rgba(255, 255, 255, .95);
    box-shadow:
        inset 0 1px 0 rgba(255, 255, 255, .95),
        0 14px 34px rgba(37, 99, 235, .13),
        0 3px 8px rgba(15, 27, 54, .05);
}

html[data-bz-theme="dark"] .breadCumb {
    background-color: var(--bz-brand-800) !important;
    background-image:
        radial-gradient(60% 316% at 80% 170%, rgba(191, 219, 254, 0) 49.3%, rgba(191, 219, 254, .55) 49.6%, rgba(191, 219, 254, 0) 50.1%),
        radial-gradient(64% 250% at 70% 205%, rgba(37, 99, 235, .45) 49.6%, rgba(37, 99, 235, 0) 50%),
        radial-gradient(60% 316% at 80% 170%, rgba(59, 130, 246, .55) 49.6%, rgba(59, 130, 246, 0) 50%),
        radial-gradient(70% 240% at 98% 150%, rgba(129, 140, 248, .30) 49.6%, rgba(129, 140, 248, 0) 50%),
        radial-gradient(38% 140% at 0% 0%, rgba(147, 197, 253, .14), rgba(147, 197, 253, 0) 70%),
        linear-gradient(100deg, var(--bz-brand-800) 0%, var(--bz-brand-700) 100%) !important;
    border: 1px solid var(--bz-glass-brd) !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .05), 0 18px 44px rgba(0, 0, 0, .45);
}

/* Glossy app-icon tile (same recipe as the Sales Order hero icon). */
html[data-bz-theme="nextgen"] .breadCumb::before,
html[data-bz-theme="dark"] .breadCumb::before {
    content: "\f15c";
    position: absolute;
    left: 22px;
    top: 50%;
    width: 50px;
    height: 50px;
    margin-top: -25px;
    border-radius: 15px;
    background: linear-gradient(150deg, #4D9BFF 0%, #1F6BFF 50%, #0F52E6 100%);
    color: #FFFFFF;
    font-family: FontAwesome;
    font-size: 22px;
    font-weight: normal;
    line-height: 50px;
    text-align: center;
    box-shadow:
        inset 0 1px 0 rgba(255, 255, 255, .55),
        inset 0 -8px 16px rgba(15, 82, 230, .35),
        0 10px 22px rgba(31, 107, 255, .40);
}

/* The title: the old white TAB becomes plain large type on the hero. */
html[data-bz-theme="nextgen"] .breadCumb > span,
html[data-bz-theme="dark"] .breadCumb > span,
html[data-bz-theme="nextgen"] .breadCumb > h3 > span,
html[data-bz-theme="dark"] .breadCumb > h3 > span {
    display: inline-block;
    padding: 0;
    border: 0 !important;
    border-radius: 0;
    background: transparent !important;
    box-shadow: none !important;
    text-transform: none;
    font-size: 23px;
    font-weight: 800;
    line-height: 48px;
    letter-spacing: -.3px;
}

html[data-bz-theme="nextgen"] .breadCumb > span,
html[data-bz-theme="nextgen"] .breadCumb > h3 > span { color: var(--bz-heading) !important; }

html[data-bz-theme="dark"] .breadCumb > span,
html[data-bz-theme="dark"] .breadCumb > h3 > span { color: #FFFFFF !important; }

html[data-bz-theme="nextgen"] .breadCumb > h3,
html[data-bz-theme="dark"] .breadCumb > h3 { margin: 0; }

/* The a.png concave corner wings belonged to the tab, which no longer
   exists as a tab - retired in both themes (Dark already did this). */
html[data-bz-theme="nextgen"] .breadCumb > span::before,
html[data-bz-theme="nextgen"] .breadCumb > span::after,
html[data-bz-theme="nextgen"] .breadCumb > h3 > span::before,
html[data-bz-theme="nextgen"] .breadCumb > h3 > span::after,
html[data-bz-theme="dark"] .breadCumb > span::before,
html[data-bz-theme="dark"] .breadCumb > span::after,
html[data-bz-theme="dark"] .breadCumb > h3 > span::before,
html[data-bz-theme="dark"] .breadCumb > h3 > span::after {
    content: none !important;
    background: none !important;
}

/* The close button some pages put in the bar: centred on the hero's
   right edge instead of hanging off its top corner. */
html[data-bz-theme="nextgen"] .breadCumb .crossBtnN,
html[data-bz-theme="dark"] .breadCumb .crossBtnN {
    top: 50%;
    right: 18px;
    margin-top: -12px;
}

@media (max-width: 767px) {
    html[data-bz-theme="nextgen"] .breadCumb,
    html[data-bz-theme="dark"] .breadCumb { padding-left: 80px; min-height: 72px; }
    html[data-bz-theme="nextgen"] .breadCumb > span,
    html[data-bz-theme="dark"] .breadCumb > span { font-size: 19px; }
}

/* ---------------------------------------------------------------------------
   (H2) DASHBOARD SECTION HEADER as a hero   [2026-09-26]  Nextgen + Dark
   ---------------------------------------------------------------------------
   The FSM Dashboard renders no .breadCumb; its page header is the section bar
   every dashboard tab shares - `.fsm-cc-block .cc-block-head.fsm-head-bar`
   (title .fsm-head-title = <i> + .fsm-head-title-text + <small>, filters
   .fsm-head-tools; markup in DashboardAttendance*.cshtml). Same wave hills as
   (H); the block's own overflow:hidden + radius clip them. The coloured
   left rule is replaced by the icon tile. The filter strip stays transparent
   on the hero (theme-dark-polish.css paints it as a dark "sunken" slab,
   which would sit exactly where the waves are); its buttons keep their own
   solid surfaces, so they stay legible over the waves.
   --------------------------------------------------------------------------- */
html[data-bz-theme="nextgen"] .fsm-cc-block .cc-block-head.fsm-head-bar,
html[data-bz-theme="dark"] .fsm-cc-block .cc-block-head.fsm-head-bar {
    padding: 14px 18px;
    border-left: 0;
    border-bottom: 1px solid var(--bz-glass-brd);
}

html[data-bz-theme="nextgen"] .fsm-cc-block .cc-block-head.fsm-head-bar {
    background-color: #EEF2FF;
    background-image:
        radial-gradient(60% 316% at 66% 170%, rgba(255, 255, 255, 0) 49.3%, rgba(255, 255, 255, .9) 49.6%, rgba(255, 255, 255, 0) 50.1%),
        radial-gradient(64% 250% at 56% 205%, rgba(37, 99, 235, .40) 49.6%, rgba(37, 99, 235, 0) 50%),
        radial-gradient(60% 316% at 66% 170%, rgba(59, 130, 246, .62) 49.6%, rgba(59, 130, 246, 0) 50%),
        radial-gradient(70% 240% at 90% 150%, rgba(165, 180, 252, .50) 49.6%, rgba(165, 180, 252, 0) 50%),
        radial-gradient(38% 140% at 0% 0%, rgba(255, 255, 255, .85), rgba(255, 255, 255, 0) 70%),
        linear-gradient(100deg, #F0F3FF 0%, #E8EDFF 50%, #E0EAFF 100%);
}

html[data-bz-theme="dark"] .fsm-cc-block .cc-block-head.fsm-head-bar {
    background-color: var(--bz-brand-800) !important;
    background-image:
        radial-gradient(60% 316% at 66% 170%, rgba(191, 219, 254, 0) 49.3%, rgba(191, 219, 254, .5) 49.6%, rgba(191, 219, 254, 0) 50.1%),
        radial-gradient(64% 250% at 56% 205%, rgba(37, 99, 235, .40) 49.6%, rgba(37, 99, 235, 0) 50%),
        radial-gradient(60% 316% at 66% 170%, rgba(59, 130, 246, .50) 49.6%, rgba(59, 130, 246, 0) 50%),
        radial-gradient(70% 240% at 90% 150%, rgba(129, 140, 248, .28) 49.6%, rgba(129, 140, 248, 0) 50%),
        linear-gradient(100deg, var(--bz-brand-800) 0%, var(--bz-brand-700) 100%) !important;
}

html[data-bz-theme="nextgen"] .fsm-head-bar .fsm-head-title > i,
html[data-bz-theme="dark"] .fsm-head-bar .fsm-head-title > i {
    width: 38px;
    height: 38px;
    border-radius: 12px;
    background: linear-gradient(150deg, #4D9BFF 0%, #1F6BFF 50%, #0F52E6 100%);
    color: #FFFFFF !important;
    font-size: 16px;
    line-height: 38px;
    text-align: center;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .5), 0 6px 14px rgba(31, 107, 255, .32);
}

html[data-bz-theme="nextgen"] .fsm-head-bar .fsm-head-title-text,
html[data-bz-theme="dark"] .fsm-head-bar .fsm-head-title-text {
    font-size: 16px;
    font-weight: 800;
    letter-spacing: .3px;
}

html[data-bz-theme="nextgen"] .fsm-head-bar .fsm-head-title-text { color: var(--bz-heading); }
html[data-bz-theme="dark"] .fsm-head-bar .fsm-head-title-text { color: #FFFFFF !important; }

html[data-bz-theme="nextgen"] .fsm-head-bar .fsm-head-tools,
html[data-bz-theme="dark"] .fsm-head-bar .fsm-head-tools {
    background-color: transparent !important;
    background-image: none !important;
}

/* ===========================================================================
   (H3) FSM DASHBOARD - full visual redesign   [2026-09-26]  Nextgen + Dark
   ---------------------------------------------------------------------------
   Same data, same markup, same scripts - only the look. Regions and their
   real markup (read from the live page, not assumed):
     tab bar        .tabs-style-shape nav > ul.tabItemsLI > li(.active) > a > span
     KPI tiles      .mainDashBoxes.newStyleMN .widgBox.c2|c3|c5|c4 (.active)
                    > .icon > img, .lspacer > .Numb / .txt / .dtday
                    c2 Employee Strength, c3 At Work, c5 On Leave, c4 Not Logged In
     detail grid    table.dt-legacy-grid (DataTables) thead th.sorting,
                    input.dt-col-search
     action rail    ul.flotting-right-btn > li > .hoverMenu
   fsm-dashboard-cc.css styles all of these in EVERY theme, largely with
   !important; the html[data-bz-theme] prefix here out-ranks it and
   !important is used only where that file pins the property. Geometry
   (sizes, positions, the rail's slide-out) is left as that file set it.
   The grid's sort arrows are DataTables background-images on th.sorting,
   so only background-COLOR is set on header cells, never `background`.
   No transform/filter on any container (containing-block audit); the only
   filter is on the icon <img> glyphs (allowed - an image hosts nothing).
   =========================================================================== */

/* --- tab bar: a glass segmented control ------------------------------------ */
html[data-bz-theme="nextgen"] .tabs-style-shape nav > ul.tabItemsLI,
html[data-bz-theme="dark"] .tabs-style-shape nav > ul.tabItemsLI {
    width: -webkit-fit-content;
    width: fit-content;
    max-width: 100%;
    padding: 5px !important;
    border-radius: 16px;
}

html[data-bz-theme="nextgen"] .tabs-style-shape nav > ul.tabItemsLI {
    background: rgba(255, 255, 255, .78);
    border: 1px solid rgba(255, 255, 255, .95);
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .95), 0 8px 22px rgba(37, 99, 235, .10);
}

html[data-bz-theme="dark"] .tabs-style-shape nav > ul.tabItemsLI {
    background: rgba(19, 28, 46, .85);
    border: 1px solid var(--bz-glass-brd);
    box-shadow: 0 8px 22px rgba(0, 0, 0, .35);
}

html[data-bz-theme="nextgen"] .tabs-style-shape nav li a span:not(.exec-cmd-inner),
html[data-bz-theme="dark"] .tabs-style-shape nav li a span:not(.exec-cmd-inner) {
    border-radius: 12px !important;
    font-weight: 600;
}

html[data-bz-theme="dark"] .tabs-style-shape nav li:not(.active) a span:not(.exec-cmd-inner) { color: #CBD5E1 !important; }

html[data-bz-theme="dark"] .tabItemsLI li:not(.active) a:hover span:not(.exec-cmd-inner) {
    background: rgba(96, 165, 250, .12) !important;
    color: #FFFFFF !important;
}

/* :not(#bz-fb-none) = ID weight (matches everything): fsm-dashboard-cc.css
   colours each active tab with `.tabItemsLI li[id].active a:link span:not(..)
   {... !important}` = (0,5,3), which a class-only rule cannot beat. */
html[data-bz-theme="nextgen"] .tabItemsLI li.active a span:not(.exec-cmd-inner):not(#bz-fb-none),
html[data-bz-theme="dark"] .tabItemsLI li.active a span:not(.exec-cmd-inner):not(#bz-fb-none) {
    background: linear-gradient(135deg, #3B82F6 0%, #1F6BFF 55%, #0F52E6 100%) !important;
    color: #FFFFFF !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .35), 0 6px 16px rgba(31, 107, 255, .35);
}

html[data-bz-theme="nextgen"] .tabItemsLI li.active a span:not(.exec-cmd-inner):not(#bz-fb-none) > i.fa,
html[data-bz-theme="dark"] .tabItemsLI li.active a span:not(.exec-cmd-inner):not(#bz-fb-none) > i.fa { color: #FFFFFF !important; }

/* --- KPI tiles: colour-coded glass cards ------------------------------------
   Each tile: white-to-tint glass, a bloom of its colour top-right and a wave
   arc of its colour bottom-right (hard-stop ellipse, clipped by the radius). */
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox {
    border-radius: 18px !important;
    --bz-kpi: 37, 99, 235;
}

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.c3,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.c3 { --bz-kpi: 22, 163, 74; }
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.c5,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.c5 { --bz-kpi: 217, 119, 6; }
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.c4,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.c4 { --bz-kpi: 225, 29, 72; }
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.c1,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.c1 { --bz-kpi: 124, 58, 237; }

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox {
    background-color: #FFFFFF !important;
    background-image:
        radial-gradient(70% 120% at 100% 165%, rgba(var(--bz-kpi), .12) 49.6%, rgba(var(--bz-kpi), 0) 50%),
        radial-gradient(60% 75% at 100% 0%, rgba(var(--bz-kpi), .14), rgba(var(--bz-kpi), 0) 70%),
        linear-gradient(160deg, #FFFFFF 0%, #F8FAFF 100%) !important;
    border: 1px solid rgba(255, 255, 255, .95) !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .95), 0 10px 26px rgba(15, 27, 54, .07) !important;
}

html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox {
    background-color: #131C2E !important;
    background-image:
        radial-gradient(70% 120% at 100% 165%, rgba(var(--bz-kpi), .20) 49.6%, rgba(var(--bz-kpi), 0) 50%),
        radial-gradient(60% 75% at 100% 0%, rgba(var(--bz-kpi), .24), rgba(var(--bz-kpi), 0) 70%),
        linear-gradient(160deg, #1B2640 0%, #131C2E 100%) !important;
    border: 1px solid rgba(148, 163, 184, .14) !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .05), 0 10px 26px rgba(0, 0, 0, .35) !important;
}

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox:hover {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .95), 0 16px 34px rgba(var(--bz-kpi), .18) !important;
}
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox:hover {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .06), 0 16px 34px rgba(var(--bz-kpi), .28) !important;
}

/* The selected tile: a ring in its own colour. */
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.active,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.active {
    border-color: rgba(var(--bz-kpi), .55) !important;
    box-shadow: 0 0 0 3px rgba(var(--bz-kpi), .16), 0 14px 30px rgba(var(--bz-kpi), .20) !important;
}

/* Glossy gradient icon tile with a white glyph (was a flat white chip). */
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .icon,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .icon,
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.active .icon,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.active .icon {
    width: 42px !important;
    height: 42px !important;
    border-radius: 13px !important;
    border: 0 !important;
    background: linear-gradient(150deg, rgba(var(--bz-kpi), .78) 0%, rgba(var(--bz-kpi), 1) 100%) !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .45), 0 8px 18px rgba(var(--bz-kpi), .35) !important;
}

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .icon img,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .icon img {
    width: 20px;
    height: 20px;
    -webkit-filter: brightness(0) invert(1);
    filter: brightness(0) invert(1);
}

/* The Not Logged In artwork is a filled red DISC with a white power glyph,
   so a white-glyph filter turned the whole disc white (seen live). It keeps
   its own colours; the white glyph reads on the rose tile as it is. */
html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox.c4 .icon img,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox.c4 .icon img {
    -webkit-filter: none;
    filter: none;
    width: 26px;
    height: 26px;
}

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .lspacer,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .lspacer { padding-right: 54px; }

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .txt,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .txt {
    font-size: 11px !important;
    font-weight: 800 !important;
    letter-spacing: .08em;
}

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .txt { color: rgb(var(--bz-kpi)) !important; }
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .txt { color: #CBD5E1 !important; }

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .Numb,
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .Numb {
    font-size: 32px !important;
    font-weight: 800 !important;
    letter-spacing: -.5px;
}

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .Numb { color: var(--bz-heading) !important; }
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .Numb { color: #FFFFFF !important; }

html[data-bz-theme="nextgen"] .mainDashBoxes.newStyleMN .widgBox .dtday { color: #64748B !important; }
html[data-bz-theme="dark"] .mainDashBoxes.newStyleMN .widgBox .dtday { color: #94A3B8 !important; }

/* --- detail grid ------------------------------------------------------------ */
html[data-bz-theme="nextgen"] .dt-legacy-grid > thead > tr > th,
html[data-bz-theme="dark"] .dt-legacy-grid > thead > tr > th {
    font-size: 11.5px !important;
    font-weight: 800 !important;
    letter-spacing: .06em;
    text-transform: uppercase;
}

html[data-bz-theme="nextgen"] .dt-legacy-grid > thead > tr > th {
    background-color: #EEF2FF !important;
    color: #475569 !important;
}

html[data-bz-theme="dark"] .dt-legacy-grid > thead > tr > th {
    background-color: #16213A !important;
    color: #CBD5E1 !important;
}

html[data-bz-theme="nextgen"] .dt-legacy-grid > tbody > tr:hover > td { background-color: rgba(37, 99, 235, .05) !important; }
html[data-bz-theme="dark"] .dt-legacy-grid > tbody > tr:hover > td { background-color: rgba(96, 165, 250, .09) !important; }

html[data-bz-theme="nextgen"] .dt-legacy-grid .dt-col-search,
html[data-bz-theme="dark"] .dt-legacy-grid .dt-col-search {
    border-radius: 10px !important;
    transition: border-color var(--bz-t) var(--bz-ease), box-shadow var(--bz-t) var(--bz-ease);
}

html[data-bz-theme="nextgen"] .dt-legacy-grid .dt-col-search { border-color: #DCE3F1 !important; }

html[data-bz-theme="nextgen"] .dt-legacy-grid .dt-col-search:focus,
html[data-bz-theme="dark"] .dt-legacy-grid .dt-col-search:focus {
    outline: none;
    border-color: var(--bz-primary) !important;
    box-shadow: 0 0 0 3px var(--bz-ring);
}

/* --- right action rail: a frosted glass drawer ------------------------------- */
html[data-bz-theme="nextgen"] .flotting-right-btn,
html[data-bz-theme="dark"] .flotting-right-btn { border-radius: 18px 0 0 18px; }

html[data-bz-theme="nextgen"] .flotting-right-btn {
    background: rgba(255, 255, 255, .86);
    border: 1px solid rgba(255, 255, 255, .95);
    border-right: none;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .95), -10px 0 30px rgba(37, 99, 235, .14);
}

html[data-bz-theme="dark"] .flotting-right-btn {
    background: rgba(19, 28, 46, .94);
    border: 1px solid var(--bz-glass-brd);
    border-right: none;
    box-shadow: -10px 0 30px rgba(0, 0, 0, .45);
}

html[data-bz-theme="nextgen"] .flotting-right-btn li .hoverMenu,
html[data-bz-theme="dark"] .flotting-right-btn li .hoverMenu { border-radius: 12px; }

html[data-bz-theme="nextgen"] .flotting-right-btn li .hoverMenu:hover { background: linear-gradient(90deg, rgba(37, 99, 235, .10), rgba(37, 99, 235, .04)); }
html[data-bz-theme="dark"] .flotting-right-btn li .hoverMenu:hover { background: linear-gradient(90deg, rgba(96, 165, 250, .18), rgba(96, 165, 250, .06)); }

/* ---------------------------------------------------------------------------
   (H4) ONE HIGHLIGHT IN THE SIDEBAR   [2026-09-26]  Nextgen + Dark
   ---------------------------------------------------------------------------
   Reported: "by default Dashboard highlighted - wrong, should highlight on
   click". The pill (section (C) above) paints BOTH li.active (the current
   page, main.js highlightCurrentPage) and li.is-open (a section the user
   expanded), so opening Masters on the dashboard showed two selected rows.
   main.js now marks the nav `.bz-menu-has-open` while a top-level section is
   expanded; while it is, the current-page row steps back to a resting row
   and only the clicked section carries the highlight. Collapse it again and
   the current page's highlight returns.
   --------------------------------------------------------------------------- */
html[data-bz-theme="nextgen"] .sideNavigation.bz-menu-has-open > ul > li.active:not(.is-open) > a,
html[data-bz-theme="dark"] .sideNavigation.bz-menu-has-open > ul > li.active:not(.is-open) > a {
    background: transparent !important;
    border-color: transparent !important;
    box-shadow: none !important;
    color: var(--bz-sidebar-dim) !important;
    font-weight: 500 !important;
}

html[data-bz-theme="nextgen"] .sideNavigation.bz-menu-has-open > ul > li.active:not(.is-open) > a > i,
html[data-bz-theme="dark"] .sideNavigation.bz-menu-has-open > ul > li.active:not(.is-open) > a > i {
    opacity: .85 !important;
}

/* ---------------------------------------------------------------------------
   (H5) CURRENT PAGE INSIDE AN OPEN SECTION   [2026-09-26]  Nextgen + Dark
   ---------------------------------------------------------------------------
   main.js restoreOpenSection() re-opens the section that holds the current
   page on load and marks that submenu link `.bz-menu-current`. Standard gets
   the expanded section only (the menu's own .is-open); the link highlight is
   Nextgen/Dark design.
   --------------------------------------------------------------------------- */
html[data-bz-theme="nextgen"] .sideNavigation .submenu-fl a.bz-menu-current,
html[data-bz-theme="dark"] .sideNavigation .submenu-fl a.bz-menu-current {
    background: rgba(255, 255, 255, .16) !important;
    color: #FFFFFF !important;
    font-weight: 600 !important;
    border-radius: 10px;
    box-shadow: inset 3px 0 0 #93C5FD;
}
