/* ============================================================================
   theme-dx-adapter.css - DevExpress under Modern / Dark.
   [2026-09-11]

   ---------------------------------------------------------------------------
   THE GAP THIS CLOSES
   ---------------------------------------------------------------------------
   Measured against the portal markup:

       dxgv          1286 occurrences      .btn           1485
       dxgvSelectedRow 404                 .form-control   494
       dxeButtonEdit   373                 .table          105
       dxgvHeader      292

   The first cut of the theme layer contained ZERO dx* selectors for this
   project. So on every grid screen - which is most of the portal - Modern
   restyled the buttons around a grid and left the grid itself, the element
   filling most of the viewport, painted exactly as Standard. That is the
   single biggest reason the theme was reported as "almost as it was".

   ERP.UI got theme-erp-adapter.css, but its DevExpress section corrects DARK
   only, on the argument that DevExpress's light skin is already close to the
   palette. That argument holds for "do not look broken"; it does not hold for
   "look redesigned". This file therefore covers BOTH appearances.

   ---------------------------------------------------------------------------
   [2026-09-11] PROMOTED TO A PARITY FILE
   ---------------------------------------------------------------------------
   Written for MyShopProject, then measured across the solution:

       MyShopProject        5542 dx-class occurrences
       ERP.UI               1498  + 13 <dx:> controls
       TargetVsAchievement   246
       Reports                     63 <dx:> controls
       FSMMaster              49

   DevExpress is not a MyShop problem, it is a solution-wide one, and every
   selector here is generic dx* + tokens with nothing MyShop-specific in it.
   So it is now copied byte-identically into all nine web roots like the rest
   of the shared set, rather than being a third one-project exception.

   It coexists with ERP.UI's theme-erp-adapter.css by design: that file styles
   ERP.UI's OWN vocabulary (cityTextbox, gridHeader, gridcellleft), which this
   file never touches, and its dark dx rules carry no !important, so where the
   two overlap this one wins and the result is consistent with the portal.

   ---------------------------------------------------------------------------
   THE RULE THAT KEEPS THIS SAFE - COLOUR ONLY
   ---------------------------------------------------------------------------
   DevExpress computes grid layout in JavaScript at render time: column widths,
   frozen columns and the scroll frame are MEASURED, not declared. Overriding
   padding, border-width, height or box-sizing on a .dxgv* element desyncs the
   header row from the data rows, and the breakage only shows up on real data
   with horizontal scroll - i.e. not in a quick local check.

   So: background, color, border-COLOR, box-shadow and border-radius only.
   Never border-width, never padding, never height, never display.

   ---------------------------------------------------------------------------
   WHY [class*="..."] AND NOT THE BARE CLASS
   ---------------------------------------------------------------------------
   DevExpress emits skin-suffixed class names - dxgvHeader_Default,
   dxgvHeader_Office2010Blue, and so on - and which suffix appears depends on
   the skin configured per control. The markup in this project contains both
   bare and suffixed forms. A substring match catches every variant, so this
   adapter does not silently miss a control that happens to use another skin.

   ASCII-only. Chrome 59 floor.
   ============================================================================ */

/* ---------------------------------------------------------------------------
   1. GRID FRAME
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxgvControl"],
[data-bz-theme="dark"] [class*="dxgvControl"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
    border-radius: var(--bz-r) !important;
    box-shadow: var(--bz-shadow-sm) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvTable"],
[data-bz-theme="dark"] [class*="dxgvTable"] {
    background-color: transparent !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* ---------------------------------------------------------------------------
   2. HEADER ROW
   The tinted, quiet header of the brief: muted ink on a faint surface, with
   the emphasis carried by the data rather than by the header.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxgvHeader"],
[data-bz-theme="dark"] [class*="dxgvHeader"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-muted) !important;
    border-color: var(--bz-border) !important;
    font-weight: 600 !important;
}

/* ---------------------------------------------------------------------------
   3. DATA ROWS
   Resting, alternating, hover, focused and selected are five DIFFERENT states
   and they are kept visually distinct on purpose. Collapsing hover and
   selected into one fill - the tempting shortcut - removes the feedback that
   tells a user which row a click is about to act on.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxgvDataRow"] td,
[data-bz-theme="dark"] [class*="dxgvDataRow"] td {
    background-color: var(--bz-surface) !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvDataRowAlt"] td,
[data-bz-theme="dark"] [class*="dxgvDataRowAlt"] td {
    background-color: var(--bz-surface-2) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvDataRow"]:hover td,
[data-bz-theme="dark"] [class*="dxgvDataRow"]:hover td {
    background-color: var(--bz-bg-2) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvFocusedRow"] td,
[data-bz-theme="dark"] [class*="dxgvFocusedRow"] td {
    background-color: var(--bz-bg-2) !important;
    color: var(--bz-text) !important;
}

/* Selected is the one state allowed to use brand fill.
   [2026-09-11] --bz-primary-fill, not --bz-primary: in Dark the latter is the
   lightened TEXT blue (#60A5FA) and the white label on it measured 2.54:1 -
   a selected row was the least readable row in the grid. The fill/ink pair
   is 5.17:1 in both appearances. */
[data-bz-theme="nextgen"] [class*="dxgvSelectedRow"] td,
[data-bz-theme="dark"] [class*="dxgvSelectedRow"] td {
    background-color: var(--bz-primary-fill) !important;
    background-image: none !important;
    color: var(--bz-on-primary) !important;
    border-color: var(--bz-primary-fill) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvSelectedRow"] td a,
[data-bz-theme="dark"] [class*="dxgvSelectedRow"] td a {
    color: var(--bz-on-primary) !important;
}

/* Footer / pager / group rows. */
[data-bz-theme="nextgen"] [class*="dxgvFooter"],
[data-bz-theme="dark"] [class*="dxgvFooter"],
[data-bz-theme="nextgen"] [class*="dxgvPagerBottomPanel"],
[data-bz-theme="dark"] [class*="dxgvPagerBottomPanel"],
[data-bz-theme="nextgen"] [class*="dxgvGroupRow"],
[data-bz-theme="dark"] [class*="dxgvGroupRow"],
[data-bz-theme="nextgen"] [class*="dxgvPanel"],
[data-bz-theme="dark"] [class*="dxgvPanel"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* Empty-data and loading panel. A loading panel that stays white on a dark
   page is a bright flash on every postback. */
[data-bz-theme="nextgen"] [class*="dxgvLoadingPanel"],
[data-bz-theme="dark"] [class*="dxgvLoadingPanel"],
[data-bz-theme="nextgen"] [class*="dxgvEmptyDataRow"],
[data-bz-theme="dark"] [class*="dxgvEmptyDataRow"] {
    background-color: var(--bz-surface) !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* ---------------------------------------------------------------------------
   4. EDITORS
   dxeEditArea is the input inside a DevExpress editor; dxeButtonEdit is the
   combo/date wrapper around it. Both are measured, so colour only.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxeEditArea"],
[data-bz-theme="dark"] [class*="dxeEditArea"],
[data-bz-theme="nextgen"] [class*="dxeMemoEditArea"],
[data-bz-theme="dark"] [class*="dxeMemoEditArea"],
[data-bz-theme="nextgen"] [class*="dxeButtonEdit"],
[data-bz-theme="dark"] [class*="dxeButtonEdit"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border-2) !important;
}

[data-bz-theme="nextgen"] [class*="dxeEditArea"]::-webkit-input-placeholder,
[data-bz-theme="dark"] [class*="dxeEditArea"]::-webkit-input-placeholder {
    color: var(--bz-muted) !important;
}

/* The little drop-down button inside an editor. */
[data-bz-theme="nextgen"] [class*="dxeButtonEditButton"],
[data-bz-theme="dark"] [class*="dxeButtonEditButton"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* ---------------------------------------------------------------------------
   5. BUTTONS
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxbButton"],
[data-bz-theme="dark"] [class*="dxbButton"],
[data-bz-theme="nextgen"] [class*="dxeButton"]:not([class*="dxeButtonEdit"]),
[data-bz-theme="dark"] [class*="dxeButton"]:not([class*="dxeButtonEdit"]) {
    background-image: var(--bz-btn-grad) !important;
    background-color: transparent !important;
    color: #FFFFFF !important;
    border-color: transparent !important;
    border-radius: var(--bz-r-sm) !important;
    box-shadow: var(--bz-shadow-brand) !important;
}

[data-bz-theme="nextgen"] [class*="dxbButton"]:hover,
[data-bz-theme="dark"] [class*="dxbButton"]:hover {
    background-image: var(--bz-btn-grad-hover) !important;
}

/* Disabled must NOT keep the brand gradient - otherwise a dead button still
   advertises itself as the primary action. */
[data-bz-theme="nextgen"] [class*="dxeButtonDisabled"],
[data-bz-theme="dark"] [class*="dxeButtonDisabled"],
[data-bz-theme="nextgen"] [class*="dxgvDisabled"],
[data-bz-theme="dark"] [class*="dxgvDisabled"] {
    background-image: none !important;
    background-color: var(--bz-surface-2) !important;
    color: var(--bz-muted) !important;
    box-shadow: none !important;
}

/* ---------------------------------------------------------------------------
   6. POPUPS, CALENDARS, TABS
   These float above the page, so they need an opaque surface or the page
   ground shows through and the text sits on a gradient.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxpcLite"],
[data-bz-theme="dark"] [class*="dxpcLite"],
[data-bz-theme="nextgen"] [class*="dxpc-content"],
[data-bz-theme="dark"] [class*="dxpc-content"],
[data-bz-theme="nextgen"] [class*="dxpcHeader"],
[data-bz-theme="dark"] [class*="dxpcHeader"],
[data-bz-theme="nextgen"] [class*="dxdpLite"],
[data-bz-theme="dark"] [class*="dxdpLite"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxeCalendar"],
[data-bz-theme="dark"] [class*="dxeCalendar"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxeCalendarHeader"],
[data-bz-theme="dark"] [class*="dxeCalendarHeader"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-heading) !important;
}

[data-bz-theme="nextgen"] [class*="dxeCalendarSelected"],
[data-bz-theme="dark"] [class*="dxeCalendarSelected"] {
    background-color: var(--bz-primary-fill) !important;
    background-image: none !important;
    color: var(--bz-on-primary) !important;
}

[data-bz-theme="nextgen"] [class*="dxtcLite"],
[data-bz-theme="dark"] [class*="dxtcLite"],
[data-bz-theme="nextgen"] [class*="dxtc-tab"],
[data-bz-theme="dark"] [class*="dxtc-tab"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxtc-activeTab"],
[data-bz-theme="dark"] [class*="dxtc-activeTab"] {
    background-image: var(--bz-btn-grad) !important;
    color: #FFFFFF !important;
    border-color: transparent !important;
}

/* The rest of the tab control, which had no rule at all. dxtc-strip,
   dxtc-link and dxtc-content are the real structural classes (16, 15 and 10
   references), so the strip behind the tabs and the panel under them both
   kept the skin ground. */
[data-bz-theme="nextgen"] [class*="dxtc-stripContainer"],
[data-bz-theme="dark"] [class*="dxtc-stripContainer"],
[data-bz-theme="nextgen"] [class*="dxtc-strip"],
[data-bz-theme="dark"] [class*="dxtc-strip"] {
    background-color: transparent !important;
    background-image: none !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxtc-content"],
[data-bz-theme="dark"] [class*="dxtc-content"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* The anchor inside a tab must not take the page link colour. */
[data-bz-theme="nextgen"] [class*="dxtc-link"],
[data-bz-theme="dark"] [class*="dxtc-link"] {
    color: inherit !important;
    background: transparent !important;
}

/* ===========================================================================
   7. CHROME THE FIRST PASS MISSED   [2026-09-11]
   ---------------------------------------------------------------------------
   HOW THIS LIST WAS BUILT - and why the earlier one was incomplete.

   Sections 1-6 were written from the DevExpress class names that appear in
   THIS REPOSITORY's own stylesheets. That is a biased sample: it contains only
   the classes somebody once needed to override. Everything DevExpress renders
   that nobody ever had to restyle in the light theme - the group panel, the
   filter row, the edit form, the search panel - was invisible to that method,
   and stayed light on a dark page. The reported case was
   "Drag a column header here to group by that column" rendering as a white
   band: dxgvGroupPanel, which no file here mentions.

   There are NO DevExpress stylesheets in this repository - the skin is served
   at runtime from DevExpress.Web.v15.1 through WebResource.axd - so for a long
   time this looked unscannable. It is not: that assembly IS committed (see
   CLAUDE.md on vendor binaries), and its class vocabulary can be read straight
   out of it:

       python -c "import re;b=open('ERP.UI/bin/DevExpress.Web.v15.1.dll','rb').read();
       print(sorted(set(re.findall(r'\bdxgv[A-Za-z]+\b', b.decode('latin-1')))))"

   635 class names, against 32 covered. This section closes the gap for the
   CHROME families - the ones that paint a surface. Deliberately NOT blanket-
   theming all 635: most are layout helpers (dxeCaptionHALSys, dxeContentLeftSys
   and friends are alignment, not colour), and blanket-theming a vendor
   vocabulary is exactly how the scrollbar and pager regressions happened.

   Substring selectors, because DevExpress appends the skin name at runtime -
   the group panel renders as dxgvGroupPanel_PlasticBlue. Colour only; no
   geometry, so no grid measurement shifts.
   =========================================================================== */

/* ---- panels, bars and captions: the frame around the data --------------- */
[data-bz-theme="dark"] [class*="dxgvGroupPanel"],
[data-bz-theme="dark"] [class*="dxgvTitlePanel"],
[data-bz-theme="dark"] [class*="dxgvStatusBar"],
[data-bz-theme="dark"] [class*="dxgvPagerTopPanel"],
[data-bz-theme="dark"] [class*="dxgvSearchPanel"],
[data-bz-theme="dark"] [class*="dxgvFilterBar"],
[data-bz-theme="dark"] [class*="dxeCaption"],
[data-bz-theme="dark"] [class*="dxflCaption"],
[data-bz-theme="dark"] [class*="dxflGroupBoxCaption"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-muted) !important;
    border-color: var(--bz-border) !important;
}

/* ---- the filter row -----------------------------------------------------
   Its editors were already themed in section 4, so an unthemed row left dark
   inputs sitting on a white strip - the "black boxes" in the same report. */
[data-bz-theme="dark"] [class*="dxgvFilterRow"],
[data-bz-theme="dark"] [class*="dxgvFilterRow"] td {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* ---- the inline / popup edit form -------------------------------------- */
[data-bz-theme="dark"] [class*="dxgvEditForm"],
[data-bz-theme="dark"] [class*="dxgvEditFormTable"],
[data-bz-theme="dark"] [class*="dxgvEditFormDisplayRow"],
[data-bz-theme="dark"] [class*="dxgvEditFormCell"],
[data-bz-theme="dark"] [class*="dxgvPopupEditForm"],
[data-bz-theme="dark"] [class*="dxtcPageContent"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* ---- the command column: buttons on the row, not a surface of its own --- */
[data-bz-theme="dark"] [class*="dxgvCommandColumn"],
[data-bz-theme="dark"] [class*="dxgvCommandColumnItem"] {
    background-color: transparent !important;
    background-image: none !important;
    color: var(--bz-primary) !important;
}

/* ---- floating layers: a drop-down needs to sit ABOVE the page ----------- */
[data-bz-theme="dark"] [class*="dxeDropDownWindow"],
[data-bz-theme="dark"] [class*="dxpcDropDown"],
[data-bz-theme="dark"] [class*="dxlpLoadingPanelWithContent"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border: 1px solid var(--bz-border-2) !important;
    box-shadow: var(--bz-shadow-lg) !important;
}

/* ---- footer cells whose ink is set from JAVASCRIPT ----------------------
   Several report pages tint individual footer totals at runtime:

       $("#gridsummarydashboard_DXFooterRow td:eq(2)").css({ color: '#2443AA' })

   That writes an INLINE style, which outranks every rule above - the row went
   dark and the totals stayed navy on navy at 1.99:1. An attribute selector
   cannot catch it either, because jQuery hands the value to the DOM and the
   browser serialises it back as `rgb(36, 67, 170)`, so `[style*="#2443AA"]`
   never matches. Only !important on the cell itself beats an inline style.

   The rule above sets the ROW's colour; a cell with its own inline ink does
   not inherit it. Stated at cell level so it does.

   Found by Tools/theme-dark-audit-js.py, which reads colours applied from
   JavaScript - the tier no CSS audit can see. */
[data-bz-theme="dark"] [class*="dxgvFooter"] td,
[data-bz-theme="dark"] [class*="dxgvFooter"] td b,
[data-bz-theme="dark"] [class*="dxgvFooter"] td span {
    color: var(--bz-text) !important;
}

/* ===========================================================================
   8. SPECIFICITY - BEATING THE APPLICATION'S OWN !important RULES  [2026-09-12]
   ---------------------------------------------------------------------------
   REPORTED: the Employees grid header rendered bright blue in Dark.

   Sections 1-7 select DevExpress by attribute substring - `[class*="dxgvHeader"]`
   - which is (0,2,0). That is deliberate: the skin name is appended at runtime,
   so the full class is not knowable. It is also LOW, and this application has
   its own rules on the same elements:

       ftsNewScreen.css
       table.dxgvTable_PlasticBlue > tbody > tr:nth-child(2) > td.dxgvHeader_PlasticBlue
       { background: #094e8c !important }                         -> (0,3,4)

   Both sides carry !important, so !important cancels out and SPECIFICITY
   decides - (0,3,4) beats (0,2,0), and the header stayed the light theme's
   solid blue on a dark grid.

   Measured rather than guessed: exactly three app rules on DevExpress classes
   outrank the adapter. They are restated here at a specificity that wins,
   using the same structural shape so the match is exact:

       [data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr
           > td[class*="dxgvHeader"][class]                       -> (0,4,4)

   The trailing [class] adds one attribute and nothing else - a deliberate,
   readable specificity bump rather than a deeper guess at the DOM.
   =========================================================================== */
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr > td[class*="dxgvHeader"][class],
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr > th[class*="dxgvHeader"][class] {
    background: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* The editor base inside a label table - main.css reaches it at (0,3,3). */
[data-bz-theme="dark"] .lblHolder table tr td [class*="dxeBase"][class],
[data-bz-theme="dark"] .lblHolder table tr td [class*="dxeEditArea"][class] {
    background-color: var(--bz-surface) !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border-2) !important;
}

/* ---------------------------------------------------------------------------
   9. THE FILTER ROW AND ITS FIELDS MUST NOT BE THE SAME COLOUR
   ---------------------------------------------------------------------------
   Section 7 gave `dxgvFilterRow` --bz-surface. Section 4 already gave the
   editors --bz-surface. Identical values, so the input boxes disappeared into
   the row they sit in and only their borders showed - the "black boxes" in the
   report. That was introduced by section 7, not inherited.

   A field is RECESSED relative to the bar that holds it. The row moves up to
   the raised surface and the editors stay on the resting one, which restores
   the one-step difference the elevation model is built on.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] [class*="dxgvFilterRow"],
[data-bz-theme="dark"] [class*="dxgvFilterRow"] td {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
}

/* dxic is the DevExpress input CELL - 31 references in this repo and no
   coverage until now. Left light it framed every editor in white. */
[data-bz-theme="dark"] [class*="dxgvFilterRow"] td[class*="dxic"],
[data-bz-theme="dark"] td[class*="dxic"],
[data-bz-theme="dark"] [class*="dxeTextBoxSys"] td[class*="dxic"] {
    background-color: transparent !important;
    background-image: none !important;
}

/* [2026-09-12] The filter-row fields were reading as heavy outlines against
   the dark row. --bz-border-2 (#33445F) is the FOCUS/emphasis hairline; at
   rest a field in a dense grid wants the quieter --bz-border (#24324A), which
   is the same relationship Standard has - a faint grey box, not an outlined
   one. */
[data-bz-theme="dark"] [class*="dxgvFilterRow"] [class*="dxeEditArea"],
[data-bz-theme="dark"] [class*="dxgvFilterRow"] input,
[data-bz-theme="dark"] [class*="dxgvFilterRow"] [class*="dxeButtonEdit"] {
    border-color: var(--bz-border) !important;
}

/* ===========================================================================
   10. THE EDITOR WRAPPER, AND THE REST OF THE DX VOCABULARY   [2026-09-12]
   ---------------------------------------------------------------------------
   Reported on /OMS/Management/Master/Employee.aspx: "white highlighted search
   in grid ... rest column are buggy white color".

   Found by inventory, not by reading the screenshot. Every dx* class token in
   the repo's markup was counted and diffed against the substrings this file
   actually selects on (Tools scan, 2026-09-12). The top uncovered entry:

       dxeTextBox                 79 references        UNCOVERED
       dxgvBatchEditModifiedCell  24                   UNCOVERED
       dxeErrorFrameSys/CellSys   20                   UNCOVERED
       dxgvHSDC / dxgvCSD         22                   UNCOVERED

   `dxeTextBoxSys` looked covered because section 9 names it - but only as
   `[class*="dxeTextBoxSys"] td[class*="dxic"]`, which paints the input CELL.
   The element carrying the skin's `background-color:White; border:1px solid`
   is the WRAPPER TABLE around that cell, and nothing had ever selected it.

   That is why section 4 was not enough. An ASPxTextBox is three elements:

       table.dxeTextBox_PlasticBlue   <- the visible field   (was WHITE)
         td.dxic                      <- the input cell      (section 9)
           input.dxeEditArea          <- the text            (section 4)

   The wrapper is the field. It takes --bz-surface so it meets the inner
   dxeEditArea with no seam, and one --bz-border hairline - the same resting
   edge section 9 settled on for the filter row. ASPxButtonEdit already worked
   because `[class*="dxeButtonEdit"]` happens to match its wrapper too; the
   plain text box has no such luck.

   Everything below it in this section is the remainder of that inventory,
   fixed in one pass rather than one screenshot at a time.
   ========================================================================== */

/* --- the editor wrapper ------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxeTextBox"],
[data-bz-theme="dark"] [class*="dxeTextBox"],
[data-bz-theme="nextgen"] [class*="dxeMemo"]:not([class*="dxeMemoEditArea"]),
[data-bz-theme="dark"] [class*="dxeMemo"]:not([class*="dxeMemoEditArea"]),
[data-bz-theme="nextgen"] [class*="dxeListBox"]:not([class*="Item"]),
[data-bz-theme="dark"] [class*="dxeListBox"]:not([class*="Item"]) {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* The cells INSIDE that wrapper must not re-declare a ground of their own,
   or the seam comes back one level down. */
[data-bz-theme="dark"] [class*="dxeTextBox"] > tbody > tr > td,
[data-bz-theme="dark"] [class*="dxeMemo"]:not([class*="dxeMemoEditArea"]) > tbody > tr > td,
[data-bz-theme="dark"] [class*="dxeControlsCell"],
[data-bz-theme="dark"] [class*="dxeNoBorder"] {
    background-color: transparent !important;
    background-image: none !important;
}

/* --- list-box selection ------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxeListBoxItemSelected"],
[data-bz-theme="dark"] [class*="dxeListBoxItemSelected"] {
    background-color: rgba(96, 165, 250, .20) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
}

/* --- validation --------------------------------------------------------- */
/* The skin plates an error in pale yellow, which on a dark page is a lamp.
   A dark UI signals an error by INK and a low-alpha wash, not by a slab. */
[data-bz-theme="dark"] [class*="dxeErrorFrame"],
[data-bz-theme="dark"] [class*="dxeErrorCell"] {
    background-color: rgba(248, 113, 113, .12) !important;
    background-image: none !important;
    border-color: rgba(248, 113, 113, .45) !important;
    color: var(--bz-danger) !important;
}

[data-bz-theme="dark"] [class*="dxeOutOfRWarn"] {
    background-color: rgba(251, 191, 36, .14) !important;
    background-image: none !important;
    color: var(--bz-warning) !important;
}

[data-bz-theme="dark"] [class*="dxeValidStEditorTable"],
[data-bz-theme="dark"] [class*="dxflHARSys"],
[data-bz-theme="dark"] [class*="dxflHALSys"],
[data-bz-theme="dark"] [class*="dxflVATSys"] {
    background-color: transparent !important;
    background-image: none !important;
}

[data-bz-theme="dark"] [class*="dxflRequired"] {
    color: var(--bz-danger) !important;
}

/* --- grid: modified cell, separators, customization --------------------- */
[data-bz-theme="dark"] [class*="dxgvBatchEditModifiedCell"] {
    background-color: rgba(251, 191, 36, .16) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
}

/* HSDC = Header Separator Div Container, CSD = Column Separator Div. These
   are hairlines, so they are a BORDER colour, never a fill. */
[data-bz-theme="dark"] [class*="dxgvHSDC"],
[data-bz-theme="dark"] [class*="dxgvCSD"],
[data-bz-theme="dark"] [class*="dxtlHSDC"] {
    border-color: var(--bz-border) !important;
    background-color: transparent !important;
}

[data-bz-theme="dark"] [class*="dxgvCustomization"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* --- tree list (same widget family as the grid) ------------------------- */
[data-bz-theme="dark"] [class*="dxtlControl"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="dark"] [class*="dxtlHeader"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-heading) !important;
    border-color: var(--bz-border) !important;
}

/* --- standalone pager --------------------------------------------------- */
[data-bz-theme="dark"] [class*="dxpLite"],
[data-bz-theme="dark"] [class*="dxpLite"] td {
    background-color: transparent !important;
    background-image: none !important;
    color: var(--bz-text) !important;
}

/* --- disabled ----------------------------------------------------------- */
[data-bz-theme="dark"] [class*="dxeDisabled"],
[data-bz-theme="dark"] [class*="dxeDisabled"] input {
    background-color: var(--bz-bg-2) !important;
    background-image: none !important;
    color: var(--bz-muted) !important;
}

/* --- radio / check lists sit ON their panel, they are not panels -------- */
[data-bz-theme="dark"] [class*="dxeRadioButtonList"],
[data-bz-theme="dark"] [class*="dxeCheckBoxList"],
[data-bz-theme="dark"] [class*="dxeRadioButtonList"] td,
[data-bz-theme="dark"] [class*="dxeCheckBoxList"] td,
[data-bz-theme="dark"] [class*="dxeIRadioButton"] {
    background-color: transparent !important;
    background-image: none !important;
    color: var(--bz-text) !important;
}

/* ===========================================================================
   11. THE ONE GRID BORDER THE GENERATOR CANNOT REACH   [2026-09-12]
   ---------------------------------------------------------------------------
   Reported on the Countries master: white lines ruling the grid.

   Almost all of them were the generator's to fix once borders became a
   measured property - .dxgvControl_PlasticBlue (#e9e9e9) and td.dxgv
   (#e7e7e7) are both covered by theme-dark-surfaces.css now.

   This one is not, and the reason is arithmetic. ftsNewScreen.css line 1356:

       table.dxgvTable_PlasticBlue > tbody > tr:nth-child(2)
           > td.dxgvHeader_PlasticBlue {
           border-right: 1px solid #999999 !important;
       }

   Four elements and three classes/pseudo-classes - (0,3,4) - carrying
   !important. Every generated rule is `[data-bz-theme="dark"] .selector`,
   which is at most (0,2,0). !important on both sides cancels, so specificity
   decides and the generated rule loses. No amount of regenerating fixes it.

   Matched here by restating the application's own selector with the theme
   attribute in front, which is (0,4,4) - one step above, and no more. The
   column separator is a hairline between headers, so it takes --bz-border,
   the same edge every other line in this grid now uses.
   =========================================================================== */
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody
    > tr:nth-child(2) > td[class*="dxgvHeader"] {
    border-right-color: var(--bz-border) !important;
}

/* Same family, same problem: the app gives the grid frame a light box at
   (0,1,0) with no !important, which the generator does beat - but PopUp and
   Vendor masters load ftsNewScreen AFTER the theme in a couple of places, so
   the frame is restated here at a specificity nothing in the app reaches. */
[data-bz-theme="dark"] table[class*="dxgvTable"],
[data-bz-theme="dark"] div[class*="dxgvControl"] {
    border-color: var(--bz-border) !important;
}

/* ===========================================================================
   12. ONE FIELD, ONE EDGE - AND A GUTTER FOR THE FIRST COLUMN   [2026-09-12]
   ---------------------------------------------------------------------------
   12.1 THE BOX INSIDE THE BOX  (a regression from section 10, same day)

   Section 10 gave the editor WRAPPER a visible border, because the wrapper is
   what the DevExpress skin paints white and nothing had ever selected it. Its
   own comment said the wrapper should become "the single visible field" - but
   the rule only made the wrapper's CELLS transparent. It never took the
   border off the input inside.

   So both elements drew one, and every search box and filter field in the
   product rendered as a rectangle inside a rectangle:

       table.dxeTextBox_PlasticBlue     <- section 10 gave this an edge
         td.dxic                        <- section 9, transparent
           input.dxeEditArea            <- the SKIN still gives this an edge

   Reported on the Countries master as "search inside border not needed", and
   that is exactly right. A text field has one edge. The wrapper keeps it
   because it is the element with the correct box; the input gives its up.

   Stated as `border: 0` rather than a colour, because a colour on a border
   that is still 1px wide only changes which line you see, not how many.
   =========================================================================== */
   EVERY SELECTOR HERE REQUIRES A WRAPPER ANCESTOR, ON PURPOSE
   ---------------------------------------------------------------------------
   The tempting shorthand is `[class*="dxgvFilterRow"] input` - it reads well
   and it is wrong. A bare input with no DevExpress wrapper around it would be
   stripped of BOTH its border and its background and then sit directly on the
   filter row, which is --bz-surface-2: an invisible field, which is a worse
   bug than the double edge this is fixing.

   So the border is only ever taken away from an input that demonstrably has
   something else drawing the field for it. Every selector below names the
   wrapper first. The search panel and the filter row both render ASPxTextBox,
   so `[class*="dxeTextBox"] input` already reaches them - naming them again
   would only widen the blast radius.
   =========================================================================== */
[data-bz-theme="dark"] [class*="dxeTextBox"] [class*="dxeEditArea"],
[data-bz-theme="dark"] [class*="dxeTextBox"] input,
[data-bz-theme="dark"] [class*="dxeMemo"] textarea,
[data-bz-theme="dark"] [class*="dxeButtonEdit"] [class*="dxeEditArea"],
[data-bz-theme="dark"] [class*="dxeButtonEdit"] input {
    border: 0 !important;
    box-shadow: none !important;
    background-color: transparent !important;
    background-image: none !important;
}

/* The wrapper now carries the whole appearance of the field, so it gets the
   rounding too - otherwise a square outer box holds a field that used to look
   rounded. */
[data-bz-theme="dark"] [class*="dxeTextBox"],
[data-bz-theme="dark"] [class*="dxeButtonEdit"] {
    border-radius: var(--bz-r-sm) !important;
}

/* ---------------------------------------------------------------------------
   12.2 SUPERSEDED - see section 13.
   --------------------------------------------------------------------------- */

/* ===========================================================================
   13. GRID GEOMETRY: ADDRESS THE CELL, NOT THE ROW   [2026-09-12]
   ---------------------------------------------------------------------------
   13.1 WHY THE FIRST ROW WAS THE ONLY ONE WITHOUT PADDING

   Reported exactly: "1st list record not padded". 12.2 raised the first
   column's left padding and reached four row types out of five.

   ftsNewScreen.css line 1367 declares that padding for FIVE row classes:

       .dxgvEditFormDisplayRow_PlasticBlue td.dxgv,
       .dxgvDataRow_PlasticBlue          td.dxgv,
       .dxgvDataRowAlt_PlasticBlue       td.dxgv,
       .dxgvSelectedRow_PlasticBlue      td.dxgv,
       .dxgvFocusedRow_PlasticBlue       td.dxgv   { padding: 8px 6px 8px }

   12.2 was written as `[class*="dxgvDataRow"]`, which matches exactly two of
   them. `dxgvFocusedRow` does not contain the substring "dxgvDataRow", and
   DevExpress focuses the first row on load - so the first record of every
   grid in the product kept the old 6px while every row under it moved to 14px.

   I read the VALUE out of that rule and never read its SELECTOR. The list of
   every row type was on the same line as the number I copied.

   The fix is not to add the two missing names. It is to stop addressing the
   ROW: `dxgv` is the class DevExpress puts on the data CELL and it is present
   whatever state the row is in. One selector, five row types, and no vendor
   list to keep in step with.

   ---------------------------------------------------------------------------
   13.2 THE LINES ARE REMOVED BY COLOUR, NOT BY WIDTH - THIS IS NOT A DETAIL

   Also reported: "extra border white line many places / unnecessary line".
   They are not white - they are --bz-border - but there are two per cell edge
   and the vertical ones carry no information. Modern data tables rule rows and
   not columns, because the gap between values already delimits the column.

   The obvious way to remove them is `border-right: 0`. This file's own header
   forbids exactly that, and the reason is not stylistic:

       "DevExpress computes grid layout in JavaScript at render time: column
        widths, frozen columns and the scroll frame are MEASURED, not declared.
        Overriding padding, border-width, height or box-sizing on a .dxgv*
        element desyncs the header row from the data rows... Never
        border-width, never padding."

   Measured against this repo, that warning has teeth:

       FixedStyle="Left"            54 columns   (frozen - two tables, JS-aligned)
       HorizontalScrollBarMode      19 grids     (separate header + data tables)
       ASPxGridView views           82

   So the vertical rules are made TRANSPARENT instead of zero-width. The 1px
   box is untouched, nothing DevExpress measured changes, and the line is
   gone. A colour change is what the file's rule explicitly permits.

   ---------------------------------------------------------------------------
   13.3 PADDING IS A DELIBERATE, NARROW EXCEPTION TO THAT RULE

   Padding cannot be faked with a colour. It is applied here anyway, because
   the cramped first column was reported twice and 6px is genuinely too tight
   at this width - but it is an EXCEPTION and it is recorded as one:

     * It is applied identically to the header, the filter row and the data
       cells, so the three tables of a scrolling grid keep the same box.
     * DevExpress writes explicit column widths on scrollable and frozen
       grids, so padding reduces the content area rather than the column - the
       failure mode is early text wrapping, not a misaligned header.
     * It is themed-appearance only. Standard renders exactly as it does today,
       so any grid that does misbehave has a working comparison one click away.

   IF A GRID EVER LOOKS MISALIGNED IN DARK AND CORRECT IN STANDARD, THIS BLOCK
   IS THE FIRST THING TO REVERT - start with the 54 FixedStyle="Left" columns.
   =========================================================================== */
[data-bz-theme="nextgen"] table[class*="dxgvTable"] > tbody > tr > td[class*="dxgv"],
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr > td[class*="dxgv"] {
    /* VERTICAL padding is left at the app's own 8px on purpose. Row height is
       the one measurement DevExpress uses for virtual scrolling, so changing
       it has a second failure mode beyond header alignment. Only the
       horizontal gutter - the thing actually reported - moves. */
    padding: 8px 14px !important;
    /* colour only - the border box keeps its 1px on every side */
    border-left-color: transparent !important;
    border-right-color: transparent !important;
    border-top-color: transparent !important;
    border-bottom-color: var(--bz-border) !important;
}

/* The Actions column is declared Width="6%" with HorizontalAlign="Center", so
   it is the one cell where padding costs width that is not there to give and
   pushes a centred pair off-centre. Section 17 of theme-dark-polish.css had to
   be rewritten once for exactly this column. */
[data-bz-theme="nextgen"] table[class*="dxgvTable"] > tbody > tr > td[class*="dxgv"]:last-child,
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr > td[class*="dxgv"]:last-child {
    padding-left: 4px !important;
    padding-right: 4px !important;
}

/* The header sits on the same vertical line as the data under it. This also
   restates the one border the generator can never reach: ftsNewScreen.css
   line 1356 puts `border-right: 1px solid #999999 !important` on the header
   cell at (0,3,4), and naming the same shape with the theme attribute in
   front is (0,4,4) - one step above, and no more. */
[data-bz-theme="nextgen"] table[class*="dxgvTable"] > tbody > tr:nth-child(2) > td[class*="dxgvHeader"],
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr:nth-child(2) > td[class*="dxgvHeader"] {
    border-right-color: transparent !important;
    border-left-color: transparent !important;
    padding: 8px 14px !important;
}

/* The filter row's FIELDS keep their own edge (section 12.1). This is only the
   cell that holds them lining up with its column. */
[data-bz-theme="nextgen"] [class*="dxgvFilterRow"] > td,
[data-bz-theme="dark"] [class*="dxgvFilterRow"] > td {
    padding: 6px 14px !important;
    border-left-color: transparent !important;
    border-right-color: transparent !important;
}

/* The last row should not rule a line into the panel's own bottom edge. */
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr:last-child > td[class*="dxgv"] {
    border-bottom-color: transparent !important;
}

/* ===========================================================================
   14. THE COMBO DROP-DOWN LIST  [2026-09-13]
   ---------------------------------------------------------------------------
   Reported: the Class Name drop-down on the Add Products dialog is still a
   white panel in dark.

   Two separate reasons, and the first is a selector that never matched
   anything.

   1. DEVEXPRESS 15.1 EMITS HYPHENATED POPUP CLASSES.
      Section 8 above styles [class*="dxpcContent"] and [class*="dxpcHeader"].
      Grepping the whole product for those spellings returns exactly one hit -
      this file. What the control actually renders is:

          dxpc-content        84 references      dxpc-mainDiv        16
          dxpc-header         41                 dxpc-headerContent  10
          dxpc-contentWrapper 17                 dxpc-shadow          3

      `dxpcLite` does match, so the OUTER popup went dark; `dxpc-mainDiv` and
      `dxpc-content` sit inside it, kept the skin's white, and covered it.

   2. THE LIST ITEMS WERE NEVER THEMED.
      Only `dxeListBoxItemSelected` had a rule. The unselected cells - the
      whole list, in other words - kept the skin's white ground.

   A popup is appended to <body>, outside every page container, so it can only
   be reached by rules anchored on the theme attribute on <html>. That is why
   these are written flat rather than scoped to a panel.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxpc-mainDiv"],
[data-bz-theme="dark"] [class*="dxpc-mainDiv"],
[data-bz-theme="nextgen"] [class*="dxpc-contentWrapper"],
[data-bz-theme="dark"] [class*="dxpc-contentWrapper"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxpc-header"],
[data-bz-theme="dark"] [class*="dxpc-header"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-heading) !important;
    border-color: var(--bz-border) !important;
}

/* The list itself: table, rows and cells all carry their own skin ground. */
[data-bz-theme="nextgen"] [class*="dxeListBoxTable"],
[data-bz-theme="dark"] [class*="dxeListBoxTable"],
[data-bz-theme="nextgen"] [class*="dxeListBoxItemRow"],
[data-bz-theme="dark"] [class*="dxeListBoxItemRow"],
[data-bz-theme="nextgen"] [class*="dxlbd"],
[data-bz-theme="dark"] [class*="dxlbd"] {
    background-color: transparent !important;
    background-image: none !important;
    border-color: var(--bz-border) !important;
}

/* Unselected items - the entire list. `Selected` keeps the brand wash set
   further up, so it is excluded here rather than restated. */
[data-bz-theme="nextgen"] [class*="dxeListBoxItem"]:not([class*="Selected"]),
[data-bz-theme="dark"] [class*="dxeListBoxItem"]:not([class*="Selected"]) {
    background-color: transparent !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: transparent !important;
}

/* Hover needs to read as a pointer target without competing with Selected. */
[data-bz-theme="nextgen"] [class*="dxeListBoxItem"]:not([class*="Selected"]):hover,
[data-bz-theme="dark"] [class*="dxeListBoxItem"]:not([class*="Selected"]):hover {
    background-color: var(--bz-surface-2) !important;
    color: var(--bz-text) !important;
}

/* ===========================================================================
   15. A SELECTED ROW vs A LIST WHERE EVERYTHING IS SELECTED  [2026-09-13]
   ---------------------------------------------------------------------------
   Section 4 paints a selected grid row in a SOLID brand fill, and that is
   right: in a normal grid one row is selected, and a 5.17:1 fill/ink pair is
   what makes it the most readable row rather than the least.

   An ASPxGridLookup drop-down breaks the assumption. It is a MULTI-select with
   a checkbox per row, so the ordinary state is that most or all rows are
   selected - and 29 branches all painted #2563EB is not a highlight, it is a
   solid blue slab where the checkbox, not the fill, is what actually carries
   the state.

   Inside a drop-down the fill therefore steps back to a wash and the ink
   returns to normal text. The checkbox still says what is selected, and the
   row separators stay visible, which they were not against a solid fill.

   Scoped by the popup ancestor, so a grid ON the page is untouched: DevExpress
   renders a GridLookup list inside a dxpc popup and a page grid never is.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxpc"] [class*="dxgvSelectedRow"] td,
[data-bz-theme="dark"] [class*="dxpc"] [class*="dxgvSelectedRow"] td {
    background-color: rgba(96, 165, 250, .16) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: transparent !important;
    border-bottom-color: var(--bz-border) !important;
}

/* The focused row inside a drop-down must not compete with the wash either. */
[data-bz-theme="nextgen"] [class*="dxpc"] [class*="dxgvFocusedRow"] td,
[data-bz-theme="dark"] [class*="dxpc"] [class*="dxgvFocusedRow"] td {
    background-color: rgba(96, 165, 250, .24) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
}

/* ---------------------------------------------------------------------------
   A GRIDLOOKUP SHOWS EVERY SELECTED VALUE IN ONE FIXED-WIDTH BOX
   ---------------------------------------------------------------------------
   "BEHALA, branch1, CAP" - cut mid-word, so it reads as a rendering fault
   rather than as more-than-fits.

   Only the ELLIPSIS is added. The width is not touched: it comes from the
   page's own `.w150`, the theme layer sets no width or padding on a DX editor,
   and section 17 of theme-dark-polish.css is the record of what changing the
   geometry of a control inside a fixed-width cell does to a grid.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] input[class*="dxeEditArea"],
[data-bz-theme="dark"] input[class*="dxeEditArea"] {
    text-overflow: ellipsis;
}

/* ---------------------------------------------------------------------------
   THE EMPTY-DATA ROW'S CELLS  [2026-09-13]
   ---------------------------------------------------------------------------
   Section 4 themes `[class*="dxgvEmptyDataRow"]`, which is the <tr>. Section 13
   themes data cells as `td[class*="dxgv"]`. The empty row's <td> carries NO
   dxgv class, so it fell between the two and kept the skin's white - visible as
   a white block beside "No data to display", and wider than the text because
   the grid splits into two tables when columns do not fill the width.

   The indent cell has the same problem, and so does any bare <td> inside a
   dxgvTable - which is what the filler on the right of a short row is.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxgvEmptyDataRow"] > td,
[data-bz-theme="dark"] [class*="dxgvEmptyDataRow"] > td,
[data-bz-theme="nextgen"] [class*="dxgvIndentCell"],
[data-bz-theme="dark"] [class*="dxgvIndentCell"],
[data-bz-theme="nextgen"] table[class*="dxgvTable"] > tbody > tr > td:not([class]),
[data-bz-theme="dark"] table[class*="dxgvTable"] > tbody > tr > td:not([class]) {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* ===========================================================================
   16. THE GRID VOCABULARY THAT HAD NO RULE AT ALL  [2026-09-13]
   ---------------------------------------------------------------------------
   The white bar under an empty grid is `dxgvFSDC` - the Footer Scroll Div
   Container. It was never themed, because nothing in this repository mentions
   it: like the popup and pager vocabulary, it is emitted at runtime.

   Read out of DevExpress.Web.v15.1.dll: 71 dxgv* classes exist, 40 had no rule.
   The list below is the VISUAL subset. The rest are behavioural markers -
   dxgvSavedHtml, dxgvColumnIndex, dxgvRowVisibleIndex, dxgvSkipValueChanged,
   dxgvLinkClickHanlderAssigned and so on - which carry no appearance and are
   deliberately not named here.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxgvFSDC"],
[data-bz-theme="dark"] [class*="dxgvFSDC"],
[data-bz-theme="nextgen"] [class*="dxgvHFSC"],
[data-bz-theme="dark"] [class*="dxgvHFSC"],
[data-bz-theme="nextgen"] [class*="dxgvHFSAC"],
[data-bz-theme="dark"] [class*="dxgvHFSAC"],
[data-bz-theme="nextgen"] [class*="dxgvHeaderPanel"],
[data-bz-theme="dark"] [class*="dxgvHeaderPanel"],
[data-bz-theme="nextgen"] [class*="dxgvLoadingPanelStatusBar"],
[data-bz-theme="dark"] [class*="dxgvLoadingPanelStatusBar"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvDetailRow"],
[data-bz-theme="dark"] [class*="dxgvDetailRow"],
[data-bz-theme="nextgen"] [class*="dxgvDetailCell"],
[data-bz-theme="dark"] [class*="dxgvDetailCell"],
[data-bz-theme="nextgen"] [class*="dxgvPreviewRow"],
[data-bz-theme="dark"] [class*="dxgvPreviewRow"],
[data-bz-theme="nextgen"] [class*="dxgvGroupFooter"],
[data-bz-theme="dark"] [class*="dxgvGroupFooter"],
[data-bz-theme="nextgen"] [class*="dxgvEditFormCaption"],
[data-bz-theme="dark"] [class*="dxgvEditFormCaption"],
[data-bz-theme="nextgen"] [class*="dxgvInlineEditRow"],
[data-bz-theme="dark"] [class*="dxgvInlineEditRow"],
[data-bz-theme="nextgen"] [class*="dxgvInlineEditCell"],
[data-bz-theme="dark"] [class*="dxgvInlineEditCell"],
[data-bz-theme="nextgen"] [class*="dxgvBatchEditCell"],
[data-bz-theme="dark"] [class*="dxgvBatchEditCell"],
[data-bz-theme="nextgen"] [class*="dxgvFilterBar"],
[data-bz-theme="dark"] [class*="dxgvFilterBar"],
[data-bz-theme="nextgen"] [class*="dxgvFilterBuilder"],
[data-bz-theme="dark"] [class*="dxgvFilterBuilder"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* Error states keep their meaning; only the ground moves. */
[data-bz-theme="nextgen"] [class*="dxgvErrorCell"],
[data-bz-theme="dark"] [class*="dxgvErrorCell"],
[data-bz-theme="nextgen"] [class*="dxgvEditingErrorRow"],
[data-bz-theme="dark"] [class*="dxgvEditingErrorRow"] {
    background-color: rgba(248, 113, 113, .14) !important;
    background-image: none !important;
    color: var(--bz-danger-ink) !important;
}

[data-bz-theme="nextgen"] [class*="dxgvDataRowHover"],
[data-bz-theme="dark"] [class*="dxgvDataRowHover"],
[data-bz-theme="nextgen"] [class*="dxgvFocusedGroupRow"],
[data-bz-theme="dark"] [class*="dxgvFocusedGroupRow"] {
    background-color: var(--bz-bg-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
}

/* ---------------------------------------------------------------------------
   ONE RECIPE FOR EVERY DEVEXPRESS FIELD  [2026-09-13, restated 2026-09-14]
   ---------------------------------------------------------------------------
   Employee(s) is a DevExpress ButtonEdit; From Date and To Date are DateEdits
   inside `.for-cust-icon`. They were drawn to two different recipes and the
   ButtonEdit read as the smaller, thinner one, so this aligned it to the
   field ground that section 25 of theme-dark-polish.css was painting on the
   date wrapper.

   That wrapper paint has since been withdrawn - it boxed in the <label> too
   (see section 25) - which leaves THIS the single recipe for every DX field,
   date fields included. That is the right way round: the control carries its
   own appearance, no view-specific wrapper has to, and a DateEdit, a
   ButtonEdit and a plain <select> on one row all read as the same field.

   HEIGHT is left alone: a DX editor lays itself out as a table, and forcing a
   height on that is the hazard section 17 records - a purely visual change to
   a control inside a fixed-width cell is a layout change.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] [class*="dxeButtonEdit"],
[data-bz-theme="dark"] [class*="dxeTextBox"] {
    background-color: #0C1524 !important;
    border: 1px solid rgba(148, 163, 184, .22) !important;
    border-radius: var(--bz-r-sm, 8px) !important;
}

/* ---------------------------------------------------------------------------
   THE FOOTER ROW'S CELLS  [2026-09-13]
   ---------------------------------------------------------------------------
   Chased three times and guessed wrong twice. What it actually is:

   `PerformanceGridView.cshtml` sets `ShowFooter = true` AND
   `HorizontalScrollBarMode = ScrollBarMode.Visible`. With scrolling on,
   DevExpress renders the footer as its OWN table BELOW the horizontal
   scrollbar - which is exactly where the white bar sits, under the dark
   scrollbar track rather than inside the grid body.

   The footer <tr> was already covered, by two rules. The <td> was not: section
   13 addresses data cells and sets only padding and border colours, never a
   background, so the skin's own footer cell fill survived both.

   A row rule does not repaint a cell that brings its own background.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] tr[class*="dxgvFooter"] > td,
[data-bz-theme="dark"] tr[class*="dxgvFooter"] > td,
[data-bz-theme="nextgen"] [class*="dxgvFooter"] > td,
[data-bz-theme="dark"] [class*="dxgvFooter"] > td,
[data-bz-theme="nextgen"] td[class*="dxgvFooter"],
[data-bz-theme="dark"] td[class*="dxgvFooter"],
[data-bz-theme="nextgen"] [class*="dxgvStatusBar"],
[data-bz-theme="dark"] [class*="dxgvStatusBar"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* The footer travels in its own table when the grid scrolls, so that table and
   whatever wraps it must not stay light either. */
[data-bz-theme="nextgen"] table[class*="dxgvFooter"],
[data-bz-theme="dark"] table[class*="dxgvFooter"],
[data-bz-theme="nextgen"] div[class*="dxgvFooter"],
[data-bz-theme="dark"] div[class*="dxgvFooter"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    border-color: var(--bz-border) !important;
}
