/* ================================================================
   Bootstrap 3 → Bootstrap 5 CSS Override for Attendance Page
   Purpose: Restore Bootstrap 3 layout styles without reverting libraries
   ================================================================ */

/* ================================================================
0. BOOTSTRAP 3 CLASSES DROPPED ENTIRELY IN BOOTSTRAP 5+
================================================================
   FIX: found independently on pto-request-que.php (".col-sm-offset-4")
   and pto-request-personnel.php (".col-md-offset-2") - both times the
   class computed to zero effect under Bootstrap 5, throwing off layout
   in a way that had nothing to do with any rule in this file; Bootstrap
   5 simply has no definition for these class names at all. Rather than
   keep re-diagnosing "why does this offset/float/hide class do nothing"
   page by page, this section restores every Bootstrap 3 class in this
   category up front, mechanically, from Bootstrap 3's own documented
   values - so it's covered site-wide before the next page hits it.

   Restoring these is inherently low-risk: since Bootstrap 5 never
   defines any of these class *names*, there is nothing for the rules
   below to collide with - they can only ever apply to markup that
   still uses the old Bootstrap 3 name, which by definition means it
   was never migrated to a Bootstrap 5 equivalent and has been getting
   zero styling from either framework until now.

   Deliberately NOT included here: Bootstrap 3 *components* dropped in
   4+ (".panel"/".panel-heading"/etc., ".well", ".thumbnail",
   ".navbar-fixed-top", ".input-group-addon", ".hidden-xs"/".visible-md"
   -style responsive-visibility utilities, ".label"). Those need real
   visual dimensions/colors/breakpoints verified against DevOps's actual
   computed styles per instance (see the ".new_left_bar .panel" block
   further down for the established per-component pattern) - a blanket
   guess at "textbook Bootstrap 3 values" for a whole component risks
   NOT matching DevOps (this repo's style-new.css has already diverged
   from DevOps's copy in places - see the migration playbook's root
   cause #7), which would defeat the point of this migration pass. Keep
   fixing those case-by-case as encountered, the same way as so far. */

/* ---- Grid column widths - restores Bootstrap 3's ".col-xs-{1-12}"
   (the un-breakpointed baseline column width, always active regardless
   of viewport). Bootstrap 4+ renamed this tier to the bare ".col-{1-12}"
   (no "xs" infix) and never kept "col-xs-*" as an alias, so old markup
   using it gets no width at all -- it falls back to this codebase's own
   ".row > *" default of "width: 100%", collapsing every column in the
   row to a full-width stack instead of sitting side by side. Bootstrap
   5's own ".row > *" rule (bootstrap.min.css) already supplies the
   shared flex-item base every column needs (flex-shrink, gutter
   padding); each of these only needs to override the two properties
   Bootstrap 5's own ".col-{1-12}" itself sets on top of that -- "flex"
   and "width" -- copied verbatim from this codebase's own vendored
   "assets-v2/css/bootstrap/5.3.8/bootstrap.min.css" (e.g. its ".col-6"
   is "flex:0 0 auto;width:50%"), so a row mixing old "col-xs-*" columns
   with real Bootstrap 5 "col-md-*"/etc. columns lays out identically
   either way. ".col-xs-12" is included even though it matches the
   ".row > *" default of 100% -- restoring "flex: 0 0 auto" still
   matters, since without it the column would keep the default
   ".col"-style "flex: 1 0 0" (grow to fill available space) instead of
   a fixed width, which only looks the same as 100% when it is in fact
   the sole column in its row. */

.col-xs-1 {
  flex: 0 0 auto !important;
  width: 8.33333333% !important;
}

.col-xs-2 {
  flex: 0 0 auto !important;
  width: 16.66666667% !important;
}

.col-xs-3 {
  flex: 0 0 auto !important;
  width: 25% !important;
}

.col-xs-4 {
  flex: 0 0 auto !important;
  width: 33.33333333% !important;
}

.col-xs-5 {
  flex: 0 0 auto !important;
  width: 41.66666667% !important;
}

.col-xs-6 {
  flex: 0 0 auto !important;
  width: 50% !important;
}

.col-xs-7 {
  flex: 0 0 auto !important;
  width: 58.33333333% !important;
}

.col-xs-8 {
  flex: 0 0 auto !important;
  width: 66.66666667% !important;
}

.col-xs-9 {
  flex: 0 0 auto !important;
  width: 75% !important;
}

.col-xs-10 {
  flex: 0 0 auto !important;
  width: 83.33333333% !important;
}

.col-xs-11 {
  flex: 0 0 auto !important;
  width: 91.66666667% !important;
}

.col-xs-12 {
  flex: 0 0 auto !important;
  width: 100% !important;
}

/* ---- Grid offsets - restores Bootstrap 3's ".col-{bp}-offset-{1-11}"
   (margin-left: n/12 columns). ".col-{bp}-offset-0" isn't included: it
   was Bootstrap 3's explicit "cancel a smaller breakpoint's offset"
   reset, and margin-left:0 is already Bootstrap 5's untouched default
   for every ".col-*", so restoring it would be a no-op. */

.col-xs-offset-1 {
  margin-left: 8.33333333% !important;
}

.col-xs-offset-2 {
  margin-left: 16.66666667% !important;
}

.col-xs-offset-3 {
  margin-left: 25% !important;
}

.col-xs-offset-4 {
  margin-left: 33.33333333% !important;
}

.col-xs-offset-5 {
  margin-left: 41.66666667% !important;
}

.col-xs-offset-6 {
  margin-left: 50% !important;
}

.col-xs-offset-7 {
  margin-left: 58.33333333% !important;
}

.col-xs-offset-8 {
  margin-left: 66.66666667% !important;
}

.col-xs-offset-9 {
  margin-left: 75% !important;
}

.col-xs-offset-10 {
  margin-left: 83.33333333% !important;
}

.col-xs-offset-11 {
  margin-left: 91.66666667% !important;
}

/* ---- Grid push/pull - restores Bootstrap 3's ".col-{bp}-push-{1-11}"/
   ".col-{bp}-pull-{1-11}" (source-order reflow via relative left/right
   offsets). Each needs "position: relative" restored alongside it -
   Bootstrap 3's own ".col-*" rule set that unconditionally; Bootstrap 5
   only sets it on flex items actually inside a ".row", so a push/pull
   column outside one (or one whose ".row" has other issues) has no
   positioned context for "left"/"right" to resolve against at all. */

.col-xs-push-1 {
  position: relative !important;
  left: 8.33333333% !important;
}

.col-xs-push-2 {
  position: relative !important;
  left: 16.66666667% !important;
}

.col-xs-push-3 {
  position: relative !important;
  left: 25% !important;
}

.col-xs-push-4 {
  position: relative !important;
  left: 33.33333333% !important;
}

.col-xs-push-5 {
  position: relative !important;
  left: 41.66666667% !important;
}

.col-xs-push-6 {
  position: relative !important;
  left: 50% !important;
}

.col-xs-push-7 {
  position: relative !important;
  left: 58.33333333% !important;
}

.col-xs-push-8 {
  position: relative !important;
  left: 66.66666667% !important;
}

.col-xs-push-9 {
  position: relative !important;
  left: 75% !important;
}

.col-xs-push-10 {
  position: relative !important;
  left: 83.33333333% !important;
}

.col-xs-push-11 {
  position: relative !important;
  left: 91.66666667% !important;
}

.col-xs-pull-1 {
  position: relative !important;
  right: 8.33333333% !important;
}

.col-xs-pull-2 {
  position: relative !important;
  right: 16.66666667% !important;
}

.col-xs-pull-3 {
  position: relative !important;
  right: 25% !important;
}

.col-xs-pull-4 {
  position: relative !important;
  right: 33.33333333% !important;
}

.col-xs-pull-5 {
  position: relative !important;
  right: 41.66666667% !important;
}

.col-xs-pull-6 {
  position: relative !important;
  right: 50% !important;
}

.col-xs-pull-7 {
  position: relative !important;
  right: 58.33333333% !important;
}

.col-xs-pull-8 {
  position: relative !important;
  right: 66.66666667% !important;
}

.col-xs-pull-9 {
  position: relative !important;
  right: 75% !important;
}

.col-xs-pull-10 {
  position: relative !important;
  right: 83.33333333% !important;
}

.col-xs-pull-11 {
  position: relative !important;
  right: 91.66666667% !important;
}

@media (min-width: 768px) {
  .col-sm-offset-1 {
    margin-left: 8.33333333% !important;
  }

  .col-sm-offset-2 {
    margin-left: 16.66666667% !important;
  }

  .col-sm-offset-3 {
    margin-left: 25% !important;
  }

  .col-sm-offset-4 {
    margin-left: 33.33333333% !important;
  }

  .col-sm-offset-5 {
    margin-left: 41.66666667% !important;
  }

  .col-sm-offset-6 {
    margin-left: 50% !important;
  }

  .col-sm-offset-7 {
    margin-left: 58.33333333% !important;
  }

  .col-sm-offset-8 {
    margin-left: 66.66666667% !important;
  }

  .col-sm-offset-9 {
    margin-left: 75% !important;
  }

  .col-sm-offset-10 {
    margin-left: 83.33333333% !important;
  }

  .col-sm-offset-11 {
    margin-left: 91.66666667% !important;
  }

  .col-sm-push-1 {
    position: relative !important;
    left: 8.33333333% !important;
  }

  .col-sm-push-2 {
    position: relative !important;
    left: 16.66666667% !important;
  }

  .col-sm-push-3 {
    position: relative !important;
    left: 25% !important;
  }

  .col-sm-push-4 {
    position: relative !important;
    left: 33.33333333% !important;
  }

  .col-sm-push-5 {
    position: relative !important;
    left: 41.66666667% !important;
  }

  .col-sm-push-6 {
    position: relative !important;
    left: 50% !important;
  }

  .col-sm-push-7 {
    position: relative !important;
    left: 58.33333333% !important;
  }

  .col-sm-push-8 {
    position: relative !important;
    left: 66.66666667% !important;
  }

  .col-sm-push-9 {
    position: relative !important;
    left: 75% !important;
  }

  .col-sm-push-10 {
    position: relative !important;
    left: 83.33333333% !important;
  }

  .col-sm-push-11 {
    position: relative !important;
    left: 91.66666667% !important;
  }

  .col-sm-pull-1 {
    position: relative !important;
    right: 8.33333333% !important;
  }

  .col-sm-pull-2 {
    position: relative !important;
    right: 16.66666667% !important;
  }

  .col-sm-pull-3 {
    position: relative !important;
    right: 25% !important;
  }

  .col-sm-pull-4 {
    position: relative !important;
    right: 33.33333333% !important;
  }

  .col-sm-pull-5 {
    position: relative !important;
    right: 41.66666667% !important;
  }

  .col-sm-pull-6 {
    position: relative !important;
    right: 50% !important;
  }

  .col-sm-pull-7 {
    position: relative !important;
    right: 58.33333333% !important;
  }

  .col-sm-pull-8 {
    position: relative !important;
    right: 66.66666667% !important;
  }

  .col-sm-pull-9 {
    position: relative !important;
    right: 75% !important;
  }

  .col-sm-pull-10 {
    position: relative !important;
    right: 83.33333333% !important;
  }

  .col-sm-pull-11 {
    position: relative !important;
    right: 91.66666667% !important;
  }
}

@media (min-width: 992px) {
  .col-md-offset-1 {
    margin-left: 8.33333333% !important;
  }

  .col-md-offset-2 {
    margin-left: 16.66666667% !important;
  }

  .col-md-offset-3 {
    margin-left: 25% !important;
  }

  .col-md-offset-4 {
    margin-left: 33.33333333% !important;
  }

  .col-md-offset-5 {
    margin-left: 41.66666667% !important;
  }

  .col-md-offset-6 {
    margin-left: 50% !important;
  }

  .col-md-offset-7 {
    margin-left: 58.33333333% !important;
  }

  .col-md-offset-8 {
    margin-left: 66.66666667% !important;
  }

  .col-md-offset-9 {
    margin-left: 75% !important;
  }

  .col-md-offset-10 {
    margin-left: 83.33333333% !important;
  }

  .col-md-offset-11 {
    margin-left: 91.66666667% !important;
  }

  .col-md-push-1 {
    position: relative !important;
    left: 8.33333333% !important;
  }

  .col-md-push-2 {
    position: relative !important;
    left: 16.66666667% !important;
  }

  .col-md-push-3 {
    position: relative !important;
    left: 25% !important;
  }

  .col-md-push-4 {
    position: relative !important;
    left: 33.33333333% !important;
  }

  .col-md-push-5 {
    position: relative !important;
    left: 41.66666667% !important;
  }

  .col-md-push-6 {
    position: relative !important;
    left: 50% !important;
  }

  .col-md-push-7 {
    position: relative !important;
    left: 58.33333333% !important;
  }

  .col-md-push-8 {
    position: relative !important;
    left: 66.66666667% !important;
  }

  .col-md-push-9 {
    position: relative !important;
    left: 75% !important;
  }

  .col-md-push-10 {
    position: relative !important;
    left: 83.33333333% !important;
  }

  .col-md-push-11 {
    position: relative !important;
    left: 91.66666667% !important;
  }

  .col-md-pull-1 {
    position: relative !important;
    right: 8.33333333% !important;
  }

  .col-md-pull-2 {
    position: relative !important;
    right: 16.66666667% !important;
  }

  .col-md-pull-3 {
    position: relative !important;
    right: 25% !important;
  }

  .col-md-pull-4 {
    position: relative !important;
    right: 33.33333333% !important;
  }

  .col-md-pull-5 {
    position: relative !important;
    right: 41.66666667% !important;
  }

  .col-md-pull-6 {
    position: relative !important;
    right: 50% !important;
  }

  .col-md-pull-7 {
    position: relative !important;
    right: 58.33333333% !important;
  }

  .col-md-pull-8 {
    position: relative !important;
    right: 66.66666667% !important;
  }

  .col-md-pull-9 {
    position: relative !important;
    right: 75% !important;
  }

  .col-md-pull-10 {
    position: relative !important;
    right: 83.33333333% !important;
  }

  .col-md-pull-11 {
    position: relative !important;
    right: 91.66666667% !important;
  }
}

@media (min-width: 1200px) {
  .col-lg-offset-1 {
    margin-left: 8.33333333% !important;
  }

  .col-lg-offset-2 {
    margin-left: 16.66666667% !important;
  }

  .col-lg-offset-3 {
    margin-left: 25% !important;
  }

  .col-lg-offset-4 {
    margin-left: 33.33333333% !important;
  }

  .col-lg-offset-5 {
    margin-left: 41.66666667% !important;
  }

  .col-lg-offset-6 {
    margin-left: 50% !important;
  }

  .col-lg-offset-7 {
    margin-left: 58.33333333% !important;
  }

  .col-lg-offset-8 {
    margin-left: 66.66666667% !important;
  }

  .col-lg-offset-9 {
    margin-left: 75% !important;
  }

  .col-lg-offset-10 {
    margin-left: 83.33333333% !important;
  }

  .col-lg-offset-11 {
    margin-left: 91.66666667% !important;
  }

  .col-lg-push-1 {
    position: relative !important;
    left: 8.33333333% !important;
  }

  .col-lg-push-2 {
    position: relative !important;
    left: 16.66666667% !important;
  }

  .col-lg-push-3 {
    position: relative !important;
    left: 25% !important;
  }

  .col-lg-push-4 {
    position: relative !important;
    left: 33.33333333% !important;
  }

  .col-lg-push-5 {
    position: relative !important;
    left: 41.66666667% !important;
  }

  .col-lg-push-6 {
    position: relative !important;
    left: 50% !important;
  }

  .col-lg-push-7 {
    position: relative !important;
    left: 58.33333333% !important;
  }

  .col-lg-push-8 {
    position: relative !important;
    left: 66.66666667% !important;
  }

  .col-lg-push-9 {
    position: relative !important;
    left: 75% !important;
  }

  .col-lg-push-10 {
    position: relative !important;
    left: 83.33333333% !important;
  }

  .col-lg-push-11 {
    position: relative !important;
    left: 91.66666667% !important;
  }

  .col-lg-pull-1 {
    position: relative !important;
    right: 8.33333333% !important;
  }

  .col-lg-pull-2 {
    position: relative !important;
    right: 16.66666667% !important;
  }

  .col-lg-pull-3 {
    position: relative !important;
    right: 25% !important;
  }

  .col-lg-pull-4 {
    position: relative !important;
    right: 33.33333333% !important;
  }

  .col-lg-pull-5 {
    position: relative !important;
    right: 41.66666667% !important;
  }

  .col-lg-pull-6 {
    position: relative !important;
    right: 50% !important;
  }

  .col-lg-pull-7 {
    position: relative !important;
    right: 58.33333333% !important;
  }

  .col-lg-pull-8 {
    position: relative !important;
    right: 66.66666667% !important;
  }

  .col-lg-pull-9 {
    position: relative !important;
    right: 75% !important;
  }

  .col-lg-pull-10 {
    position: relative !important;
    right: 83.33333333% !important;
  }

  .col-lg-pull-11 {
    position: relative !important;
    right: 91.66666667% !important;
  }
}

/* ---- Other Bootstrap 3 utility classes dropped outright (not renamed
   to a same-behavior Bootstrap 5 equivalent the markup could pick up
   automatically) - each picked because it's a plain, unambiguous value
   straight from Bootstrap 3's own source, not something guessed. */

/* Bootstrap 3's float utilities; renamed .float-start/.float-end in
   Bootstrap 5 with the old names dropped entirely. */
.pull-left {
  float: left !important;
}

.pull-right {
  float: right !important;
}

/* Bootstrap 3's block-centering utility; renamed .mx-auto (only handles
   the margins, not "display: block") in Bootstrap 5. */
.center-block {
  display: block !important;
  margin-left: auto !important;
  margin-right: auto !important;
}

/* Bootstrap 3's unconditional hide utility (".hide" in this codebase's
   own style-new.css is a different, pre-existing class - not the same
   as Bootstrap's ".hidden", which Bootstrap 5 doesn't define at all). */
.hidden {
  display: none !important;
}

/* FIX: Bootstrap 3's ".form-control[readonly]"/".form-control:disabled"
   shipped with a built-in grey "background-color: #eee" (uat.i-t-g.net's
   reference build still shows it - e.g. office/office-info.php's
   read-only "Office Name"/"Payroll PC#"/"Prior Week"/"Current Week"
   fields). Bootstrap 5 dropped that default entirely - readonly/disabled
   inputs render with the exact same white background as an editable
   one, making them visually indistinguishable. Global rather than
   page-scoped since ".form-control[readonly]" is used sitewide for this
   same "display a value the user can't edit" pattern, and Bootstrap 3's
   own value (verbatim, not a guess) can only ever apply to elements that
   are actually readonly/disabled - it can't affect anything else. */
.form-control[readonly],
.form-control:disabled {
  background-color: #eee !important;
  opacity: 1 !important;
}

/* FIX: ".thead-dark"/".thead-light" (Bootstrap 4 - office/office-info.php's
   "Office Contact" table, uat.i-t-g.net's reference build still shows it
   styled) were dropped outright in Bootstrap 5 (replaced by ".table-dark"/
   ".table-light" on the <table> or <thead> itself), so the class currently
   does nothing and every header renders as plain unstyled white/light grey
   instead of DevOps's dark header row. This codebase's own vendored
   "css/bootstrap4.4.1.min.css" confirms these are Bootstrap 4's exact,
   documented values - restored mechanically rather than a guess, same as
   the ".hidden"/".pull-left"/etc. restorations above. */
.thead-dark th {
  color: #fff !important;
  background-color: #343a40 !important;
  border-color: #454d55 !important;
}

.thead-light th {
  color: #495057 !important;
  background-color: #e9ecef !important;
  border-color: #dee2e6 !important;
}

/* ---- Added 2026-08-31, same "verbatim from Bootstrap 3's own source,
   not a guess" reasoning as everything else in this section. A sitewide
   audit of the already-migrated modules turned up widespread usage of
   these class names that nobody had checked for yet - each one below
   is a plain utility/typography class Bootstrap 5 defines no CSS for at
   all (dropped outright, not renamed to something the markup could pick
   up automatically), so restoring Bootstrap 3's own value can only ever
   apply to elements that were getting zero styling from Bootstrap 5. */

/* Bootstrap 3's text-alignment utilities; renamed .text-start/.text-end
   in Bootstrap 5 (RTL-friendly naming) with the old names dropped. */
.text-left {
  text-align: left !important;
}

.text-right {
  text-align: right !important;
}

/* Bootstrap 3's help text under a form control; renamed .form-text in
   Bootstrap 4+ with the old name dropped entirely. */
.help-block {
  display: block !important;
  margin-top: 5px !important;
  margin-bottom: 10px !important;
  color: #737373 !important;
}

/* Bootstrap 3's responsive-image utilities; renamed .img-fluid (and
   the radius utilities folded into the general ".rounded"/".rounded-circle"
   naming) in Bootstrap 4+ with the old names dropped. */
.img-responsive {
  display: block !important;
  max-width: 100% !important;
  height: auto !important;
}

.img-circle {
  border-radius: 50% !important;
}

.img-rounded {
  border-radius: 6px !important;
}

/* Bootstrap 3's dropdown-caret triangle; Bootstrap 5 draws its caret via
   ::after on .dropdown-toggle instead of a standalone class, so a bare
   ".caret" element (still used on a handful of pages) renders as nothing. */
.caret {
  display: inline-block !important;
  width: 0 !important;
  height: 0 !important;
  margin-left: 2px !important;
  vertical-align: middle !important;
  border-top: 4px solid !important;
  border-right: 4px solid transparent !important;
  border-left: 4px solid transparent !important;
}

/* Bootstrap 3's compact-table modifier; renamed .table-sm in Bootstrap 4+
   with the old name dropped. */
.table-condensed > thead > tr > th,
.table-condensed > tbody > tr > th,
.table-condensed > tfoot > tr > th,
.table-condensed > thead > tr > td,
.table-condensed > tbody > tr > td,
.table-condensed > tfoot > tr > td {
  padding: 5px !important;
}

/* Bootstrap 3's modal/alert dismiss "x" button; renamed .btn-close in
   Bootstrap 5 with an entirely different rendering model (background-image
   icon, no text glyph) - old markup (a literal "&times;" inside
   class="close") gets no styling at all under Bootstrap 5. This is a
   plain text-glyph treatment with no site-specific color/sizing to guess
   at, unlike the component-level classes intentionally left out of this
   section (see the note further up) - restored verbatim from Bootstrap
   3's own source. Note this only restores the *look*; the dismiss click
   itself still needs the surrounding data-dismiss -> data-bs-dismiss
   attribute, handled separately by the shim in include/header.php. */
.close {
  float: right !important;
  font-size: 21px !important;
  font-weight: bold !important;
  line-height: 1 !important;
  color: #000 !important;
  text-shadow: 0 1px 0 #fff !important;
  opacity: .2 !important;
}

.close:hover,
.close:focus {
  color: #000 !important;
  text-decoration: none !important;
  cursor: pointer !important;
  opacity: .5 !important;
}

button.close {
  padding: 0 !important;
  cursor: pointer !important;
  background: transparent !important;
  border: 0 !important;
  -webkit-appearance: none !important;
}

/* ================================================================
1. HEADER - FULL WIDTH - DEVOPS DESIGN MATCH
================================================================ */

/* FIX: header .top_part (logo bar) and .medil_part ("Office - Training"
   bar) each wrap their content in Bootstrap's fixed-width .container
   (max-width caps out around 1320px and auto-centers), while the nav
   bar below them correctly uses .container-fluid (full width). That
   mismatch left visible empty margins on both sides of the header,
   unlike DevOps where these sections span the full page width. Scoped
   to header only so other .container usage on the page is untouched. */
header .container {
  width: 100% !important;
  max-width: none !important;
  margin: 0 !important;
}

/* FIX: Bootstrap 5's default h1 uses responsive, viewport-relative
   sizing (font-size: calc(1.375rem + 1.5vw)) instead of Bootstrap 3's
   fixed 36px/1.1 line-height. That made the FUSE logo heading (and so
   the whole blue top bar, which sizes itself around it) render taller
   than DevOps - 68px vs 63px at this viewport width. Restoring the
   fixed Bootstrap 3 values here, scoped to just this logo heading. */
header .top_part h1 {
  font-size: 36px !important;
  line-height: 1.1 !important;
}

/* FIX: Keep "F U S E | WorkForce" on ONE line. Under Bootstrap 5 the
   logo lived in a rigid 33% col-md-4; once that column was narrower than
   the two floated headings, WorkForce wrapped under FUSE and inflated
   the fixed header so page titles sat underneath it. Prefer flex wrap:
   logo column sizes to content and never wraps; the icons/user column
   takes remaining space and drops to the next row as a unit when the
   viewport is too narrow for both side-by-side. */
header .top_part .row {
  display: flex !important;
  flex-wrap: wrap !important;
  align-items: center !important;
}

header .top_part .col-md-4 {
  float: none !important;
  width: auto !important;
  max-width: 100% !important;
  flex: 0 0 auto !important;
  display: flex !important;
  flex-wrap: wrap !important;
  align-items: center !important;
  gap: 0 !important;
}

header .top_part .col-md-4 > h1,
header .top_part .col-md-4 > h2 {
  float: none !important;
  flex: 0 0 auto !important;
  white-space: nowrap !important;
}

header .top_part .col-md-8 {
  float: none !important;
  width: auto !important;
  max-width: 100% !important;
  flex: 1 1 420px !important;
  margin-left: auto !important;
  min-width: 0 !important;
}

header .top_part .col-md-8 .TopIcons {
  text-align: right !important;
  white-space: nowrap !important;
}

/* Grey office bar still needs the Bootstrap 3 float/width restore —
   it is not part of the logo/icons wrap behavior above. */
@media (min-width: 992px) {
  header .medil_part [class*="col-md-"] {
    position: relative !important;
    float: left !important;
    min-height: 1px !important;
  }

  header .medil_part .col-md-4 {
    width: 33.33333333% !important;
  }

  header .medil_part .col-md-8 {
    width: 66.66666667% !important;
  }
}

/* FIX: DevOps keeps the office selector at a fixed desktop width inside
   the grey bar. On the target it collapses to ~244px, which changes the
   visual balance of the header and makes the bar look unfinished. */
header .medil_part .select2-container {
  width: 422px !important;
  max-width: 100% !important;
}

/* FIX: "FUSE new design system update" (commit 71e1a96761c, 2026-09-03)
   added a sitewide ".medil_part { display:none !important }" to
   style-new.css, on the assumption that ".medil_part" is always the
   redundant/leftover grey "Office" bar that the new header design no
   longer needs. That's true on pages using the modern header only, but
   ~15 older pages (e.g. work-order-view.php, via
   include/sub_header_not_selected_wo2.php) still render their entire
   working nav menu (menu.php's "#myNavbar") inside their own
   ".medil_part" wrapper - the sitewide rule hid the whole top menu on
   every one of those pages with no visible error. Confirmed live
   against devops (which predates that commit and never had this rule)
   on 2026-09-03: only re-show ".medil_part" when it actually contains
   the nav, leaving the intended new-design-system behavior untouched
   everywhere else. */
.medil_part:has(#myNavbar) {
  display: block !important;
}
.medil_part:has(#myNavbar) .container {
  display: none;
}

/* ================================================================
3. PAGE CONTENT (Attendance heading through DataTable) - DEVOPS MATCH
================================================================ */

/* FIX: Bootstrap 5's .btn uses a CSS variable (--bs-btn-font-size)
   that resolves to 16px by default, vs Bootstrap 3's fixed 14px.
   Buttons with a more specific custom class (e.g. .btn-blue used by
   Clear Selection/Active/Inactive) already set their own font-size
   and were unaffected, but plain ".btn btn-primary/btn-success"
   buttons (e.g. Search, and the Update/Cancel modal buttons) were
   rendering 2px larger than DevOps. */
/* FIX: Bootstrap 3's .btn also includes "white-space: nowrap" in its
   base style; Bootstrap 5 dropped it. Without it, short-but-tight
   buttons (e.g. the DataTable's "Add Note" button, ~58px wide) wrap
   their label onto a second line, which then gets clipped by the
   row's fixed height. Restoring the BS3 behavior here. */
.btn {
  font-size: 14px !important;
  white-space: nowrap !important;
}

/* FIX: Same pattern as .btn above - Bootstrap 5's .form-control uses
   font-size: 1rem (16px) by default vs Bootstrap 3's 14px. Affects
   every plain text input sitewide, including the DataTable row inputs
   (Scheduled StartTime/EndTime, ClockedIn, etc.). Padding/border/height
   already matched DevOps exactly - only font-size was off. Bootstrap 5
   reboot also switches body/headings to system-ui; DevOps uses
   Conv_MyriadPro-Light at 14px body and 33px page titles. */
body {
  font-family: 'Conv_MyriadPro-Light', Verdana, Geneva, sans-serif;
  font-size: 14px;
  color: #212121;
}
.heading_bold h2 {
  font-family: 'Conv_MyriadPro-Light', Verdana, Geneva, sans-serif;
  font-size: 33px;
  font-weight: 300;
}
.form-control {
  font-family: 'Conv_MyriadPro-Light', Verdana, Geneva, sans-serif;
  font-size: 14px !important;
}

/* FIX: This codebase uses Bootstrap 3's ".form-group" pattern sitewide
   (100+ files) to stack labeled filter/form rows with even spacing.
   Bootstrap 3 shipped ".form-group { margin-bottom: 15px; }" as part of
   its forms CSS; Bootstrap 5 dropped the ".form-group" component
   entirely (no rule for it at all, replaced sitewide by utility classes
   like ".mb-3" - but this codebase's markup was never migrated to use
   those), so every stacked control - dropdowns, date pickers, filter
   rows - sits flush against the next one with no gap, instead of
   DevOps's evenly-spaced rows. Restoring Bootstrap 3's own default. */
.form-group {
  margin-bottom: 15px;
}

/* FIX: Department/Supervisor/Custom Groups dropdown buttons come from
   the bootstrap-multiselect plugin. On DevOps the generated toggle
   button includes "btn btn-default" (so it picked up Bootstrap 3
   sizing same as the .btn fix above), but locally the plugin/markup
   generates "form-select ... custom-select" instead - Bootstrap 5
   form-control classes with their own 16px default and extra right
   padding reserved for a native <select> arrow icon that this custom
   dropdown doesn't use. Restoring the Bootstrap 3 button proportions. */
.multiselect.dropdown-toggle {
  font-size: 14px !important;
  padding: 6px 12px !important;
}

/* FIX: the toggle button's open/focus state uses Bootstrap 5's default blue
   focus ring (it carries a "form-select" class - see above - so it gets
   ".form-select:focus"'s box-shadow), whereas DevOps's plain "btn
   btn-default" markup gets Bootstrap 3's classic open/active "pressed
   button" look instead: grey background, darker border, a subtle inset
   shadow, no colored ring. Restoring that when the dropdown is open
   (".show", added by Bootstrap 5's dropdown JS) or focused, and
   overriding the native blue ring so it doesn't also show. Colors copied
   directly from DevOps's computed styles. */
.multiselect.dropdown-toggle.show,
.multiselect.dropdown-toggle:focus {
  background-color: #d4d4d4 !important;
  border-color: #8c8c8c !important;
  color: #333 !important;
  box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125) !important;
}

/* FIX: DevOps's bootstrap-multiselect build renders its caret as a
   literal "<b class="caret">" child element (Bootstrap 3 convention).
   This site's bootstrap-multiselect@2.0.0 build doesn't generate that
   element at all - it relies on Bootstrap 5's own ".dropdown-toggle"
   CSS to draw the caret via a "::after" pseudo-element instead - but
   the plugin's own stylesheet ships ".multiselect.dropdown-toggle:after
   { display: none }" (presumably written back when this build still
   expected the "<b class="caret">" approach), so the one caret
   mechanism it does support ends up switched off. Turning the
   pseudo-element back on lets Bootstrap 5's built-in triangle render. */
.multiselect.dropdown-toggle::after {
  display: inline-block !important;
}

/* FIX: The button's own "form-select" class (see the size/padding fix
   above) also brings Bootstrap 5's ".form-select" chevron
   background-image - a second, separate arrow indicator meant for a
   real <select>, not a dropdown-toggle button. With the ".dropdown-
   toggle::after" triangle now restored (fix above), the button showed
   both at once. DevOps's markup has no "form-select" class, so it only
   ever had the one caret; removing the background-image here matches
   that without touching ".form-select" on actual <select> elements
   elsewhere. */
.multiselect.dropdown-toggle.form-select {
  background-image: none !important;
}

/* FIX: The Department/Supervisor/Custom Groups dropdown menu (opened
   from the button above) now works after the Popper.js fix, but its
   markup is a newer, Bootstrap-5-native version of the multiselect
   plugin (each option is a <button class="dropdown-item"> rather than
   DevOps's older <li><label><input>) - a different, legitimate
   implementation, not something to force back into the old structure.
   What still needs fixing is that Bootstrap 5's plain .dropdown-menu
   defaults don't match the site's look: it auto-sizes to its content
   (205px) instead of matching the 400px toggle button, uses BS5's
   16px base font-size instead of the site's 14px, and is missing the
   drop shadow / uses BS5's default 6px corner radius instead of the
   site's 4px.
   FIX 2 [multiselect height]: the plugin's old markup wrapped options in
   a "<ul class=\"multiselect-container dropdown-menu\">", which this
   codebase's own page-level CSS (e.g. personnel-action-notice.php's
   ".btn-group ul { max-height: 300px; overflow-y: scroll; }") relied on
   to keep long option lists (e.g. the Personnel selector's full employee
   list) scrollable inside a fixed-height box. bootstrap-multiselect@2.0.0
   renders this same container as a "<div>" instead of a "<ul>" (see the
   FIX above), so that selector no longer matches anything - the dropdown
   now grows to fit every option instead of capping height, pushing far
   past the viewport with no internal scrollbar. Restoring the same
   300px/scroll behavior here, scoped to the actual container class so it
   applies regardless of which tag the plugin renders it as. */
.multiselect-container.dropdown-menu {
  width: 100% !important;
  min-width: 100% !important;
  font-size: 14px !important;
  border-radius: 4px !important;
  box-shadow: 0 6px 12px rgba(0, 0, 0, 0.176) !important;
  max-height: 300px !important;
  overflow-y: auto !important;
  overflow-x: hidden !important;
}

.multiselect-container.dropdown-menu .dropdown-item {
  font-size: 14px !important;
}

/* FDCM-3547: BS5 markup renamed "col-md-offset-3" to "offset-3"
   (personnel/ajax/selector_ajax/ajax_personel_docs.php), so this override
   stopped matching and the 25% offset pushed the Personnel Documents panel
   right of centre. Match both class names. */
.col-md-6.offset-3.left_sidw_fx {
	margin: 0 15px;
}

/* FIX: work-order-pages/billing-reconcile-import_schedule_SP.php's "Export
   To" dropup (second grid) - same underlying gap as the multiselect fix
   above: Bootstrap 5's plain .dropdown-menu has no drop shadow (DevOps's
   Bootstrap 3 build gives every dropdown-menu "box-shadow: 0 6px 12px
   rgba(0,0,0,.176)" by default) and uses BS5's 16px base font-size/6px
   corner radius instead of the site's 14px/4px. Without the shadow the menu
   - which only has a near-invisible 1px rgba(0,0,0,.176) border - reads as
   unstyled text floating over the page instead of a card popped up off the
   button. Scoped to this one dropdown rather than every ".dropdown-menu"
   sitewide, since only this page's markup was reported/verified against
   DevOps. */
.billing-reconcile-export.dropup .dropdown-menu {
  border-radius: 4px !important;
  box-shadow: 0 6px 12px rgba(0, 0, 0, 0.176) !important;
  font-size: 14px !important;
  padding: 5px 0 !important;
}

/* FIX: Each option row (.dropdown-item) had several problems vs DevOps:
   1) Visible "border-top"/"border-bottom: 1px solid #999" dividers
      between every row plus taller padding, giving 36px rows vs
      DevOps's compact 26px, completely borderless rows.
   2) Bootstrap 5's default 3px border-radius on each row, which
      DevOps's rows don't have at all.
   3) The selected/checked row highlights with Bootstrap 5's default
      light-grey .active background (#D3D3D3) instead of Bootstrap 3's
      Carbon Blue 60 active dropdown item (white
      text) that DevOps uses. */
.multiselect-container.dropdown-menu .dropdown-item {
  padding: 3px 4px 3px 12px !important;
  border: none !important;
  border-radius: 0 !important;
}

.multiselect-container.dropdown-menu .dropdown-item.active {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
}

/* FIX: Hover state on option rows used Bootstrap 5's much darker
   default (#A9A9A9) instead of DevOps's light #F5F5F5 (verified via
   a real hover on DevOps: background #F5F5F5, text #262626). Excluding
   .active so the selected row's blue doesn't get overridden by hover. */
.multiselect-container.dropdown-menu .dropdown-item:hover:not(.active) {
  background-color: #F5F5F5 !important;
  color: #262626 !important;
}

/* FIX: Rebuilding the search box as a proper joined "input-group"
   matching DevOps exactly, instead of the earlier icon-overlay attempt.
   DevOps's version is a grey icon box (39px, #EEEEEE, bordered) sitting
   flush against a bordered input - two visually separate segments
   joined into one control. The earlier fix used absolute positioning
   to overlay the icon inside a single input; even with a verified gap
   in computed pixels, the icon glyph's own visual ink can extend past
   its box, so it still looked like it touched the text - and it also
   didn't match DevOps's actual joined-box look. Since local's markup
   is already a flex row (icon and input as siblings, not nested), the
   simplest correct approach is to size the icon as its own fixed-width
   box in normal flow (no absolute positioning at all) and let the
   input follow it naturally - eliminates any possibility of overlap. */
.multiselect-filter {
  border: 1px solid #999 !important;
  border-radius: 3px !important;
  overflow: hidden !important;
  align-items: stretch !important;
}

.multiselect-filter .fa-search {
  position: static !important;
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  width: 39px !important;
  flex-shrink: 0 !important;
  background-color: #EEEEEE !important;
  border-right: 1px solid #999 !important;
  margin: 0 !important;
  pointer-events: none;
}

.multiselect-filter input.multiselect-search {
  margin: 0 !important;
  padding-left: 12px !important;
  flex: 1 !important;
  width: auto !important;
  height: 34px !important;
  border: none !important;
  border-radius: 0 !important;
  box-sizing: border-box !important;
}

.multiselect-filter .multiselect-clear-filter {
  flex: 0 0 34px !important;
  width: 34px !important;
  height: 34px !important;
  padding: 0 !important;
  font-size: 22px !important;
  line-height: 1 !important;
  text-decoration: none !important;
}

.multiselect-container.dropdown-menu .form-check-input[type="radio"] {
  border-radius: 50% !important;
}

/* DataTable page-length control: normalize legacy, Bootstrap 5, and
   Responsive markup to "Show [select] entries". */
.dataTables_length,
.dt-container .dt-length {
  display: inline-flex !important;
  align-items: center !important;
  gap: 8px !important;
  white-space: nowrap;
}

/* Legacy DataTables wraps the text and select in one label. */
.dataTables_length > label {
  display: inline-flex !important;
  align-items: center !important;
  gap: 8px !important;
  margin: 0 !important;
  font-weight: normal !important;
}

/* Every grid: "Show" comes from CSS before the page-size select. Do not
   append "Show Records" after the select; those leftover spans are hidden. */
.dt-container .dt-length::before,
.dataTables_length::before {
  content: "Show" !important;
  display: inline !important;
  font-size: 14px;
  font-weight: normal;
  margin-right: 0;
}

.dt-container .dt-length label,
.dataTables_length > label {
  display: inline-flex !important;
  align-items: center !important;
  gap: 8px !important;
  margin: 0 !important;
  padding: 0 !important;
  border: 0 !important;
  background: transparent !important;
  font-size: 0 !important;
  font-weight: normal !important;
}

.dt-container .dt-length label::after,
.dataTables_length > label::after {
  content: "entries";
  font-size: 14px;
  margin-left: 0;
}

.dt-container .dt-length > span,
.dt-container .dt-length label > span,
.dataTables_length > span,
.dataTables_length > label > span,
span.show-records-label,
span.show-records-text {
  display: none !important;
}

.dataTables_length select,
.dt-container .dt-length select {
  box-sizing: border-box !important;
  display: inline-block !important;
  width: auto !important;
  min-width: 64px !important;
  height: 36px !important;
  min-height: 36px !important;
  margin: 0 8px 0 0 !important;
  padding: 0 28px 0 10px !important;
  border: 1px solid #ccc !important;
  border-radius: 3px !important;
  background-color: #fff !important;
  box-shadow: none !important;
  color: #333 !important;
  font-size: 14px !important;
  line-height: 34px !important;
}

/* Length menu and sort icons must not paint before the grid's first
   draw (otherwise a blank page shows only "Show [n] entries" + carets). */
.dt-container:not(.itg-dt-ready),
div.dataTables_wrapper:not(.itg-dt-ready) {
  opacity: 0;
}

.dt-container.itg-dt-ready,
div.dataTables_wrapper.itg-dt-ready {
  opacity: 1;
}

/* Bootstrap 5 gives .table an opaque --bs-table-bg. Tables placed in the
   app's gray .qc_mainPrat cards were transparent under Bootstrap 3, so the
   card background should remain visible through their cells. */
.qc_mainPrat .table {
  --bs-table-bg: transparent;
}

/* Support User Settings log modal: retain the established DevOps information
   modal palette while using Bootstrap 5's modal behavior. */
#view_log_spt_modal .modal-header {
  padding: 10px 24px;
  background-color: #fff;
}

#view_log_spt_modal .modal-title {
  color: #1f7fbd;
  font-size: 18px;
  font-weight: 700;
}

#view_log_spt_modal .modal-header .close {
  margin-left: auto;
  padding: 0;
  border: 0;
  background: transparent;
  color: #1f7fbd;
  font-size: 22px;
  font-weight: 400;
  line-height: 1;
}

#view_log_spt_modal #view_log_spt_tbl thead th {
  --bs-table-bg: #edf6ff;
  background-color: #edf6ff;
  color: #1f7fbd;
  text-align: center;
}

/* The personnel selector's close button used to float inside .filter_list,
   allowing DataTables' generated wrapper to occupy the same hit-test area.
   Keep the header and table body in separate normal-flow rows. */
#myModal .personnel-selector-modal-header {
  min-height: 43px;
  padding: 10px 16px;
  position: relative;
  z-index: 2;
}

#myModal .personnel-selector-modal-header .btn-close {
  margin-left: auto;
}

#myModal .modal-body,
#myModal #example_permission_user_wrapper {
  position: relative;
  z-index: 1;
}

/* FIX: bootstrap-multiselect@2.0.0 renders each option as a Bootstrap 5
   .form-check with a .form-check-input radio/checkbox. Several pages
   (asset-assignment.php among them) still carry legacy page-level rules
   like "input[type=radio] { max-height: 8px }" that squash those inputs
   into broken pill/circle shapes in the open dropdown. Restore normal
   control dimensions inside multiselect menus only. */
.multiselect-container.dropdown-menu .form-check,
.multiselect-container.dropdown-menu .dropdown-item label {
  display: flex !important;
  align-items: center !important;
  gap: 8px !important;
  margin-bottom: 0 !important;
  cursor: pointer !important;
}

.multiselect-container.dropdown-menu .form-check-input {
  width: 1em !important;
  height: 1em !important;
  min-height: 1em !important;
  max-height: none !important;
  margin-top: 0 !important;
  margin-right: 0.5em !important;
  flex-shrink: 0 !important;
  float: none !important;
}

.multiselect-container.dropdown-menu .form-check-label {
  flex: 1 1 auto !important;
}

/* FIX: The Font Awesome build loaded on this page has a bug in its own
   CSS: ".fa-sm { line-height: 0.07143em }" - clearly unintentional
   (should just inherit normal line-height), and it squashes any
   fa-sm-sized icon (e.g. the multiselect search icon) down to about
   1px tall, making it invisible. This is a bug in the third-party
   file itself, not our markup, so correcting the property here. */
.fa-sm {
  line-height: 1 !important;
}

/* FIX: Bootstrap 5's .btn-success uses CSS custom properties defaulting
   to --bs-btn-bg: #198754 (a darker, more saturated green) instead of
   Bootstrap 3's #5cb85c. Overriding the actual properties directly
   (rather than the --bs-* variables) so it wins regardless of how
   Bootstrap's own rule resolves them. Search button uses this class
   once a filter is applied. */
.btn-success {
  color: #fff !important;
  background-color: #5cb85c !important;
  border-color: #4cae4c !important;
}

.btn-success:hover,
.btn-success:focus,
.btn-success:active {
  background-color: #449d44 !important;
  border-color: #398439 !important;
}

/* FIX: This codebase applies Bootstrap 3/4's ".form-control" class to
   plain <select> elements throughout (rather than Bootstrap 5's
   dedicated ".form-select"). Bootstrap 5's ".form-control" rule sets
   "appearance: none" to normalize text-input styling, which also
   strips the native OS dropdown arrow from any select that carries it
   - and unlike ".form-select", ".form-control" pairs no replacement
   chevron background-image, so the arrow just disappears. DevOps's
   Bootstrap 3 selects never had "appearance: none" applied in the
   first place, so restoring the browser's native arrow (rather than
   attempting to recreate Bootstrap 5's SVG chevron) matches DevOps.
   Global because this ".form-control" class-on-select pattern isn't
   scoped to any one page. */
select.form-control {
  appearance: auto !important;
  -webkit-appearance: auto !important;
  -moz-appearance: auto !important;
}

/* FIX: style-new.css uses magic-number body padding-top values for the
   fixed <header>. Those go stale whenever .top_part wraps (logo stack
   or icons-on-next-row), which hides .heading_bold page titles under
   the nav. Migrated pages set --fuse-header-offset from measured
   header height (see sync script in header.php); this is the fallback
   until that runs. Inline padding-top with !important from the script
   wins over style-new.css's later !important rules. */
html body {
  padding-top: var(--fuse-header-offset, 160px) !important;
}

@media (min-width: 1200px) {
  html body {
    padding-top: var(--fuse-header-offset, 140px) !important;
  }
}

/* ================================================================
2. NAVIGATION MENU - DEVOPS DESIGN MATCH
================================================================ */

/* Hide the navigation toggle button - desktop widths only.
   FIX: was the bare selector "nav button", which matches EVERY button
   inside <nav> - including the Reports/Risk & Safety category buttons
   ([class*="report_collapsible"]), silently forcing them to
   display:none via !important and making them completely unclickable.
   Scoped to the actual mobile hamburger toggle only.
   FIX 2: this was hiding the toggle unconditionally (all widths), which
   also killed it at <=991px - Bootstrap's own ".navbar-toggle { display:
   block }" rule at "@media (max-width: 991px)" is what's supposed to
   show it there, since that's the only way to open the nav once the
   horizontal menu list collapses at narrower widths (confirmed: without
   it, the nav becomes completely inaccessible at tablet widths like
   768px, matching DevOps's own hamburger-menu behavior there). Scoping
   the hide to desktop widths only, where the horizontal menu is shown
   directly and the toggle isn't needed. */
@media (min-width: 992px) {
  nav button.navbar-toggle,
  header .navbar-toggle,
  header .navbar-header {
    display: none !important;
    visibility: hidden !important;
  }
}

/* FIX: ".navbar-toggle"/".icon-bar" are Bootstrap 3 class names with no
   equivalent in Bootstrap 5 (which uses ".navbar-toggler" instead), so
   Bootstrap 5's CSS provides zero styling for them - the button rendered
   as a bare, unstyled 14x4px sliver instead of a proper 44x34px bordered
   hamburger icon. DevOps gets this styling for free from Bootstrap 3's
   own CSS (a "float: right" + negative-margin technique that assumes
   ".navbar-header" is a normal block spanning the full nav width).
   Locally ".navbar-header" is a flex item of ".container-fluid" (a
   Bootstrap 5 base style, not present on DevOps's Bootstrap 3 setup)
   and shrinks to fit just the button's own content - float has no room
   to move within it, and flex containers ignore "float" on their
   children entirely anyway. Using "position: absolute" anchored to
   "nav" (already "position: relative") sidesteps that flex/float
   conflict rather than fighting it. */
@media (max-width: 991px) {
  /* FIX: "top: 8px" placed the button relative to <nav>'s own box, which
     starts right where the gray ".medil_part" bar (the "Office -
     Training" row) ENDS - so the button rendered just below/outside
     that gray bar instead of inside it like DevOps. Measured directly
     (via an isolated same-width iframe, since window resize wasn't
     reliably testable): at ~768px, ".medil_part" spans roughly 89-136px
     from the top while <nav> starts at 136px, so an offset of about
     -40px (relative to nav) is needed to center the button vertically
     within that gray bar instead. */
  nav button.navbar-toggle {
    display: block !important;
    position: absolute !important;
    top: -40px !important;
    right: 15px !important;
    width: 44px !important;
    height: 34px !important;
    padding: 9px 10px !important;
    margin: 0 !important;
    border: 1px solid #999 !important;
    background-color: transparent !important;
    border-radius: 3px !important;
    /* FIX: once the menu is toggled open, ".navbar-collapse.collapse"
       below expands with "position: absolute" (inherited, not
       overridden) and no z-index, ending up on top of - and covering -
       this button, so a real click at the button's own screen position
       actually lands on the expanded menu instead, making it impossible
       to toggle closed again. Forcing this above that stacking context. */
    z-index: 1000 !important;
  }

  nav button.navbar-toggle .icon-bar {
    display: block !important;
    width: 22px !important;
    height: 2px !important;
    background-color: #888 !important;
    border-radius: 1px;
  }

  nav button.navbar-toggle .icon-bar + .icon-bar {
    margin-top: 4px !important;
  }
}

/* Navigation container - DevOps design.
   Exclude CRM pipeline's <nav class="horizontal-nav"> — that tab strip
   is display:flex. This reset was collapsing it into a vertical stack
   (FDCM-3547: crm_lead, crm_contact, crm_company, crm_opportunity). */
nav:not(.horizontal-nav) {
  display: block !important;
  height: auto !important;
  min-height: auto !important;
  background-color: transparent !important;
  border-bottom: none !important;
  padding: 0 !important;
  margin: 0 !important;
  width: 100% !important;
}

nav.horizontal-nav {
  display: flex !important;
  flex-direction: row !important;
  flex-wrap: nowrap !important;
  align-items: center !important;
  justify-content: space-between !important;
  height: auto !important;
  min-height: auto !important;
  width: 100% !important;
  max-width: 100% !important;
  background-color: #ffffff !important;
  border-bottom: 1px solid #e5e7eb !important;
  padding: 0 !important;
  margin: 0 0 20px 0 !important;
  overflow-x: auto !important;
  overflow-y: hidden !important;
  gap: 4px !important;
}

/* Main navigation list - inline-block horizontal layout (DevOps style).
   Exclude .fuse-module-navbar — that bar stays a single row (style-new.css + header.php). */
nav:not(.fuse-module-navbar) ul.nav.navbar-nav {
  display: inline-block !important;
  width: 100% !important;
  height: auto !important;
  padding: 0 !important;
  margin: 0 !important;
  list-style: none !important;
  background-color: transparent !important;
  white-space: nowrap !important;
}

/* Module bar: single horizontal row from 1220px up when items fit. */
@media (min-width: 1220px) {
header nav.fuse-module-navbar:not(.fuse-nav-collapsed) ul.nav.navbar-nav,
header nav.fuse-module-navbar:not(.fuse-nav-collapsed) ul.nav.navbar-nav.Navagation {
  display: flex !important;
  flex-direction: row !important;
  flex-wrap: nowrap !important;
  align-items: center !important;
  width: 100% !important;
  max-width: 100% !important;
  min-width: 0 !important;
  white-space: nowrap !important;
  height: auto !important;
}

header nav.fuse-module-navbar:not(.fuse-nav-collapsed) ul.nav.navbar-nav > li,
header nav.fuse-module-navbar:not(.fuse-nav-collapsed) ul.nav.navbar-nav.Navagation > li {
  display: block !important;
  flex: 0 0 auto !important;
  width: auto !important;
  float: none !important;
}
}

/* Top-level menu items */
nav ul.nav.navbar-nav > li {
  display: inline-block !important;
  float: none !important;
  padding: 0 !important;
  margin: 0 !important;
  border-right: none !important;
  height: auto !important;
  line-height: normal !important;
  vertical-align: top !important;
  position: relative !important;
}

nav ul.nav.navbar-nav > li:last-child {
  border-right: none !important;
}

/* Raise the hovered/open module so its dropdown covers later items (Settings) */
header nav.fuse-module-navbar ul.nav.navbar-nav > li:hover,
header nav.fuse-module-navbar ul.nav.navbar-nav > li:focus-within,
header nav.fuse-module-navbar ul.nav.navbar-nav.Navagation > li:hover,
header nav.fuse-module-navbar ul.nav.navbar-nav.Navagation > li:focus-within,
header nav.fuse-module-navbar ul.nav.navbar-nav > li:has(> .panel-collapse.show),
header nav.fuse-module-navbar ul.nav.navbar-nav > li:has(> .panel-collapse.in),
header nav.fuse-module-navbar ul.nav.navbar-nav.Navagation > li:has(> .panel-collapse.show),
header nav.fuse-module-navbar ul.nav.navbar-nav.Navagation > li:has(> .panel-collapse.in) {
  z-index: 3000 !important;
}

/* Top-level links - DevOps design with gray text */
nav ul.nav.navbar-nav > li > a {
  display: block !important;
  padding: 4px 15px !important;
  color: rgb(119, 119, 119) !important;
  text-decoration: none !important;
  font-size: 14px !important;
  white-space: nowrap !important;
  margin: 0 !important;
  line-height: 21px !important;
  height: auto !important;
  float: none !important;
  border: none !important;
  background-color: transparent !important;
  cursor: pointer !important;
}

/* Fuse360 blue module bar: white links (overrides gray "white navbar" rules above).
   Match both .fuse-module-navbar and header .navbar-default — staging/menu.php
   sometimes ships without the fuse-module-navbar class, and the gray rule
   above is more specific than carbon-theme's white-link selectors, which
   left Personnel/Work Order/etc. gray-on-blue (crm_lead.php). */
header nav.navbar-default ul.nav.navbar-nav > li > a,
header .navbar.navbar-default ul.nav.navbar-nav.Navagation > li > a,
header nav.fuse-module-navbar ul.nav.navbar-nav > li > a,
header .navbar.fuse-module-navbar ul.nav.navbar-nav.Navagation > li > a {
  color: #ffffff !important;
  background-color: transparent !important;
  border: none !important;
  font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif !important;
  font-weight: 500 !important;
  line-height: 1.2 !important;
  padding: 10px var(--fuse-module-nav-pad-x, 5px) !important;
  font-size: var(--fuse-module-nav-font-size, 13px) !important;
  letter-spacing: 0 !important;
}

/* FIX: at 1366px and narrower, the full 14px/15px spacing makes the menu
   row wider than the viewport and forces a wrap onto a second line
   (which brought its own set of alignment/overlap issues). Shrinking
   font-size and padding here keeps every item on a single row instead,
   avoiding wrapping entirely at this width. Wider screens are untouched
   and keep the default 14px/15px spacing above. */
@media (min-width: 1101px) and (max-width: 1366px) {
  nav:not(.fuse-module-navbar) ul.nav.navbar-nav > li > a {
    font-size: 12px !important;
    padding: 4px 5px !important;
  }
}

/* FIX: DevOps's hover state keeps the white background, turns the text
   blue (#2296F3, the site's accent color) with no transition delay, and
   adds a thin 1px light-gray (#c9c9c9) vertical border on both sides of
   the hovered item - a subtle divider outlining just that item. Local
   was using a leftover gray-tint background (rgba(0,0,0,.05)) and a
   darker gray text color with no border at all - a plausible generic
   "hover" look, but not what DevOps actually does here. */
nav ul.nav.navbar-nav > li > a:hover {
  background-color: #ffffff !important;
  color: rgb(34, 150, 243) !important;
  border-left: 1px solid #c9c9c9 !important;
  border-right: 1px solid #c9c9c9 !important;
}

header nav.navbar-default ul.nav.navbar-nav > li > a:hover,
header .navbar.navbar-default ul.nav.navbar-nav.Navagation > li > a:hover,
header nav.fuse-module-navbar ul.nav.navbar-nav > li > a:hover,
header .navbar.fuse-module-navbar ul.nav.navbar-nav.Navagation > li > a:hover {
  background-color: var(--cds-button-primary-hover, #0043ce) !important;
  color: #ffffff !important;
  border-left: none !important;
  border-right: none !important;
}

/* FIX [FDCM-3547]: the top-level link rule above ("nav ul.nav.navbar-nav >
   li > a") sets "color: rgb(119,119,119) !important" for every top-level
   item so it wins the cascade against Bootstrap 5's own link color -
   but !important always beats a non-important declaration regardless of
   selector specificity, so it was also flattening style-new.css's
   ".navbar-default .navbar-nav>li.active a" (color:#2296f3, no
   !important) on the one top-level item that ships with class="active"
   in menu.php - the "Settings" tab, which DevOps always renders as a
   permanently blue/highlighted item (not a "current page" indicator).
   Restoring that active look here with matching !important so it wins,
   scoped to just the active item so every other top-level link keeps
   the gray fix above untouched. */
nav ul.nav.navbar-nav > li.active > a,
nav ul.nav.navbar-nav > li.active > a:hover {
  color: rgb(34, 150, 243) !important;
  background-color: #ffffff !important;
  border-left: 1px solid #c9c9c9 !important;
  border-right: 1px solid #c9c9c9 !important;
}

header nav.navbar-default ul.nav.navbar-nav > li.active > a,
header nav.navbar-default ul.nav.navbar-nav > li.active > a:hover,
header .navbar.navbar-default ul.nav.navbar-nav.Navagation > li.active > a,
header .navbar.navbar-default ul.nav.navbar-nav.Navagation > li.active > a:hover,
header .navbar.navbar-default ul.nav.navbar-nav.Navagation > li > a.active,
header nav.fuse-module-navbar ul.nav.navbar-nav > li.active > a,
header nav.fuse-module-navbar ul.nav.navbar-nav > li.active > a:hover,
header .navbar.fuse-module-navbar ul.nav.navbar-nav.Navagation > li.active > a,
header .navbar.fuse-module-navbar ul.nav.navbar-nav.Navagation > li.active > a:hover,
header nav.fuse-module-navbar ul.nav.navbar-nav > li > a.active,
header .navbar.fuse-module-navbar ul.nav.navbar-nav.Navagation > li > a.active {
  color: #ffffff !important;
  background-color: var(--cds-button-primary-hover, #0043ce) !important;
  border-left: none !important;
  border-right: none !important;
}

/* Submenu styling - shown on hover (dropdown positioned under parent) */
nav ul.nav.navbar-nav > li > ul {
  display: none !important;
  position: absolute !important;
  top: 100% !important;
  left: 0 !important;
  background-color: #ffffff !important;
  border: 1px solid #ddd !important;
  border-top: none !important;
  list-style: none !important;
  padding: 0 !important;
  margin: 0 !important;
  z-index: 1000 !important;
  min-width: 180px !important;
  height: auto !important;
  max-height: none !important;
  min-height: auto !important;
}

nav ul.nav.navbar-nav > li:hover > ul {
  display: block !important;
}

/* ===== REPORTS-STYLE ACCORDION MENUS - DEVOPS DESIGN MATCH =====
   Covers Reports, Risk & Safety, and any future menu built the same
   way. Rewritten to use generic selectors matched by partial class
   name / shared class (e.g. [class*="report_menu_content"],
   .two-column-items) instead of being hardcoded to ":nth-child(7)".
   DevOps itself names these classes per-instance with a numeric
   suffix (report_menu_content_32, report_collapsible_58, etc.) - a
   selector tied to one nth-child position breaks the moment the
   suffix changes or a second instance (Risk & Safety) is added.

   This also drops the old display:none/grid "hide unless .report_active"
   trick. DevOps's real mechanism is simpler: the container is always
   display:grid, collapsed via max-height:0/overflow:hidden, and JS
   expands it by setting an inline max-height on click. So max-height/
   overflow here are intentionally NOT !important - an inline style set
   by JS (even without !important) still needs to be able to override
   them to expand the panel. Using !important there would permanently
   lock every category shut regardless of what the click handler does. */

/* Collapsible container - collapsed by default via max-height */
nav .left_bar [class*="report_menu_content"] {
  padding: 0 18px;
  max-height: 0;
  overflow: hidden;
  transition: max-height 0.2s ease-out;
  background-color: #f1f1f1;
}

/* 2-column grid layout for report items */
nav .left_bar .two-column-items {
  display: grid;
  grid-template-columns: repeat(2, minmax(180px, 1fr));
  gap: 8px 15px;
}

/* Report item links - card style.
   Specificity (nav + .left_bar + .two-column-items + a = 2 classes)
   intentionally beats style-new.css's generic ".left_bar ul li a"
   rule (1 class + 3 types) without needing !important - classes are
   weighted before type count in CSS specificity, so no arms race here.
   Hover background/arrow and hover color come for free from that same
   site-wide style-new.css (.left_bar ul li a:hover, and
   .Navagation > li .left_bar li a:hover) - not redeclared. */
nav .left_bar .two-column-items a {
  padding: 7px;
  background-color: #F7F7F7;
  border-radius: 4px;
  color: #555555;
  font-size: 15px;
  word-wrap: break-word;
}

/* Category buttons — ATS primary var(--cds-interactive, #0f62fe) */
nav .left_bar [class*="report_collapsible"] {
  display: block;
  width: 100%;
  padding: 18px;
  font-size: 15px;
  font-weight: normal;
  background-color: var(--cds-interactive, #0f62fe);
  color: #fff;
  border: none;
  border-radius: 3px;
  cursor: pointer;
  text-align: left;
  box-sizing: border-box;
}

/* "report_active" itself is NOT suffixed on DevOps (confirmed: same
   class name reused across every instance), only "report_collapsible"
   is - so this one rule covers the active state for every instance. */
nav .left_bar [class*="report_collapsible"].report_active,
nav .left_bar [class*="report_collapsible"]:hover {
  background-color: var(--cds-button-primary-hover, #0043ce);
}

/* +/- expand indicator */
nav .left_bar [class*="report_collapsible"]::after {
  content: "+";
  color: #fff;
  font-weight: bold;
  float: right;
  margin-left: 5px;
}

nav .left_bar [class*="report_collapsible"].report_active::after {
  content: "\2212";
}

/* Search input inside these menus */
nav .left_bar input[type="text"].form-control {
  display: block;
  width: 100%;
  max-width: 536px;
  margin: 1px 0 5px 0;
  padding: 6px 12px;
  font-size: 14px;
  border: 1px solid #ccc;
  border-radius: 3px;
  background-color: #fff;
  box-sizing: border-box;
}

/* ================================================================
FIX: Dropdown overflow - long item text was breaking out of its
container because "white-space: nowrap" on nav ul.nav.navbar-nav
(needed for the horizontal top-level menu) was inheriting down into
every nested dropdown (e.g. Expense > .left_bar > .menu-sub items).
Reset it here so long labels wrap inside their column instead.
================================================================ */
nav ul.nav.navbar-nav .left_bar,
nav ul.nav.navbar-nav .menu-sub {
  white-space: normal !important;
}

nav ul.nav.navbar-nav .left_bar li,
nav ul.nav.navbar-nav .left_bar li a,
nav ul.nav.navbar-nav .menu-sub li,
nav ul.nav.navbar-nav .menu-sub li a {
  white-space: normal !important;
  word-wrap: break-word !important;
  overflow-wrap: break-word !important;
}

/* Constrain the per-item dropdown container width to match DevOps design
   and prevent it from ever exceeding its intended size */
nav ul.nav.navbar-nav > li > div.panel-collapse {
  max-width: 540px !important;
  box-sizing: border-box !important;
}

nav ul.nav.navbar-nav > li > div.panel-collapse .left_bar {
  max-width: 536px !important;
  box-sizing: border-box !important;
}

/* Other submenu styling */
nav ul.nav.navbar-nav > li:not(:nth-child(7)) > ul > li {
  display: block !important;
  padding: 0 !important;
  margin: 0 !important;
  width: 100% !important;
  border-bottom: 1px solid #f0f0f0 !important;
  height: auto !important;
  max-height: none !important;
}

nav ul.nav.navbar-nav > li:not(:nth-child(7)) > ul > li:last-child {
  border-bottom: none !important;
}

nav ul.nav.navbar-nav > li:not(:nth-child(7)) > ul > li > a {
  display: block !important;
  padding: 8px 15px !important;
  color: #333 !important;
  font-size: 13px !important;
  white-space: nowrap !important;
  line-height: 20px !important;
  text-decoration: none !important;
  border: none !important;
  background-color: transparent !important;
  height: auto !important;
}

nav ul.nav.navbar-nav > li:not(:nth-child(7)) > ul > li > a:hover {
  background-color: #f5f5f5 !important;
}

/* Nested submenus for multi-level menus (Risk & Safety submenu items) */
nav ul.nav.navbar-nav > li > ul > li > ul {
  display: none !important;
  position: absolute !important;
  top: 0 !important;
  left: 100% !important;
  background-color: #ffffff !important;
  border: 1px solid #ddd !important;
  list-style: none !important;
  padding: 0 !important;
  margin: 0 !important;
  z-index: 1001 !important;
  min-width: 180px !important;
  height: auto !important;
  max-height: none !important;
}

nav ul.nav.navbar-nav > li > ul > li:hover > ul {
  display: block !important;
}

nav ul.nav.navbar-nav > li > ul > li > ul > li {
  display: block !important;
  padding: 0 !important;
  margin: 0 !important;
  width: 100% !important;
  border-bottom: 1px solid #f0f0f0 !important;
  height: auto !important;
}

nav ul.nav.navbar-nav > li > ul > li > ul > li:last-child {
  border-bottom: none !important;
}

nav ul.nav.navbar-nav > li > ul > li > ul > li > a {
  display: block !important;
  padding: 8px 15px !important;
  color: #333 !important;
  font-size: 13px !important;
  white-space: nowrap !important;
  line-height: 20px !important;
  text-decoration: none !important;
  border: none !important;
  background-color: transparent !important;
  height: auto !important;
}

nav ul.nav.navbar-nav > li > ul > li > ul > li > a:hover {
  background-color: #f5f5f5 !important;
}

/* Hide textboxes by default - but NOT in Reports submenu */
nav input[type="hidden"] {
  display: none !important;
}

nav > ul input[type="text"] {
  display: none !important;
}

/* CRITICAL: Override responsive media query to keep nav horizontal */
@media (max-width: 768px) {
  nav ul.nav.navbar-nav {
    display: inline-block !important;
  }

  nav ul.nav.navbar-nav > li {
    display: inline-block !important;
    border-right: none !important;
    border-bottom: none !important;
  }
}

/* ================================================================
CRITICAL OVERRIDE: Fix navbar-collapse display after Bootstrap 5 upgrade
This must come after all media queries to ensure it applies correctly
DevOps Design: Use inline-block instead of flex
================================================================ */

/* FIX: these ".navbar-collapse" rules were unconditional (all widths),
   forcing "display: inline-block !important" regardless of screen size.
   That's correct for desktop, where the menu should always be visible,
   but at <=991px it fights the mobile hamburger-toggle mechanism: the
   toggle button's own click handler (see header_local.php) does
   "$('#myNavbar').toggle()", which sets an inline "display: block" -
   but our own unconditional !important rule (and a separate, unrelated
   "@media (max-width: 991px) { .navbar-collapse.collapse { display:
   none !important } }" rule matching Bootstrap 3's default collapsed-
   by-default behavior) both out-rank a plain inline style, so the menu
   never actually appeared when toggled open. Scoping all of these to
   desktop widths only so the mobile collapse/expand behavior can work
   as intended below that. */
@media (min-width: 992px) {
  .navbar-collapse {
    display: inline-block !important;
    width: 100% !important;
    height: auto !important;
    max-height: none !important;
    /* FIX: was position:absolute (inherited from Bootstrap's mobile
       collapse behavior), which floated the entire menu row ~15px
       above the nav bar's actual box. That mismatch pushed every
       per-item dropdown up so it started overlapping the nav bar
       instead of sitting flush below it. Forcing normal flow here
       realigns the menu row with nav's real edges. */
    position: relative !important;
    top: 0 !important;
  }

  .navbar-collapse.collapse {
    display: inline-block !important;
    width: 100% !important;
    height: auto !important;
    max-height: none !important;
  }

  .navbar-collapse.collapse.show,
  .navbar-collapse.collapse.in {
    display: inline-block !important;
    width: 100% !important;
    height: auto !important;
    max-height: none !important;
  }

  .navbar-default .navbar-collapse {
    display: inline-block !important;
    width: 100% !important;
    height: auto !important;
    max-height: none !important;
  }

  nav:not(.fuse-module-navbar) .navbar-nav {
    display: inline-block !important;
    width: 100% !important;
    white-space: nowrap !important;
    height: auto !important;
    max-height: none !important;
  }
}

/* FIX: at <=991px, Bootstrap 5 Collapse toggles .show (and we mirror
   Bootstrap 3's .in). Also honor a leftover inline display:block from
   the old jQuery .toggle() handler. */
@media (max-width: 991px) {
  .navbar-collapse.collapse.show,
  .navbar-collapse.collapse.in,
  .navbar-collapse.collapse[style*="display: block"] {
    display: block !important;
    width: 100% !important;
    position: static !important;
    z-index: auto !important;
  }

  .navbar-collapse.collapse.show ul.navbar-nav,
  .navbar-collapse.collapse.in ul.navbar-nav,
  .navbar-collapse.collapse[style*="display: block"] ul.navbar-nav {
    display: block !important;
    width: 100% !important;
    white-space: normal !important;
  }

  .navbar-collapse.collapse.show ul.navbar-nav > li,
  .navbar-collapse.collapse.in ul.navbar-nav > li,
  .navbar-collapse.collapse[style*="display: block"] ul.navbar-nav > li {
    display: block !important;
    float: none !important;
    width: 100% !important;
    text-align: center;
    border-bottom: 1px solid #eee !important;
  }
}

/* FIX: style-new.css has "@media (max-width: 767px) { #collapse_Top11 {
   left: 50%; margin-left: -140px; } }" (plus a near-duplicate "left: 51%;
   position: relative;" rule) - a rough, never-quite-right attempt at
   positioning the category submenu on mobile. Every submenu shares this
   same id (a pre-existing markup issue, not something fixable from
   here), so this single rule shifts ALL of them by the same fixed
   offset regardless of which menu item they belong to or how wide it
   is - landing well off to the side instead of under the actual
   clicked item (verified: this misalignment happens independently of
   the separate JS click-handler bug, which also sets its own wrong
   "left: 50%" inline style on click).
   The correct approach for a mobile accordion menu is to not position
   the submenu at all - just let it flow as a normal block directly
   after its parent <li> in the stacked list, so it's automatically
   flush underneath and full-width no matter which item opened it. */
@media (max-width: 991px) {
  nav ul.nav.navbar-nav > li > div.panel-collapse {
    position: static !important;
    left: auto !important;
    top: auto !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
    width: 100% !important;
    max-width: 100% !important;
  }

  nav ul.nav.navbar-nav > li > div.panel-collapse .left_bar {
    max-width: 100% !important;
  }
}

/* ================================================================
4. DATATABLE - DEVOPS DESIGN MATCH
================================================================ */

/* FIX: The attendance DataTable's header row (#example8 thead) renders
   at 36px locally vs DevOps's 55px. Font-size, color, and padding on
   the header cells all already matched exactly (14px/700/#212121/
   "0px 5px") on both sites, and no stylesheet rule (local or DevOps,
   where accessible) explicitly sets a height - this is DataTables'
   own runtime row-height calculation resolving differently, not a
   static CSS mismatch. Forcing the row height directly here to match
   the verified DevOps value. */
/* FIX: style-new.css has a sitewide ".form-control { width: 97% !important; }"
   rule (not editable here). It overrode the DataTables Bootstrap5 adapter's
   own ".dt-search input { width: auto; }" rule regardless of specificity
   (an !important always beats a non-important declaration), stretching the
   table's search box to the table's full width instead of DevOps's compact
   ~160px box. Matching !important on a more specific selector to win here. */
#example8_wrapper .dt-search input {
  width: auto !important;
}

/* FIX: At the "@media (min-width: 1600px)" breakpoint, style-new.css sets
   BOTH "max-width: 1594px !important" AND "width: 1594px !important" on
   .big-table, so it renders correctly. But its "@media (min-width: 1366px)"
   breakpoint only sets "margin: 0 auto; max-width: 1350px;" - no explicit
   width, and no !important. With no width declared, the box's used width
   collapses to a tiny content-shrunk ~118px instead of filling the
   available ~1350px (this only shows up combined with .big-table's own
   "overflow-x: auto", which is otherwise needed so a too-wide table can
   scroll instead of blowing out the page). At 1366-1599px viewports this
   pushed the whole page content into a ~118px sliver flush against the
   right edge - every dropdown, the legend, and the DataTable all crammed
   into it. Restoring an explicit width here the same way the 1600px
   breakpoint already does fixes it. */
@media (min-width: 1366px) {
  /* FIX: style-new.css's base ".Middle" rule (unconditional, not in any
     media query) sets "float: left". A floated box can't be centered with
     "margin: auto" - per the CSS spec, auto margins on a float always
     resolve to 0, not to the space needed to center it - so the
     margin-left/right: auto below was silently doing nothing and this
     1140px-capped box just hugged the left edge of its (wider) parent
     ".container" instead of sitting in the middle, e.g. on
     personnel/attendance.php where DevOps's page shows the Search/Clear
     Selection/Active/Inactive buttons and filter dropdowns centered.
     Un-floating it here (still scoped to this breakpoint, where the width
     cap applies) is what lets the auto margins actually center it.

     MUST stay scoped to attendance.php. An unscoped ".Middle { width:
     1140px }" also matches every other module page's content card
     (recruiting, work order, HR, ONB, …) and is the Bootstrap 5
     "narrower card" regression: DevOps's ".Middle" is float:left;
     width:100% of a full-width container. */ 
  body:has(.big-table.attendance-page) .container > .Middle:not(.payrl) {
    float: none !important;
    width: 1140px !important;
    max-width: 1140px !important;
    margin-left: auto !important;
    margin-right: auto !important;
  }

  /* Pages that already opt into a full-bleed wrapper (inline min-width:100%
     / width:100% on .container, the ONB recruiting pattern) must keep
     ".Middle" at 100%. Bootstrap 5's .container max-width does not cap
     those wrappers (min-width wins), so the content card should fill them. */
  .container[style*="min-width"] > .Middle,
  .container[style*="width:100%"] > .Middle,
  .container[style*="width: 100%"] > .Middle {
    float: left !important;
    width: 100% !important;
    max-width: none !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  .big-table.attendance-page {
    width: 1350px !important;
    max-width: 1350px !important;
    margin-left: auto !important;
    margin-right: auto !important;
  }

  /* FIX: the bare ".Middle" selector above (written for attendance.php's
     filter panel) also matches personnel/pto-request-que.php's own,
     unrelated "<div class="Middle payrl bonus-category">" - same class
     name, different page. Forcing it to a fixed 1140px and unfloating it
     blows the whole filter panel out past its actual 432px-wide
     ".col-sm-4" column (the office/employee/supervisor/custom-group
     selects and the Start/End Date table all inherit that 1140px width
     from their ".Middle" ancestor). Restoring this page's own float and
     100% (of its real 432px column, not attendance.php's 1366px-viewport
     assumption) undoes that. Scoped via :has(#framework_ofc) since the
     wrapper has no page-specific class of its own. */
  .container:has(#framework_ofc) .Middle {
    float: left !important;
    width: 100% !important;
    max-width: 100% !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  /* FIX: the exact same "Middle payrl bonus-category" class string (no
     "text-center") is reused - copy/pasted wrapper markup, not a
     component - on dozens of other pages sitewide (e.g.
     personnel/field-training-input.php), all unrelated to attendance.php.
     On field-training-input.php this capped its ".qc_mainPrat" ADD ROW
     table's grey background at 1140px while the (table-layout:auto,
     many-column) <table> inside kept its natural ~1350px content width,
     so the table visibly overflowed past the right edge of its own grey
     background; the same cap also squeezed the #example DataTable's
     wrapper narrower than its ~1540px content, forcing a horizontal
     scrollbar DevOps's (uncapped, full-width) version never needs.
     attendance.php never uses this exact 3-class combo without also
     adding ".text-center", so excluding it here is safe. */
  .Middle.payrl.bonus-category:not(.text-center),
  .Middle.doc {
    float: left !important;
    width: 100% !important;
    max-width: 100% !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  /* FIX: hr/general-notice.php's form fields sit in a bare "<div class="Middle ">"
     (no other class) - the exact shape the first, unscoped ".Middle" rule
     above (added for attendance.php's filter panel) matches. That capped
     it at 1140px and centered it, so its ".qc_mainPrat col-sm-8" form
     column (66.67% of 1140, not of the page) hugged the left edge with
     only ~113px of margin, while the true Bootstrap-3 design (style-
     new.css's base ".Middle" is float:left; width:100%, i.e. the full
     width of its ".col-md-12" parent) put ~113px on the left and left the
     remaining ~493px of dead space stacking on the right. Scoped via
     :has(#notice_title) - the Notice Title input's id, unique to this
     page - so attendance.php and the other pages already carved out
     above keep their own widths.
     (This page's Recurring/Onetime Notice DataTables further down live in
     their own separate "<div class="Middle payrl bonus-category">" wrappers,
     not this one - those already get float:left/width:100% for free from
     the ".Middle.payrl.bonus-category:not(.text-center)" rule above, so
     they needed no extra rule here.) */
  .Middle:has(#notice_title) {
    float: left !important;
    width: 100% !important;
    max-width: 100% !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  /* FIX: hr/issue-corrective-action.php's form wrapper is
     "<div class="Middle payrl">" - "payrl" alone (no "bonus-category"),
     so it doesn't match the ".Middle.payrl.bonus-category:not(.text-
     center)" carve-out above either, and falls into the same bare
     ".Middle" 1140px trap as general-notice.php did: its own
     ".col-sm-8.col-sm-offset-2" form column then rendered at 66.67% of
     the 1140px cap instead of 66.67% of the real (wider) ".container",
     leaving a large dead gap on the right - exactly matching the
     reported "narrower box" screenshot. Scoped via :has(#ActionType) -
     the Corrective Action type select's id, unique to this page. */
  .Middle:has(#ActionType) {
    float: left !important;
    width: 100% !important;
    max-width: 100% !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  /* FIX: the ".Middle" rule above only widens ".Middle" to 100% of ITS
     OWN parent - but that parent is "<div class="container rtd"
     style="width:100%;">", and the inline "width:100%" only overrides
     the "width" property, not Bootstrap 5's own ".container" max-width
     (1140px at this 1366px viewport's breakpoint - BS5's "xl" tier,
     1200-1399px). So ".container" itself was still capped to 1140px
     regardless of the ".Middle" fix, and every descendant (".Middle",
     ".qc_mainPrat", the "col-sm-8" field column, down to the "#ActionType"
     select itself) inherited that narrower width - this is the actual
     remaining cause of the reported "narrower box" screenshot, verified
     directly against DevOps's own computed styles for this page: DevOps's
     ".container" resolves to "max-width: none" (effectively full viewport
     width, ~1351px here) at every width, not just below some breakpoint.
     Restoring that here, scoped the same way as the ".Middle" fix above
     (":has(#ActionType)", same page). */
  .container.rtd:has(#ActionType) {
    max-width: none !important;
  }
}

/* FIX: Same "Bootstrap 5 dropped the default float:left on .col-*"
   regression already fixed above for ".work-type-s" and ".qc_mainPrat"
   (see those blocks for the full mechanism), now on hr/general-notice.php's
   own label/field row wrapper, ".gen" (not ".row" either - same missing-
   gutter consequence). Every "<div class="gen"><div class="col-sm-3">
   label</div><div class="col-sm-8">field</div></div>" row (Select Notice
   Type, Title, Message, Office, Position Title, Department, Personnel,
   etc.) stacked the label above the field instead of beside it, and with
   no gutter the two columns also had no gap once floated. ":not(:only-
   child)" excludes this page's few single-column ".gen" rows (e.g. the
   Enabled/Disabled radios, centered via ".col-sm-offset-3" with nothing
   beside them) - those already render correctly and floating their one
   child could collapse ".gen"'s height instead. ".gen" is reused by ~40
   other pages sitewide with their own row shapes, so this is scoped via
   :has(#notice_title) (see the ".Middle" fix above - same wrapper, the
   form-fields one, not the DataTable ones) rather than promoted global.

   Widened from a direct-child ("> [class*=...]") to a plain descendant
   selector [FDCM-3547 follow-up]: several of this page's field columns
   nest a *second* level of ".col-sm-*" columns inside their own (already-
   floated-by-this-rule) ".col-sm-8"/".col-sm-9" field column - e.g. Enable
   Response's Text/Yes-No/Multiple-Choice checkboxes+label, Recurring's
   checkbox+Every+Day trio, and One Time Notice's checkbox+"Date To
   Send"+date+time boxes. The direct-child version left that inner level
   unfloated, so those inner columns fell back to plain block stacking.
   That alone would just stack them (label above field, same as the outer
   level before this rule), but several of those inner "checkbox" columns
   (".control--checkbox" wrapping only a zero-width hidden input, styled
   via a ".control__indicator" that's "position: absolute" *relative to
   the checkbox's own label*, not the column) render with zero content
   height. An unfloated zero-height block doesn't push its next sibling
   down, so that next column (e.g. "Date To Send") started at the exact
   same box the checkbox column did - and the absolutely-positioned
   checkbox square then drew directly on top of that sibling's leading
   text (visually clipping "Date To Send" to "e To Send", "Every" to
   "Evdry", etc). Floating both levels (a floated box always reserves its
   own horizontal space for the next float, zero-height or not) fixes the
   inner columns the same way the outer ones already were. Verified live
   against this exact page/markup - fixed the checkbox/label collisions at
   both the reported viewport width and narrower ones, with no change to
   any row that was already correct. ":not(:only-child)" still excludes
   lone single-column rows at either nesting level. */
.Middle:has(#notice_title) .gen [class*="col-sm-"]:not(:only-child) {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* FIX: same "Bootstrap 5 dropped float:left on .col-*" regression as
   above, on hr/issue-corrective-action.php's ".gen" label/field rows
   (Corrective Action, Problem, Office, Employee, etc. all stacked their
   label above the field). Unlike general-notice.php this page also
   nests a second level of ".col-sm-*" columns one level deeper - e.g.
   Scheduled For's date + time boxes, and Suspension Required's Start
   Date/End Date pair - all inside a ".gen"'s own (already-floated by
   the rule above) ".col-sm-8"/".col-sm-6" field column, with no ".row"
   wrapper of their own either, so they need the same float restored.
   Using a plain descendant selector (not "> ") scoped to ".qc_mainPrat"
   covers both nesting levels in one rule. ":not(:only-child)" excludes
   the single-box rows (Incident Date's lone date field, the plain
   checkbox rows) where there is nothing to float beside and forcing a
   float could collapse the parent's height instead; a floated element
   always establishes its own block formatting context, so a floated
   two-level parent (e.g. ".col-sm-6" wrapping Start/End Date) still
   correctly contains its own floated children's height. Scoped via
   :has(#ActionType) (see the ".Middle" fix above - same wrapper) since
   ".gen" and ".qc_mainPrat" are both reused sitewide. */
.Middle:has(#ActionType) .qc_mainPrat [class*="col-sm-"]:not(:only-child) {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* FIX: the two float-based fixes just above never actually took effect
   for this page's row-level "col-sm-4"/"col-sm-8" pairs (Corrective
   Action, Problem, Office, Employee, Notify Supervisor, Alternative
   Supervisor, etc.) - confirmed live: their label kept rendering on its
   own line above a full-width-looking field instead of beside it, and
   the whole box was still narrower than DevOps even after the two fixes
   above and the ".container" max-width fix further above. Root cause is
   a later, unscoped rule further down this same file (search
   ".gen.mtb10 { display: flex; ... }", added for QC Categories Config's
   ".col-sm-3"+".col-sm-8" row pairing): it also matches this page's
   ".gen.mtb10" rows, and "float" has NO effect on a direct flex item
   regardless of what the rules above set it to - so every ".gen.mtb10"
   row on this page silently became a flex row despite the float fixes.
   Worse, that same rule forces any "col-sm-8" inside a ".gen.mtb10" to
   exactly 75% width (correct for QC Categories Config's 25%-label
   pairing, not this page's 33.33%-label one) - 33.33% + 75% = 108.33%,
   over 100%, so "flex-wrap: wrap" (also set by that rule) pushed the
   field onto its own line below the label on every single row, not just
   the ones already called out above.
   Reverting ".gen.mtb10" back to a plain block here restores the float-
   based model the two fixes above already assume (".gen" itself is
   "float: left; width: 100%" per style-new.css, which is what lets a
   floated child actually get contained/centered correctly). The forced
   "flex: 0 0 75%"/"max-width: 75%" on "col-sm-8" becomes inert once its
   parent isn't flex - Bootstrap 5's own native "width: 66.6667%" for
   ".col-sm-8" (untouched, vendored bootstrap.min.css) takes over again,
   and 75% > 66.6667% means that leftover max-width never actually
   clamps anything, so no separate override is needed for it here.
   Scoped via :has(#ActionType), same as every other fix for this page. */
.Middle:has(#ActionType) .gen.mtb10 {
  display: block !important;
}

/* FIX: ".form-inline .form-control { width: auto !important; }" (further
   down this file, restoring Bootstrap 3's own ".form-inline" behavior for
   compact filter-bar-style forms elsewhere on the site) also matches this
   page's Incident Date / Scheduled For / Suspension Required Start+End
   Date inputs - they reuse "<div class="form-inline"><div class="form-
   group"><input ...></div></div>" purely as this page's generic date-
   field wrapper, not as an actual compact auto-sized inline form. With
   "width: auto", the browser falls back to a plain text input's default
   intrinsic width (~156px here) instead of DevOps's own sizing for this
   exact markup - verified directly: DevOps's Bootstrap 3 build has no
   ".form-inline .form-control" rule at all for this input, so it's sized
   by style-new.css's sitewide ".form-control { width: 97% !important; }"
   (of its real, narrow "col-sm-3" column), floored at ".calendar {
   min-width: 110px; }" when 97% would be even narrower - never by
   intrinsic auto-sizing. On Incident Date/Scheduled For (each the lone
   date field in its row) the oversized 156px box is merely wider than
   DevOps's; on Suspension Required, where Start Date and End Date share
   one row, the extra width pushes the input past its own column and
   over the "End Date" label beside it. Restoring the normal (non-auto)
   width here for all of this page's date/time inputs matches DevOps's
   own uniform sizing. Scoped via :has(#ActionType). */
.Middle:has(#ActionType) .form-inline .form-control {
  display: block !important;
  width: 97% !important;
}

/* FIX: same "Bootstrap 5 dropped float:left on .col-*" regression as
   above, on hr/pan-management-loc.php's PAN filter bar (New PAN / Start
   Date / End Date / Pan Type / Pan Status / Office / Supervisor /
   Personnel / Approving User / Filter / Clear). The markup nests every
   ".col-sm-*" two levels deep inside a plain "<div class="col-m-12">" -
   "col-m-12" isn't a real Bootstrap class (typo for "col-md-12", confirmed
   no such selector exists anywhere in the CSS), so that wrapper carries
   none of the grid's own flex/float behavior either. With nothing to float
   them, every label and its field rendered as its own full-width block
   stacked down the page instead of several label/field pairs sitting
   across each row, and the whole bar rendered far narrower than its real
   container since nothing was giving the stacked single-column content
   any horizontal layout. Restoring "float: left" (the same fix already
   applied to ".gen"/".qc_mainPrat" columns elsewhere in this file) puts
   them back side by side without needing an actual ".row" ancestor for
   the ".col-sm-*" elements themselves - ".qc_mainPrat" is "display:
   inline-block" (style-new.css) and each ".row" here is itself a flex
   item's flex container, so both already establish their own block
   formatting context and correctly wrap around the now-floated columns
   without a height collapse. Scoped via :has(#filter_btn) - the Filter
   button's id, unique to this bar - so other ".qc_mainPrat" filter forms
   sitewide keep their own layout. Several near-duplicate pan-management*
   .php files (see the hr/ module note in include/asset-version-config.php)
   share this exact filter-bar markup and get the same fix for free. */
.qc_mainPrat:has(#filter_btn) [class*="col-sm-"]:not(:only-child) {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* FIX: The DataTable wrapper is ending up narrower than the reference,
   which makes the horizontal scroll area start too far in from the left
   and visually compresses the grid. Let the wrapper occupy the same
   near-full attendance width used by DevOps while preserving overflow. */
@media (min-width: 1366px) {
  #example8_wrapper {
    width: calc(100% - 40px) !important;
    margin-left: 20px !important;
    margin-right: 20px !important;
  }
}

/* FIX: Bootstrap 5's .pagination component is "display: flex" (Bootstrap
   3's was an inline-block list). A flex child is block-level for layout
   purposes, so it forces its ".dt-paging" wrapper - itself only
   "display: inline" - onto its own line via CSS blockification, instead
   of flowing inline next to the length/search controls like DevOps.
   inline-block keeps the wrapper an atomic inline-level box so its
   flex content no longer breaks the row. */
#example8_wrapper .dt-paging {
  display: inline-block !important;
}

/* FIX: style-new.css has a ".records button { background: #2296F3; color:
   #fff; ... }" rule intended for other custom buttons that happen to share
   the ".records" wrapper class. DataTables 1.x rendered pagination controls
   as <a> tags (unaffected by that rule), but the new DataTables 2.x
   Bootstrap5 adapter renders them as real <button class="page-link">
   elements, so every pagination button - not just the active page - was
   getting filled solid blue instead of Bootstrap 3's white/blue-outline
   look. Carbon Blue 60 pager, matching carbon-theme.css. */
#example8_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#example8_wrapper .dt-paging .page-link:hover,
#example8_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#example8_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#example8_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

#example8 thead tr, #example8 thead th {
  height: 55px !important;
}

/* ================================================================
5. UTILITY CLASSES
================================================================ */

.hide {
  display: none !important;
}

/* FIX: Asset settings submenu was upgraded to Bootstrap 5 collapse markup.
   Keep the old visual style while letting BS5 handle the open/close state. */
.menu_box.training_top {
  position: relative;
  width: 200px;
  margin-left: 0;
  z-index: 20;
}

.menu_box.training_top .asset-menu {
  position: relative;
  width: 200px;
  margin: 0;
}

.menu_box.training_top .asset-menu .panel,
.menu_box.training_top .asset-menu .panel-default,
.menu_box.training_top .asset-menu .panel-heading,
.menu_box.training_top .asset-menu .panel-title {
  width: 200px;
  margin: 0;
  padding: 0;
  border: 0;
  background: transparent;
  box-shadow: none;
}

.menu_box.training_top .asset-menu .panel-title {
  margin: 0;
  padding: 0;
  font-size: 14px;
  line-height: 40px;
}

.menu_box.training_top .asset-menu-toggle {
  display: block;
  width: 200px;
  height: 40px;
  padding: 0;
  color: #000;
  background: #ddd;
  border: 0;
  border-radius: 4px;
  font-size: 14px;
  font-weight: 400;
  line-height: 40px;
  text-align: center;
  text-decoration: none;
}

.menu_box.training_top .asset-menu-toggle:focus {
  outline: 0;
  box-shadow: none;
}

.menu_box.training_top .asset-menu-collapse {
  position: absolute;
  top: 40px;
  left: 0;
  width: 524px;
  background: #fff;
  border: 1px solid #cfcfcf;
  box-shadow: none;
  z-index: 2000;
}

.menu_box.training_top .asset-menu-collapse .list-group {
  display: grid;
  grid-template-columns: 1fr 1fr;
  column-gap: 16px;
  width: 100%;
  margin: 0;
  padding: 0 10px;
  list-style: none;
}

.menu_box.training_top .asset-menu-collapse .list-group li {
  display: block;
  min-height: 40px;
  margin: 0;
  padding: 0;
  border: 0;
  border-bottom: 1px solid #e5e5e5;
  background: #fff;
}

.menu_box.training_top .asset-menu-collapse .list-group li a {
  display: block;
  height: 40px;
  padding: 0 2px;
  color: #000;
  font-size: 14px;
  font-weight: 400;
  line-height: 40px;
  text-decoration: none;
  white-space: nowrap;
}

.menu_box.training_top .asset-menu-collapse .list-group li a:hover {
  color: #000;
  background: transparent;
  text-decoration: none;
}

/* Shared scroll cap for every module submenu dropdown variant. */
.menu_box.training_top .asset-menu-collapse,
.menu_box.training_top .left_bar.new_left_bar .collapse.show {
  max-height: min(420px, 70vh);
  overflow-y: auto;
  overflow-x: hidden;
  -webkit-overflow-scrolling: touch;
}

/* Preserve Bootstrap's height animation while the shared Menu opens/closes.
   Applying scroll overflow during .collapsing makes the list snap directly
   to its final box, which reads as a page jerk. */
.menu_box.training_top .left_bar.new_left_bar .collapse.collapsing,
.menu_box.training_top .left_bar.new_left_bar .collapsing {
  height: 0;
  overflow: hidden !important;
  transition: height 0.35s ease !important;
}

/* Legacy card/panel submenus (hr-settings, supply-settings, etc.) — match
   the asset-menu toggle footprint and float the open list over content. */
.menu_box.training_top .left_bar.new_left_bar .card,
.menu_box.training_top .left_bar.new_left_bar .panel {
  position: relative;
  width: 200px;
  margin: 0;
  border: 0;
  background: transparent;
  box-shadow: none;
}

.menu_box.training_top .left_bar.new_left_bar .card-header,
.menu_box.training_top .left_bar.new_left_bar .panel-heading {
  padding: 0;
  margin: 0;
  border: 0;
  background: transparent;
}

.menu_box.training_top .left_bar.new_left_bar .card-header h4,
.menu_box.training_top .left_bar.new_left_bar .panel-title {
  margin: 0;
  padding: 0;
  font-size: 14px;
  line-height: 40px;
}

.menu_box.training_top .left_bar.new_left_bar .card-header a,
.menu_box.training_top .left_bar.new_left_bar .panel-title a {
  display: block;
  width: 200px;
  height: 40px;
  padding: 0;
  color: #000;
  background: #ddd;
  border: 0;
  border-radius: 4px;
  font-size: 14px;
  font-weight: 400;
  line-height: 40px;
  text-align: center;
  text-decoration: none;
}

/* FIX [FDCM-3547]: Bootstrap 5's collapse.js removes the base ".collapse"
   class the instant it adds ".collapsing" (and only restores "collapse
   show" once the height transition finishes) - unlike the class-stacking
   behavior these selectors were written for. So every rule below that was
   scoped to ".collapse.collapsing" or ".collapse .list-group" never
   actually matched while the menu was mid-animation: for that ~0.35s the
   box had none of this positioning/background/grid styling, falling back
   to an unstyled, single-column, transparent-background list that then
   snapped into the real 2-column white box the instant the transition
   ended - the open "jerk" DevOps doesn't have. Adding the classless
   ".collapsing" variant alongside ".collapse.collapsing" everywhere below
   covers both the (never-hit) old assumption and the real BS5 state. */
.menu_box.training_top .left_bar.new_left_bar .collapse.show,
.menu_box.training_top .left_bar.new_left_bar .collapse.collapsing,
.menu_box.training_top .left_bar.new_left_bar .collapsing {
  position: absolute;
  top: 40px;
  left: 0;
  width: 524px;
  background: #fff;
  border: 1px solid #cfcfcf;
  box-shadow: none;
  z-index: 2000;
}

.menu_box.training_top .left_bar.new_left_bar .collapse .list-group,
.menu_box.training_top .left_bar.new_left_bar .collapsing .list-group {
  display: grid;
  grid-template-columns: 1fr 1fr;
  column-gap: 16px;
  width: 100%;
  margin: 0;
  padding: 0 10px;
  list-style: none;
}

/* FIX: hr/jobs.php's "All Job"/"Add New" flyout only - its <ul> carries this
   extra ".jobs-menu-list" class so this override applies ONLY here, not to
   every other page sharing the ".list-group" flyout above. That shared
   rule's "padding: 0 10px" left a 10px sliver of the flyout's own white
   background showing on both sides of each li, which the li's grey+arrow
   hover fill (below) doesn't reach - hence the white gap. Zeroing the
   padding here lets the hover fill run edge-to-edge for this page while
   every other ".menu_box.training_top" submenu keeps its existing 10px
   inset untouched. */
.menu_box.training_top .left_bar.new_left_bar .collapse .list-group.jobs-menu-list,
.menu_box.training_top .left_bar.new_left_bar .collapsing .list-group.jobs-menu-list {
  padding: 0;
}

.menu_box.training_top .left_bar.new_left_bar .collapse .list-group li,
.menu_box.training_top .left_bar.new_left_bar .collapsing .list-group li {
  display: block;
  box-sizing: border-box;
  width: 100%;
  min-height: 40px;
  margin: 0;
  padding: 0;
  border: 0;
  border-bottom: 1px solid #e5e5e5;
  background: #fff;
}

.menu_box.training_top .left_bar.new_left_bar .collapse .list-group li a,
.menu_box.training_top .left_bar.new_left_bar .collapsing .list-group li a {
  display: block;
  box-sizing: border-box;
  width: 100%;
  height: 40px;
  padding: 0 2px;
  color: #000;
  font-size: 14px;
  font-weight: 400;
  line-height: 40px;
  text-decoration: none;
  white-space: nowrap;
}

/* FIX [FDCM-3547]: this hover rule used to just reset to "background:
   transparent", silently dropping DevOps's Bootstrap 3 hover feedback for
   this widget - style-new.css's own ".left_bar ul li a:hover" rule (line
   ~1092) paints a grey background with a small right-pointing arrow
   (images/arrow.png) so the hovered item is visually obvious, but that
   rule's specificity (0,2,3) loses to this file's more specific selector
   (0,7,2), so it never painted anything once this fix file's blanket
   "background: transparent" was added. Reproducing DevOps's grey+arrow
   hover here directly so it wins instead of just falling through to
   nothing. Applied on the <li> rather than the <a> so the whole row
   (the <a> only wraps the text, not the full 254px-wide column) picks up
   the grey fill and arrow, not just the glyphs. */
.menu_box.training_top .left_bar.new_left_bar .collapse .list-group li:hover {
  background: #e6e6e6 url(../images/arrow.png) no-repeat 97% 50%;
}

.menu_box.training_top .left_bar.new_left_bar .collapse .list-group li:hover a {
  color: #000;
  background: transparent;
  text-decoration: none;
}

/* FIX [FDCM-3547]: shared ".menu_box.training_top" pages — Menu toggle and
   page title on ONE row: Menu fixed left, title centered to the full row.
   Menu is anchored to the direct ".container" (or ".has-menu-box" fallback
   from header.php) so it never attaches to an unrelated ".col-*" column.
   Below 768px the Menu stays stacked above the title in normal flow. */
@media (min-width: 768px) {
  .container:has(> .menu_box.training_top),
  .container.has-menu-box {
    position: relative;
    padding-top: 24px;
  }

  .container:has(> .menu_box.training_top) > .menu_box.training_top,
  .container.has-menu-box > .menu_box.training_top {
    position: absolute !important;
    left: 12px;
    top: 24px;
    float: none !important;
    flex: none !important;
    width: 200px !important;
    max-width: 200px !important;
    margin-top: 0 !important;
    padding-left: 0;
    z-index: 20;
  }

  .hr-settings.container.has-menu-box > .menu_box.training_top {
    top: 45px;
  }

  /* FIX [FDCM-3547]: the ".menu_box" flex item above still collapsed to
     0 height on general-notice-types.php (and any other *-submenu.php
     consumer whose ".Middle" content streams in asynchronously), which
     let its inner "Menu" card land far below the heading instead of
     beside it. Cause: ".left_bar.new_left_bar" (style-new.css) is
     "position: absolute" with "top" left as "auto", a pre-flex layout
     trick that predates this fix. With no "top", its vertical placement
     falls back to the CSS "static position" algorithm - where the box
     would have flowed had it been static - which is inconsistent inside
     a flex container and depends on what content has rendered so far.
     On support-routing.php (content present at first paint) it happens
     to resolve correctly; on general-notice-types.php (content injected
     later via JS) it resolves to the wrong spot, and the parent
     ".menu_box" - having no other in-flow content - collapses to 0
     height in the meantime. Forcing this child back into normal flow
     removes the dependency on that fragile calculation entirely, the
     same way ".menu_box" itself was already pulled out of absolute
     positioning above. */
  .container:has(> .menu_box.training_top) > .menu_box.training_top .left_bar.new_left_bar,
  .container.has-menu-box > .menu_box.training_top .left_bar.new_left_bar {
    position: relative !important;
    left: auto !important;
    top: auto !important;
    width: 100% !important;
  }

  .container:has(> .menu_box.training_top) > .Middle,
  .container.has-menu-box > .Middle {
    float: none !important;
    width: 100% !important;
    max-width: none !important;
    min-width: 0 !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  /* Bootstrap 5 gives a nested .container 12px of horizontal padding.
     These legacy HR Menu pages already inherit the outer container gutter,
     so retaining all 12px creates a 24px Menu-to-content step. Bootstrap 3
     landed the heading/grid content 15px from the Menu edge. A 3px nested
     gutter plus the row/column's 12px gutter restores that shared 15px line. */
  .container:has(> .menu_box.training_top) > .Middle > .container,
  .container.has-menu-box > .Middle > .container {
    padding-right: 3px !important;
    padding-left: 3px !important;
  }

  /* The shared partial is used in three legacy wrapper shapes. Normalize
     the two non-nested shapes to the same 15px content line as above. */
  .container:has(> .menu_box.training_top) > .Middle:not(:has(> .container)) {
    padding-right: 3px !important;
    padding-left: 3px !important;
  }

  .container:has(> .menu_box.training_top) > .row > :not(.menu_box),
  .container:has(> .row > .menu_box.training_top) > .row > :not(.menu_box) {
    padding-left: 15px !important;
  }

  /* support-users-settings.php and its sibling support pages place the
     shared Menu partial inside the first .row rather than directly under
     the container. Give that markup the same anchor and zero-gutter Menu. */
  .container:has(> .row > .menu_box.training_top) {
    position: relative;
    padding-top: 24px;
  }

  .container:has(> .row > .menu_box.training_top)
    > .row
    > .menu_box.training_top {
    position: absolute !important;
    top: 24px;
    left: 12px;
    width: 200px !important;
    max-width: 200px !important;
    margin-top: 0 !important;
    padding-right: 0;
    padding-left: 0;
    z-index: 20;
  }

  .container:has(> .row > .menu_box.training_top)
    > .row
    > .menu_box.training_top
    .left_bar.new_left_bar {
    position: relative !important;
    top: auto !important;
    left: auto !important;
    width: 100% !important;
  }

  /* Bootstrap 3 leaves 50px between the page title and the first content
     card on these HR Menu pages. BS5 currently leaves only 8px. This
     42px top-up only lands the full 50px on pages whose title happens to
     sit inside a ".row" direct child of ".container" - most *-submenu.php
     consumers don't nest ".heading_bold" that way (e.g. it's a direct
     child of ".Middle", not inside a ".row"), so they never picked up
     this rule and were still stuck at 8px. Kept as a harmless no-op
     top-up for whichever page this was originally written for (the h2
     rule below now supplies the full 50px on its own, so collapsing
     with this leaves it at 50px either way) - the real, structure-
     independent fix is the ".heading_bold h2" margin-bottom below. */
  .container:has(.menu_box.training_top)
    > .row:has(.heading_bold) {
    margin-bottom: 42px !important;
  }

  /* Title row — centered against the full container width, not the area
     to the right of the Menu column. Keep this a wrapping column so a
     sibling helper link (width:100%) cannot squeeze the h2 under Menu. */
  .container:has(> .menu_box.training_top) > .Middle > .heading_bold,
  .container.has-menu-box > .Middle > .heading_bold {
    display: flex;
    flex-direction: column;
    flex-wrap: wrap;
    align-items: center;
    justify-content: center;
    width: 100%;
    min-height: 40px;
    margin-left: 0 !important;
    padding-top: 0;
    text-align: center;
  }

  .container:has(> .menu_box.training_top) > .Middle > .heading_bold > a,
  .container.has-menu-box > .Middle > .heading_bold > a {
    flex: 0 0 auto;
    width: auto;
    max-width: 100%;
  }

  /* FIX: this used to force margin-bottom down to 8px unconditionally on
     every page carrying the shared Menu widget, relying on the separate
     ".row:has(.heading_bold)" rule above to top it back up to DevOps's
     50px total - but that rule only matches pages whose ".heading_bold"
     happens to sit inside a ".row" direct child of ".container", which
     most *-submenu.php consumers (hr-settings/corrective-action-
     problems.php, hr-settings/support-departments.php, etc.) don't.
     Those pages were left at a bare 8px gap after the title, sitewide,
     matching the reported "no gap after the title" pattern. Supplying
     the full 50px here directly removes the dependency on that other
     rule ever matching. */
  .container:has(> .menu_box.training_top) .heading_bold h2,
  .container.has-menu-box .heading_bold h2 {
    margin-top: 8px !important;
    margin-bottom: 50px !important;
  }

  .container.hr-settings.has-menu-box .heading_bold h2 {
    margin-top: 15px !important;
  }

  /* ATS-style asset shell: empty left grid track reserves Menu width so
     the title stays visually centered when header actions are present. */
  .container:has(> .menu_box.training_top) .cl-page-header,
  .container.has-menu-box .cl-page-header {
    display: grid;
    grid-template-columns: 200px minmax(0, 1fr) auto;
    align-items: center;
    gap: 16px;
    justify-content: stretch;
  }

  .container:has(> .menu_box.training_top) .cl-page-header-copy,
  .container.has-menu-box .cl-page-header-copy {
    grid-column: 2;
    text-align: center;
  }

  .container:has(> .menu_box.training_top) .cl-page-title,
  .container.has-menu-box .cl-page-title {
    margin-top: 8px;
    margin-bottom: 8px;
  }

  .container:has(> .menu_box.training_top) .cl-page-header-actions,
  .container.has-menu-box .cl-page-header-actions {
    grid-column: 3;
    justify-self: end;
  }
}

/* FIX: This page's single-level ".container" (the only content wrapper
   the markup uses here, unlike e.g. attendance.php's triple-nested one)
   steps through Bootstrap 5's responsive max-width table (540/720/960/
   1140/1320px per breakpoint). At the 768px tablet breakpoint that's a
   540px cap with ~106px of dead margin per side; DevOps instead behaves
   like a Bootstrap 3 container - a single fixed 1170px cap (with the
   standard 15px gutter) that only kicks in once the viewport exceeds
   1170px, and is otherwise just 100% of the viewport. Below 1170px that
   collapses to the same edge-to-edge rendering DevOps shows at 768px;
   above it, the auto margins center it exactly like DevOps's desktop
   layout - so one rule (not a breakpoint-specific override) matches
   both. Scoped to containers wrapping the ".work-type-s" filter rows so
   other pages that rely on the normal responsive ".container" behavior
   (e.g. attendance.php) are unaffected. */
.container:has(.work-type-s) {
  max-width: 1170px !important;
  padding-left: 15px !important;
  padding-right: 15px !important;
}

/* FIX: Each filter row (Office, Show All, Drug Test, Start Date, etc.)
   is two ".col-md-6" divs: a label "<h3>" column first, then a control
   column. The label's h3 has "float: right" (style-new.css) so its text
   hugs the boundary between the two columns - a Bootstrap 3 pattern that
   depended on ".col-md-6" itself floating left to hold its column in
   place. Bootstrap 5 no longer floats ".col-md-6" by default, so the
   label column collapses to zero height (its only child is floated out
   of flow) and the control column - a plain block, unaffected by floats -
   claims the now-empty left slot instead. The floated label then lands
   in the right slot, swapping label and control left-to-right. DevOps
   avoids this by keeping ".col-md-6" floated left here; restoring that
   scoped to ".work-type-s" reproduces its correct label-left/control-
   right layout without floating grid columns anywhere else.

   That float alone still leaves the label text touching the control
   with no gap: Bootstrap 5 moved column gutter padding out of ".col-*"
   itself and onto ".row > *" (a child-combinator rule), so it never
   applies here since this markup's parent is ".work-type-s", not
   ".row". DevOps still gets the standard Bootstrap 3 15px-per-side
   gutter on these columns; restoring it here reproduces the gap.

   ".col-md-4"/".col-md-8" is the same row shape with a narrower label
   column (co-phone-edit.php's Office/Vendor/Co Phone #/etc. rows) - the
   label here is a plain "<span>" rather than a floated "<h3>", so there's
   no left/right swap, but the missing float still collapses the row to a
   single stacked column (label on its own line, then a full-width
   control line below) instead of DevOps's label-left/control-right
   layout, and leaves the ".qc_mainPrat" box's ".col-sm-8" width mostly
   empty since only one narrow stacked column is actually using it.
   Same restoration fixes both.

   ".col-md-5"/".col-md-3" is the same shape again, one row further down
   on co-phone-edit.php: the Enable/Disable radio row uses a blank
   "<span>" label column ("col-md-5") next to a narrower control column
   ("col-md-3", wrapping the Enable/Disable <table>) instead of the
   4/8 split used everywhere else on this page. Same missing-float
   collapse, same fix. */
.work-type-s .col-md-6,
.work-type-s .col-md-5,
.work-type-s .col-md-4,
.work-type-s .col-md-3,
.work-type-s .col-md-8 {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* FIX: The results grid's cells (Position, Submit Date, Results, etc.)
   sit flush against each other with no breathing room between inputs.
   style-new.css has ".table-wid-adjust td, .table-wid-adjust th {
   padding: 0; }" - that class is shared by ~60 other pages' tables, so
   it can't just be removed globally. DevOps keeps Bootstrap 5's default
   8px table-cell padding here; scoped via "#frm_dectype" - the AJAX-
   loaded form that wraps this page's grid (a sibling of, not nested
   inside, the ".work-type-s"-containing ".container", so a
   ".container:has(.work-type-s)" scope never actually matches this
   table) - so those other pages keep their existing zero-padding tables
   untouched. */
#frm_dectype table.table-wid-adjust td,
#frm_dectype table.table-wid-adjust th {
  padding: 8px;
}

/* FIX: DataTables 2.3.8's bootstrap5 integration renders a sort-arrow
   icon (span.dt-column-order, via ::before/::after) at 0.125 opacity on
   every orderable header, all the time. DevOps runs an older DataTables
   build whose equivalent icon is only shown on the actively-sorted
   column (and on hover of the others) - so every other header there
   looks icon-free. Scoped to this page's grid (see "#frm_dectype" note
   above) so other pages' DataTables headers (which may rely on the
   always-visible icon) are unaffected. */
#frm_dectype table.table-wid-adjust th .dt-column-order::before,
#frm_dectype table.table-wid-adjust th .dt-column-order::after {
  opacity: 0 !important;
}

#frm_dectype table.table-wid-adjust th:hover .dt-column-order::before,
#frm_dectype table.table-wid-adjust th:hover .dt-column-order::after {
  opacity: 0.125 !important;
}

#frm_dectype table.table-wid-adjust th.dt-ordering-asc .dt-column-order::before,
#frm_dectype table.table-wid-adjust th.dt-ordering-desc .dt-column-order::after {
  opacity: 1 !important;
}

/* FIX: Same DataTables-2-vs-Bootstrap-3 pagination mismatch already
   fixed for attendance.php's "#example8_wrapper" (see that block further
   up this file) - style-new.css's ".records button { background:
   #2296F3; color: #fff; ... }" rule paints every pagination <button
   class="page-link"> solid blue instead of just the active page, and
   Bootstrap 5's flex ".pagination" forces ".dt-paging" (display:inline)
   onto its own row instead of flowing next to length/search like
   DevOps. This page's grid uses id "background-drug" (not "example8"),
   so it needed its own copy of the same rules. */
#background-drug_wrapper .dt-paging {
  display: inline-block !important;
}

#background-drug_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#background-drug_wrapper .dt-paging .page-link:hover,
#background-drug_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#background-drug_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#background-drug_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* FIX: Bootstrap 5's global ".btn:hover" rule (bootstrap.min.css) sets
   "background-color: var(--bs-btn-hover-bg)". ".fileUpload" carries the
   plain ".btn" class with no "-primary"/etc modifier, so that CSS
   variable is never defined and resolves to transparent on hover - the
   button's blue background (from style-new.css) disappears, leaving
   its white "Upload" label barely visible and the "Drag & Drop Files"
   text unreadably faint. DevOps's Bootstrap 3 buttons have no such
   hover rule, so the button stays solid blue on hover; forcing the same
   base colors back on hover here matches that. */
.fileUpload.btn:hover {
  background-color: var(--cds-button-primary, #0f62fe) !important;
  color: #fff !important;
  border-color: transparent !important;
}

/* FIX: Bootstrap 5's global ".btn" rule sets "border-radius:
   var(--bs-btn-border-radius)" (defaults to 6px). DevOps's Bootstrap 3
   ".fileUpload" button has square corners - nothing in style-new.css
   overrides the radius for this class, so it relied on Bootstrap 3's
   own ".btn" never rounding corners by default. Zeroing it here
   restores that square look under Bootstrap 5. */
.fileUpload.btn {
  border-radius: 0 !important;
}

/* FIX: DataTables 2's length-select and search-input each render an
   empty accessibility "<label>" (for "aria-controls") right after the
   control. With no text it's visually pointless, but it's still a
   block-level element that adds its own line-height worth of height
   underneath the control - so ".dt-search" (input + label) ends up
   ~58px tall against ".dt-paging"'s ~44px and ".dt-length"'s ~38px.
   The row's "align-items: center" then centers each control within its
   own mismatched height rather than centering all three controls with
   each other, so they visibly sit at different baselines. Hiding the
   empty labels collapses each wrapper down to its control's own height
   so centering actually lines them up, matching DevOps (whose older
   DataTables build never rendered these labels at all). */
#background-drug_wrapper .dt-length label,
#background-drug_wrapper .dt-search label {
  display: none;
}

/* FIX: DevOps's old "dom" layout wrapped length/search/pagination in a
   single ".records" div with "text-align: center", so that whole
   cluster sits centered under the grid regardless of the grid's width.
   DT2's "layout" option instead renders them in a Bootstrap 5 grid
   column classed "col-md-auto me-auto" - "me-auto" (margin-right:auto)
   pushes the cluster flush to the row's left edge and lets it consume
   all remaining space on the right, so it never reaches the center.
   Adding a matching margin-left:auto balances that margin on both
   sides, centering the fixed-width cluster in the row exactly like
   DevOps's text-align:center did. */
#background-drug_wrapper .dt-layout-start {
  margin-left: auto !important;
}

/* FIX: Same DataTables-2-vs-Bootstrap-3 mismatch as "#background-drug_wrapper"
   above, now on personnel/timesheet-disputes.php's grid (id "timesheet-
   disputes" - previously the generic "example2", which is why it needs its
   own copy of these rules rather than sharing a selector). See the
   "#background-drug_wrapper" blocks above for the full root-cause
   explanation of each rule. */
#timesheet-disputes_wrapper .dt-paging {
  display: inline-block !important;
}

#timesheet-disputes_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#timesheet-disputes_wrapper .dt-paging .page-link:hover,
#timesheet-disputes_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#timesheet-disputes_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#timesheet-disputes_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

#timesheet-disputes_wrapper .dt-length label,
#timesheet-disputes_wrapper .dt-search label {
  display: none;
}

#timesheet-disputes_wrapper .dt-layout-start {
  margin-left: auto !important;
}

/* Keep row selects inside the dispute borders, aligned with the text fields. */
#timesheet-disputes tbody td select.form-control {
  margin-top: 3px !important;
  margin-bottom: 3px !important;
  top: auto !important;
}

/* Expand to fit the selected page of rows; retain horizontal scrolling. */
#timesheet-disputes_wrapper .dt-table-scroll,
#timesheet-disputes_wrapper .dt-scroll-body,
#timesheet-disputes_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

/* FIX: DevOps's old "dom: '...exportappend...'" trick used to move this
   grid's ".export_function" Export To select into the DataTables toolbar
   row, so it sat inline with the pageLength/search/paging cluster. DT2's
   "layout" option has no equivalent custom-DOM hook, so the select was
   left in its original static markup position instead - a plain
   block-level div below the grid, disconnected from the pagination row
   above it.

   This used to be faked with a negative margin-top + a fixed "right: 33%"
   nudge, but that percentage only happened to line up with the last page
   button when the grid had enough rows to render a multi-button
   pagination cluster. With few/no rows (e.g. a date range with no
   disputes) "paging" collapses to just its two prev/next arrows, the
   whole ["pageLength","search","paging"] cluster (".dt-layout-start",
   centered via its own margin-left/right:auto - see the rule below)
   shrinks and re-centers with it, and the fixed 33% offset overshoots
   past the now-much-narrower pagination, landing on top of the
   length/search controls instead - the reported misalignment.

   Fixed properly instead of re-tuning the guess: the table's own
   "initComplete" now moves ".timesheet-disputes-export" into
   "#timesheet-disputes_wrapper .dt-layout-start" (appended right after
   "paging"), so it's a genuine sibling of the pageLength/search/paging
   controls rather than a CSS-faked overlay - it reflows with them
   correctly regardless of how many pagination buttons render. Just
   needs inline sizing/spacing now, matching the treatment already
   applied to the "Select Personnel" popup's own Export To control
   (#personnel_selector_not_selected_modal .export_function_personnel). */
.timesheet-disputes-export {
  display: inline-block !important;
  vertical-align: middle;
  margin-left: 8px !important;
}

.timesheet-disputes-export select {
  padding: 5px 10px !important;
}

/* FIX: Bootstrap 5 dropped the default "float: left" on ".col-*"
   columns. Every two-column section (Contractor Information, Emergency
   Contact, Personal Vehicle, Insurance, Owner Information, etc.) pairs
   two ".col-md-6" (or ".col-md-8") divs inside a ".qc_mainPrat" wrapper
   to sit label-set side by side; without the float they stack full
   width, one above the other, instead. Bootstrap 5 still computes each
   column's width percentage correctly even without float, so restoring
   just the float (not the width) puts them back side by side, matching
   DevOps's Bootstrap 3 layout. ".qc_mainPrat" already carries Bootstrap
   5's ".clearfix" utility class in the markup, so floating its children
   doesn't collapse the row's height. Originally fixed page-locally on
   new-contractor.php; promoted here after the identical bug showed up
   on new-contractor-company.php. */
.qc_mainPrat > .col-md-6,
.qc_mainPrat > .col-md-8,
.qc_mainPrat > .col-sm-4,
.qc_mainPrat > .col-sm-6,
.qc_mainPrat > .col-sm-12 {
  float: left;
}

/* FIX: Bootstrap 3 label/field rows (".gen.mtb10" holding a
   ".col-sm-3" label next to a ".col-sm-8" input). BS3 floated those
   columns; BS5 does not, so QC Categories Config (and the same markup
   on other settings pages) stacked labels above full-width inputs
   instead of DevOps's two-column row. Flex restores that side-by-side
   layout without touching pages that don't use this pair. */
.gen.mtb10 {
  display: flex;
  align-items: flex-start;
  flex-wrap: wrap;
}
.gen.mtb10 > [class*="col-sm-3"],
.gen.mtb10 > [class*="col-md-3"] {
  flex: 0 0 25%;
  max-width: 25%;
  box-sizing: border-box;
}
.gen.mtb10 > [class*="col-sm-8"],
.gen.mtb10 > [class*="col-md-8"] {
  flex: 0 0 75%;
  max-width: 75%;
  box-sizing: border-box;
}

/* FIX (FDCM-3547): the ".gen.mtb10 { display:flex }" rule above (added
   for label/field two-column rows) also applies to any other page that
   happens to wrap its own content in a ".gen mtb10" div -- e.g.
   auto-claim-form-settings.php's Save/Cancel bar (".last-btn.tw-three"),
   which relies on being a plain full-width block so its own
   "text-align:center" can center the buttons. As a flex item it instead
   shrinks to its content width and sits left-aligned (flex's default
   justify-content: flex-start), so centering had no room to work.
   Confirmed live: forcing it back to a full-width flex item (instead of
   the global rule's shrink-to-content default) restores centering
   without touching the label/field pair this rule was written for. */
.gen.mtb10 > .last-btn {
  flex: 1 0 100%;
  width: 100%;
}

/* FIX [FDCM-3547]: same Bootstrap-3-vs-5 float regression as ".gen.mtb10"
   above, but on hr-settings/corrective-action-note-to-file-form.php and
   hr-settings/corrective-action-form.php's own label/field rows (".gen.mb10"
   holding a ".col-sm-6.col-md-4" label next to a ".col-sm-6.col-md-8" input,
   nested inside the ".action-form" ".gen.mtb10" two-column layout). BS3
   floated those columns side by side (matches DevOps); BS5 doesn't, so each
   label stacked above its own full-width input instead. Scoped to these
   pages since ".gen.mb10" is reused by 260+ other pages that haven't been
   verified against this fix. */
.ns-corrective-action-note-to-file-form .gen.mb10,
.ns-corrective-action-form .gen.mb10 {
  display: flex;
  align-items: flex-start;
  flex-wrap: wrap;
}
.ns-corrective-action-note-to-file-form .gen.mb10 > .col-md-4,
.ns-corrective-action-form .gen.mb10 > .col-md-4 {
  flex: 0 0 33.33333%;
  max-width: 33.33333%;
  box-sizing: border-box;
}
.ns-corrective-action-note-to-file-form .gen.mb10 > .col-md-8,
.ns-corrective-action-form .gen.mb10 > .col-md-8 {
  flex: 0 0 66.66667%;
  max-width: 66.66667%;
  box-sizing: border-box;
}

/* FIX [FDCM-3547]: corrective-action-form.php's "Enter Date" field
   (?IssueCorrectiveAction_AI=127, and any other saved record) wrapped
   onto its own line below its label instead of sitting beside it like
   every other field in the box. Root cause: this one field's own markup
   carries an extra ".mr-l-5" class (a pre-existing "margin-left:5px"
   utility defined inline in this page, not added by the fix above) on
   top of the ".col-md-8" the flex-basis rule above sizes to exactly
   66.667%. Label (33.333%) + field (66.667%) already sum to 100% of the
   row, so that extra 5px margin pushed the total past the row's width,
   and "flex-wrap: wrap" (needed elsewhere in this same rule) dropped the
   overflowing field to a second line. Confirmed live against DevOps,
   which keeps it on one line. Narrowing just this field's flex-basis by
   the same 5px leaves room for its margin without affecting the other
   (un-margined) ".col-md-8" fields in the box. */
.ns-corrective-action-form .gen.mb10 > .col-md-8.mr-l-5 {
  flex-basis: calc(66.66667% - 5px);
  max-width: calc(66.66667% - 5px);
}

/* FIX [FDCM-3547]: same Bootstrap-3-vs-5 float regression as ".gen.mtb10"
   above, on the other shape of label/field row this codebase uses -
   ".gen.mb20.disagree" holding TWO label+field pairs per row (four
   ".col-sm-3" divs: label, field, label, field - e.g. personnel/misc-pay-
   correction.php's "Add New Miscellaneous Pay Correction" modal: Office/
   Pay Type, PTO Hours/Description, etc.). BS3 floated these four 25%-wide
   columns side by side; BS5 doesn't outside a flex ".row", so they
   stacked one per line instead of two label/field pairs per row. This
   exact ".gen mb20 disagree" markup is reused by 55+ other pages (grep
   for class="gen mb20 disagree"); scoped to just this page/modal
   (".personnel-misc-pay-correction-page #addnewitem") rather than
   sitewide, since only this one has actually been verified. */
.personnel-misc-pay-correction-page #addnewitem .gen.mb20.disagree {
  display: flex;
  align-items: flex-start;
  flex-wrap: wrap;
}
.personnel-misc-pay-correction-page #addnewitem .gen.mb20.disagree > [class*="col-sm-3"] {
  flex: 0 0 25%;
  max-width: 25%;
  box-sizing: border-box;
  /* FIX: the four 25%-wide columns sat flush against each other (no
     gutter at all), so a field's own box (e.g. "Office"'s input) ran
     right up against the next pair's label (e.g. "Pay Type") with no
     visual gap between them - confirmed live/reported via annotated
     screenshot. Bootstrap 3's original ".col-sm-3" got its gutter from
     "padding: 0 15px" on every column; restoring just the trailing half
     of that (leading padding isn't needed - "Office"-to-"Training"
     spacing was already fine) recreates it without touching column
     width math. */
  padding-right: 15px;
}

/* FIX [FDCM-3547]: this modal's last row - a single label+field pair,
   "<div class="gen mb20"><div class="col-sm-3">Comment</div><div
   class="col-sm-9">...</div></div>" (no "disagree" class, since it's one
   pair, not two) - hit the same missing-float regression as the rule
   above, stacking "Comment" above a full-width input instead of sitting
   beside it like every other row. ".gen.mb20" alone (without "disagree")
   is reused far more inconsistently sitewide (192 files - some single
   ".col-sm-12" rows, some empty AJAX-target containers, etc.), so unlike
   the ".disagree" rule this one is scoped to just this modal rather than
   risking a sitewide change across markup shapes this session hasn't
   individually verified. */
.personnel-misc-pay-correction-page #addnewitem .gen.mb20:not(.disagree) {
  display: flex;
  align-items: flex-start;
  flex-wrap: wrap;
}
.personnel-misc-pay-correction-page #addnewitem .gen.mb20:not(.disagree) > .col-sm-3 {
  flex: 0 0 25%;
  max-width: 25%;
  box-sizing: border-box;
  padding-right: 15px;
}
.personnel-misc-pay-correction-page #addnewitem .gen.mb20:not(.disagree) > .col-sm-9 {
  flex: 0 0 75%;
  max-width: 75%;
  box-sizing: border-box;
}

/* FIX [FDCM-3547]: the rule above is meant for icon-only "X" close links
   (the ones this codebase always also marks with inline
   "style='float:right'" - grep confirms every "X"-text instance has it),
   but its selector doesn't actually check for that - it matches ANY
   "<a class='btn btn-secondary' data-bs-dismiss='modal'>", which is also
   the exact same markup this app's full-word "Cancel" buttons commonly
   use (108+ pages, grep for class="btn btn-secondary" combined with
   "Cancel<"), stripping their background/border/color down to a bare
   text link too - confirmed live on personnel/misc-pay-correction.php's
   "Add New Miscellaneous Pay Correction" modal (#addnewitem), where
   DevOps shows a proper bordered grey "Cancel" button. Restoring that
   look is scoped to just this modal for now rather than narrowing the
   sitewide rule above (e.g. by requiring "[style*='float']") - that
   selector matches on 100+ pages this session hasn't individually
   verified, so a sitewide change risks regressing whichever of them
   actually do rely on today's stripped-down look. */
.personnel-misc-pay-correction-page #addnewitem #form_addnewitem .save-btn a.btn-secondary {
  background-color: #e8e8e8 !important;
  border: 1px solid #ccc !important;
  border-radius: 3px !important;
  color: #333 !important;
  display: inline-block !important;
  padding: 5px 20px !important;
}

.personnel-misc-pay-correction-page #addnewitem #form_addnewitem input.form-control[readonly] {
  background-color: #fff !important;
}

/* FIX [FDCM-3547]: the "Document" column's "N/A" text sat visibly higher
   than every other column's content on the same row (reported via
   annotated screenshot). Every "<td>" in this grid computes
   "vertical-align: top", including this one - but the other cells hold
   ~38-40px-tall controls (inputs, the "Yes" checkbox) that nearly fill
   the row's own ~61px height (itself set by the tallest cell), leaving
   little visible gap below them, while "Document" is a single 15px text
   line top-aligned in that same tall row - the ~40px of empty space below
   it is what reads as "misaligned" against the visual center of the rest
   of the row. Centering just this column vertically instead matches it
   to how the rest of the row reads. */
.personnel-misc-pay-correction-page #misc_pay_correction_grid tbody td:nth-child(8) {
  vertical-align: middle;
  text-align: center;
}

/* FIX [FDCM-3547]: this grid's legacy-"dom"-string controls (".records"
   wrapping length/search/paging - same shape already fixed for other
   grids elsewhere in this file, e.g. "#example15_wrapper .records > div")
   left the search box sitting flush against the pagination controls with
   no gap between them. */
.personnel-misc-pay-correction-page #misc_pay_correction_grid_wrapper .records > div:has(.dt-search) {
  margin-right: 16px;
}

/* FIX: Bootstrap 3's ".col-*" grid classes always set "position:
   relative" (it's how BS3 supports the push/pull/offset modifiers);
   Bootstrap 5 only sets it on a column that's an actual flex item
   inside a ".row" (via a CSS variable ".row" sets), which these
   ".qc_mainPrat" columns aren't - so on this repo they have no
   positioned ancestor at all. That broke the hidden file-upload inputs
   used by the "Browse" buttons (Vehicle/General/Auto Insurance
   Certificate): style-new.css sizes them "position: absolute; width:
   97%" so they sit invisibly over their visible ".browse" button and
   capture clicks. With no positioned ".col-md-6" ancestor to resolve
   that 97% against, it fell through to ".container" (1320px) instead
   of the column's own ~519px, rendering the input ~1280px wide and
   pushing the whole page into horizontal scroll - even though nothing
   about the input is visibly wider than DevOps. Restoring "position:
   relative" on the same columns already floated above fixes the
   containing block without changing any visible layout. */
.qc_mainPrat > .col-md-6,
.qc_mainPrat > .col-md-8,
.qc_mainPrat > .col-sm-4,
.qc_mainPrat > .col-sm-6,
.qc_mainPrat > .col-sm-12 {
  position: relative;
}

/* FIX: The profile-photo "Upload" button (".NewHBoxR", the
   personnel-photo widget reused across new-hire/contractor pages) is
   centered under its 236px image placeholder via "margin-left: 35%" on
   the button itself (style-new.css, ".NewHBoxR .fileUpload.btn.fake-
   shadow"). That percentage resolves against the button's own
   containing block - ".input-group-btn", the only child of ".input-
   group". DevOps's Bootstrap 3 renders ".input-group" as "display:
   table" and ".input-group-btn" as "display: table-cell", so with no
   sibling cell to share the row with, that single cell stretches to
   the full 236px width, and 35% of that centers the button. Bootstrap
   5 rebuilt ".input-group" as flex, so ".input-group-btn" isn't a
   recognized class there anymore and just shrinks to the button's own
   width (~91px) - 35% of which undershoots the true center by about
   30px. Restoring the Bootstrap 3 table mechanics here (scoped to this
   widget, not all ".input-group" sitewide) reproduces DevOps's stretch
   and centers the button correctly. Originally fixed page-locally on
   new-contractor.php; promoted here after the identical bug showed up
   on new-contractor-company.php. */
.NewHBoxR .input-group {
  display: table;
}

.NewHBoxR .input-group-btn {
  display: table-cell;
  vertical-align: middle;
}

/* FIX: The "Browse" file upload widgets (".input-group.browse" -
   Personal Vehicle / Insurance certificates, etc.) are each an
   ".input-group" containing the visible "Browse" button and a
   full-width (100%) hidden file "<input>". Bootstrap 5's flex
   ".input-group" wraps the input onto its own line below the button
   (its natural flex-basis is the full row width, which doesn't fit
   next to the button), roughly doubling the box's height versus
   DevOps's Bootstrap 3, where the group is "display: table" and both
   children are same-row table-cells. Table display alone reproduced
   DevOps's one-row layout but left the row ~8px taller than the button
   actually needs (46px vs DevOps's 41px) - Chrome's table row-height
   algorithm was folding in the markup's whitespace text nodes and
   baseline alignment across cells in a way font-size/line-height
   resets on the cells couldn't override. Switching to flex (with
   "flex: 1" on the input so it still fills the remaining width,
   matching what the table-cell did for width) sidesteps the
   whitespace/baseline problem, but Chrome's flex row-height
   calculation turned out to have the same ~8px discrepancy even with
   "align-items: center" and both children individually verified at
   their correct 38px - something about how the browser computes the
   flex line's cross size here still doesn't shrink to match. Setting
   the container's height explicitly (to DevOps's own 41px) is the one
   override that reliably takes effect, so pinning it directly is more
   robust here than continuing to fight the automatic sizing.

   "align-items: center" still centered the "Browse" button and the
   input on slightly different vertical centerlines (a ~2px gap between
   their top edges, making the button look pushed down) rather than
   lining up their top/bottom edges. "stretch" (with "height: 100%" on
   both) removes that centering math entirely - both simply fill the
   container's full height edge-to-edge.

   A 1px residual offset remained even after that: the "<input>"
   carries a "margin: 1px 0 5px -1px" from elsewhere in the site's CSS
   (likely aimed at some validation-icon layout, unrelated to this
   widget), nudging it down and shrinking its usable height versus the
   button's unmargined box. Zeroing margin on both removes that last
   mismatch. Originally fixed page-locally on new-contractor.php;
   promoted here after the identical bug showed up on
   new-contractor-company.php. */
.input-group.browse {
  display: flex;
  align-items: stretch;
  height: 41px;
}

.input-group.browse .btn,
.input-group.browse > input {
  height: 100% !important;
  margin: 0 !important;
}

.input-group.browse > input {
  flex: 1;
}

/* FIX (FDCM-3547): claim-management-settings/medical-facilities.php's "Add
   Contract Documents" field reuses this same ".input-group.browse" widget,
   but (unlike new-contractor.php/new-contractor-company.php above) wraps it
   in a ".form-inline" container. The "@media (min-width: 768px) .form-inline
   .input-group { display: inline-table !important }" rule further down this
   file (restoring real Bootstrap 3 ".form-inline" behavior for ~20 other
   pages) carries "!important" and beats the plain ".input-group.browse {
   display: flex }" rule above on specificity ties, so it wins here and
   reverts the widget back to a table. Chrome's anonymous-table-object fixup
   then puts the "Browse" button's wrapping ".input-group-btn" (inline) and
   the filename "<input>" (inline-block by default) into two separate
   anonymous rows instead of merging them into one row's two cells, stacking
   the button above the filename field instead of beside it. Adding ".browse"
   here (one extra class) keeps the same specificity+importance rule but
   outranks the media-query selector, restoring flex without touching the
   other ".form-inline .input-group" instances sitewide. */
.form-inline .input-group.browse {
  display: flex !important;
}

/* FIX: The personnel sub-navigation "Menu" dropdown (".p_menu", the
   <ul> rendered by personnel/personnel-submenu-pages.php and shared
   across ~20 personnel/* pages - summary.php, banking-info.php,
   deduction.php, personnel-information.php, etc.) reuses Bootstrap's
   generic ".list-group" class name for its <ul>. Bootstrap 3 (DevOps)
   didn't have a ".list-group" component that opinionated about layout,
   so style-new.css's own two-column rule for this widget -
   ".payroll-submenu .panel-collapse li { float: left; width: 254px }"
   - was free to lay the <li> items out two-per-row. Bootstrap 5
   defines ".list-group { display: flex; flex-direction: column; }" -
   and flex items ignore "float" entirely per spec, so every <li>
   simply stacked into one column instead, even though "float: left"
   was still computed on each of them (the property just has no effect
   inside a flex container). Restoring "display: block" on this
   specific class (not ".list-group" itself, to avoid touching any
   unrelated Bootstrap 5 list-groups elsewhere) turns "float" back on
   and reproduces DevOps's two-column menu. */
.p_menu {
  display: block;
}

/* FIX: Same DataTables-2-vs-Bootstrap-3 pagination color mismatch
   already fixed for "#background-drug_wrapper"/"#example8_wrapper"
   (see those blocks above) - style-new.css's ".records button {
   background: #2296F3; color: #fff; ... }" paints every pagination
   button solid blue instead of just the active page. This table
   ("Select Personnel" modal, summary.php and other personnel/* pages
   via include/selector_not_selected_personnel2.php) used to init
   DataTables with the older "dom"/"sPaginationType: 'full_numbers'"
   option, which rendered its pagination as "<button
   class="dt-paging-button">" (DataTables' own core markup, targeted
   here previously) instead of the Bootstrap-5-adapter's
   ".page-link"/".page-item" classes. That include file has since been
   switched to the modern "layout" option (see its own inline "FIX"
   comment removing the dead "renderer" option), which now runs the
   Bootstrap 5 adapter like the other tables here - so this table's
   pagination is back to real ".page-link"/".page-item" markup and the
   old ".dt-paging-button" selector below no longer matches anything,
   leaving every button styled the same instead of DevOps's Bootstrap 3
   "full_numbers" look (only the active page filled blue, the rest
   plain white/blue-outline). Retargeting the same colors at
   ".page-link"/".page-item" instead, matching the other already-fixed
   tables above; colors copied directly from DevOps's computed styles
   for this table's pagination. */
#example_personnel_selected_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#example_personnel_selected_wrapper .dt-paging .page-link:hover,
#example_personnel_selected_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#example_personnel_selected_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#example_personnel_selected_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* FIX: This table's header cells ("Emp ID", "Tech ID", "Emp name",
   "Action") have no background/text-color rule anywhere in this
   codebase - DevOps's Bootstrap 3 build gets its light-blue header
   from a rule that isn't in this repo's copy of style-new.css (see
   the "shared style-new.css has diverged" root cause in the migration
   playbook), so it has to be reproduced here instead. Colors copied
   directly from DevOps's computed styles. */
#example_personnel_selected_wrapper table thead th {
  background-color: #edf6ff;
  color: #1f7fbd;
  font-weight: 600;
}

/* FIX: This table's init sets "orderable: false" on every column
   (targets 0-3 in columnDefs), matching DevOps's Bootstrap 3 build
   where none of these columns are sortable. DataTables 2 still
   renders its sort-indicator element (".dt-column-order", a caret
   drawn via ::before/::after) on the header regardless, since the
   column being non-orderable only stops the click handler, not the
   indicator markup. DevOps's Bootstrap 3 build never had this element
   at all. Hiding it site-wide within this table since none of its
   columns are ever sortable. */
#example_personnel_selected_wrapper .dt-column-order {
  display: none;
}

/* FIX: DataTables 2's search input and length "<select>" use its own
   "dt-input" class here (this table inits with the legacy "dom"
   option instead of "layout", so DT2's Bootstrap 5 styling adapter -
   which would normally class these ".form-control" - never applies,
   same root cause as the ".dt-paging-button" pagination fix above).
   Sitewide "input, select { ... }" resets then leave them undersized
   and grey-bordered instead of matching DevOps's Bootstrap 3
   ".form-control.input-sm" look. Sizes/colors copied directly from
   DevOps's computed styles. Needs "!important" on border/height: same
   sitewide "button, input, select, textarea { border: 1px solid #999
   !important; }" / height reset from style-new.css hit by the other
   form-control fixes on this page. */
#example_personnel_selected_wrapper .dt-input {
  height: 40px !important;
  padding: 5px 10px;
  border: 1px solid #cfdbe8 !important;
  border-radius: 3px;
  font-size: 16px;
}

/* FIX: The personnel sub-navigation "Menu" button (".new_left_bar", the
   same shared widget as the ".p_menu" fix above) is a Bootstrap 3
   ".panel"/".panel-heading"/".panel-title" accordion trigger. Bootstrap
   5 removed the ".panel" component entirely (no ".panel"/".panel-
   heading"/".panel-title" rules exist in its CSS at all - it was
   replaced sitewide by ".card", but this legacy widget was never
   migrated), so only style-new.css's own scoped color rule
   (".new_left_bar .panel-default>.panel-heading { background: #dcdcdc;
   color: #000; }") still applies; everything Bootstrap 3 used to
   supply - the heading's padding and rounded top corners, the title's
   16px font-size, the panel's border/rounded corners/shadow - is gone,
   leaving a plain, oversized, square-cornered grey box instead of
   DevOps's compact rounded button. Restoring Bootstrap 3's own default
   values here (not guessed - copied from DevOps's live computed
   styles) reproduces it exactly. Scoped to ".new_left_bar" (matching
   style-new.css's own scope) rather than the bare ".panel-heading"/
   ".panel-title"/".panel" classes, so any other Bootstrap-3-panel
   usage elsewhere in the site is untouched. */
.new_left_bar .panel {
  border: 1px solid #ddd;
  border-radius: 4px;
  box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05);
}

.new_left_bar .panel-heading {
  padding: 10px 15px;
  border-top-left-radius: 3px;
  border-top-right-radius: 3px;
}

.new_left_bar .panel-title {
  margin: 0;
  font-size: 16px;
  font-weight: 500;
}

/* FIX [FDCM-3547]: office/office-document.php — UAT parity under Bootstrap 5.
   UAT (style-new.css) styles ".panel"/".panel-heading"/".pan-date" for this
   accordion page; BS5 removed the panel component so only partial colors
   apply. Restore DevOps/UAT chrome and layout from style-new.css without
   page-local inline overrides (wrong #e7e9f5 heading from a prior fix). */
.Middle.doc .panel {
  border: 1px solid #ddd;
  border-radius: 4px;
  box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05);
}
.Middle.doc .panel.panel-default.panel-faq {
  background: #f5f5f5;
  border: none;
  margin: 0 auto 15px;
}
.Middle.doc .panel-default > .panel-heading {
  color: #333;
  background-color: #d2d2d2;
  border: none;
  padding: 10px 15px;
  border-top-left-radius: 3px;
  border-top-right-radius: 3px;
}
.Middle.doc .panel-heading {
  border-bottom: 1px solid transparent;
}
.Middle.doc .panel-title {
  margin: 0;
  font-size: 16px;
  font-weight: 500;
  display: block;
  overflow: hidden;
}
.Middle.doc .panel-title a {
  display: block;
  text-decoration: none;
  color: #333;
}
.Middle.doc .panel-faq .panel-heading .panel-title span {
  font-size: 13px;
  font-weight: normal;
}
.Middle.doc .panel-title img {
  float: left;
}
.Middle.doc .text-acc {
  padding-left: 70px;
  text-align: left;
}
.Middle.doc .text-acc h5 {
  margin: 0 0 2px;
  font-size: 18px;
  font-weight: 600;
  color: #333;
}
.Middle.doc .text-acc h6 {
  margin: 0;
  font-size: 13px;
  color: #888;
  font-weight: normal;
}
.Middle.doc .panel-title .pull-right,
.Middle.doc .office-doc-accordion-icon {
  float: right;
  color: #555;
}
.Middle.doc .panel-collapse.collapse:not(.show) {
  display: none;
}
.Middle.doc .panel-default > .panel-heading + .panel-collapse > .panel-body {
  padding: 5px;
}
.Middle.doc .panel-body {
  background: #fff;
}
.Middle.doc .pan-date ul li {
  display: inline-block;
}
.Middle.doc .pan-date {
  margin-bottom: 20px;
  margin-top: 5px;
}

/* FIX [FDCM-3547]: office/office-document.php tab pane uses legacy
   "tab-pane active in fade" (BS3). BS5 replaced ".in" with ".show" on
   faded tab panes; without ".show", ".fade:not(.show)" keeps opacity:0 so
   the Contracts accordion row is invisible on fdcm-3547. */
.Middle.doc .tab-content > .tab-pane.active,
.Middle.doc .tab-content > .tab-pane.show {
  display: block !important;
  opacity: 1 !important;
}

/* FIX: Same DataTables-2-vs-Bootstrap-3 mismatch as "#background-drug_wrapper"
   above, now on personnel/pto-request-que.php's grid (id "pto-request-que" -
   previously the generic "example", renamed so this page's own copy of these
   rules doesn't collide with any other page still using that id). See the
   "#background-drug_wrapper" blocks above for the full root-cause explanation
   of each rule. */
#pto-request-que_wrapper .dt-paging {
  display: inline-block !important;
}

#pto-request-que_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#pto-request-que_wrapper .dt-paging .page-link:hover,
#pto-request-que_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#pto-request-que_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#pto-request-que_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

#pto-request-que_wrapper .dt-length label,
#pto-request-que_wrapper .dt-search label {
  display: none;
}

#pto-request-que_wrapper .dt-layout-start {
  margin-left: auto !important;
}

/* FIX: the table carries Bootstrap 5's ".text-center" utility class (in
   the page's own markup), but DataTables 3's Bootstrap5 adapter CSS ships
   "table.dataTable thead th { text-align: left; }" - a rule that matches
   the <th> elements directly. ".text-center" only sets text-align on the
   <table> itself for its descendants to *inherit*; an explicit rule that
   matches the <th> element always wins over an inherited value regardless
   of the ancestor's specificity or "!important" (inheritance only
   supplies a fallback when nothing else matches the element itself) - so
   the header text renders left-aligned instead of centered like DevOps,
   whose older DataTables build has no such per-element override to fight
   the inherited ".text-center" value. Forcing it back to center, scoped
   to this grid's own id. */
#pto-request-que thead th {
  text-align: center !important;
}

/* FIX: same DataTables-2-vs-Bootstrap-3 mismatch as "#background-drug_wrapper"
   above, now on personnel/contractor_retainage.php's "Log" modal grid
   (id "retainage_setting_log_table"). See the "#background-drug_wrapper"
   blocks near the top of this file for the full root-cause explanation of
   each rule: the empty DataTables-3 accessibility <label> under
   ".dt-length"/".dt-search" throws off vertical centering against
   ".dt-paging" (reported as the search box "aligned upwards"), and the
   pageLength/search/paging cluster's own "me-auto" margin pushes it flush
   left instead of centered under the grid like DevOps's old
   "text-align:center" ".records" wrapper did (reported as the modal's
   pagination row being "left aligned"). */
#retainage_setting_log_table_wrapper .dt-length label,
#retainage_setting_log_table_wrapper .dt-search label {
  display: none;
}

#retainage_setting_log_table_wrapper .dt-layout-start {
  margin-left: auto !important;
}

/* FIX: same inherited-vs-explicit ".text-center" fight as the header fix
   above, now on body cells. DataTables 3 auto-detects each column's data
   type client-side and stamps a matching class onto every <td> in that
   column - "dt-type-numeric" for Employee ID/Requested Hours (plain
   numbers) and "dt-type-date" for Requested Date/Submitted On (parsed as
   dates) - and its own CSS pairs those classes with "text-align: right".
   Being an explicit rule matched directly on the <td>, it wins over the
   inherited ".text-center" value from the <table> the same way the
   header's per-element rule did. DevOps's older DataTables build has no
   such client-side type detection, so every column there (verified: all
   12, including Requested Hours and the dates) just inherits
   ".text-center" and renders uniformly centered. */
#pto-request-que tbody td {
  text-align: center !important;
}

/* FIX: Same always-visible-sort-caret mismatch documented on
   "#frm_dectype table.table-wid-adjust th" above (DataTables 2/3's
   Bootstrap5 adapter renders ".dt-column-order" at 0.125 opacity on every
   orderable header all the time; DevOps's older DataTables build only
   shows its equivalent indicator on the actively-sorted column, plus on
   hover of the others). This grid has its own stable id ("pto-request-que"),
   so it's scoped directly to the table rather than a wrapping form div. */
#pto-request-que thead th .dt-column-order::before,
#pto-request-que thead th .dt-column-order::after {
  opacity: 0 !important;
}

#pto-request-que thead th:hover .dt-column-order::before,
#pto-request-que thead th:hover .dt-column-order::after {
  opacity: 0.125 !important;
}

#pto-request-que thead th.dt-ordering-asc .dt-column-order::before,
#pto-request-que thead th.dt-ordering-desc .dt-column-order::after {
  opacity: 1 !important;
}

/* FIX: Same zero-padding mismatch already fixed for background-drug.php's
   grid ("#frm_dectype table.table-wid-adjust td/th" above) - style-new.css's
   ".table-wid-adjust td, .table-wid-adjust th { padding: 0; }" (shared by
   ~60 other pages' tables, so it can't be removed globally) left every
   header and data cell here with no breathing room, so adjacent column
   headers ("Employee ID"/"Employee", "Submitted On"/"Requested type",
   "Requested Hours"/"User Approving") visually ran into each other with
   no gap, and data rows looked cramped compared to DevOps's 8px-padded
   cells. This grid has its own stable id, so it's scoped directly to the
   table rather than a wrapping form div. */
#pto-request-que td,
#pto-request-que th {
  padding: 8px !important;
}

/* FIX: DevOps's table-striped rows get a solid, clearly visible
   "background-color: #f9f9f9" on odd rows. DataTables 3's Bootstrap5
   adapter implements ".table-striped" differently - not a background
   color at all, but an inset "box-shadow: 0 0 0 9999px rgba(0,0,0,0.05)"
   (a 5%-opacity black overlay) - which renders almost imperceptibly
   lighter than the plain white even rows, so the header (sitting over
   this grid's grey outer wrapper, with no background of its own) reads
   as a different, more distinctly grey band than the barely-tinted body
   rows instead of the two areas visually matching like DevOps. Restoring
   an explicit, clearly visible background-color on the same odd rows
   DataTables' own selector already targets - colors copied directly from
   DevOps's computed styles. */
#pto-request-que.table-striped > tbody > tr:nth-of-type(2n+1) > * {
  background-color: #f9f9f9 !important;
}

/* ================================================================
7. "#example" / "#example2" SHARED GRIDS (include/sub_header_local.php)
================================================================ */

/* FIX: sub_header_local.php's shared auto-init for any page's own
   "#example"/"#example2" table (guarded against the "Cannot reinitialise"
   crash - see the comments in that file) still configures both using the
   legacy "dom" string option ("<'records'<''l ><''f><''p> <'
   exportappend'>>") rather than the newer "layout" option other already-
   fixed grids on this site use (compare "#background-drug_wrapper" etc.
   above) - DataTables 3 still honours "dom" for backward compatibility,
   so it isn't broken outright, but the DOM it produces is different: a
   ".records" div (style-new.css: "text-align: center") wrapping four
   plain, unclassed <div> children (one each for length/search/paging/
   export), where DevOps's old build rendered the equivalent controls as
   naturally-inline elements that "text-align: center" could actually
   center. A bare <div> is block-level by default, so under Bootstrap 5
   each of those four children forces its own line regardless of
   "text-align" (which only ever affects inline content) - length,
   search, and paging end up stacked vertically instead of DevOps's
   single centered row. This shared init is reused verbatim by ~16 active
   pages (grep for id="example2"), not just this one, so the fix is
   global rather than page-scoped, same reasoning as the ".form-group"
   fix above. */
#example_wrapper .records > div,
#example2_wrapper .records > div {
  display: inline-block !important;
  vertical-align: middle !important;
}

/* FIX: Bootstrap 5's ".form-control"/".form-select" (the classes DT3's
   Bootstrap5 adapter now stamps onto the search input and length select,
   in place of DevOps's unstyled native elements) are block-level with
   "width: 100%" by default. Even after the fix above makes their
   *wrapping* <div> inline-block, the search <input> itself still
   stretches to fill essentially the whole ".records" width instead of
   DevOps's compact ~115px box, because "width: 100%" resolves against
   its own containing block regardless of how that block is displayed. */
#example_wrapper .dt-search input,
#example2_wrapper .dt-search input {
  width: auto !important;
}

/* FIX: same empty-accessibility-<label> height mismatch already fixed on
   "#background-drug_wrapper" above (DT2/3 renders a "for"-linked <label>
   with no text under both the length select and the search input; with
   no content it's visually invisible but still an extra block-level line
   of height under each control, throwing off their vertical alignment
   relative to the pagination nav next to them). */
#example_wrapper .dt-length label,
#example2_wrapper .dt-length label,
#example_wrapper .dt-search label,
#example2_wrapper .dt-search label {
  display: none;
}

/* FIX: same DataTables-2/3-vs-Bootstrap-3 pagination color mismatch
   already fixed on every other grid above (style-new.css's ".records
   button { background: #2296F3; color: #fff; ... }" paints every
   pagination <button class="page-link"> solid blue instead of just the
   active page; colors restored to DevOps's Bootstrap 3 white/blue-
   outline look, copied from its computed styles). */
#example_wrapper .dt-paging,
#example2_wrapper .dt-paging {
  display: inline-block !important;
}

#example_wrapper .dt-paging .page-link,
#example2_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#example_wrapper .dt-paging .page-link:hover,
#example2_wrapper .dt-paging .page-link:hover,
#example_wrapper .dt-paging .page-link:focus,
#example2_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#example_wrapper .dt-paging .page-item.active .page-link,
#example2_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#example_wrapper .dt-paging .page-item.disabled .page-link,
#example2_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* FIX: same always-visible-sort-caret mismatch documented on every other
   grid above (DataTables 2/3's Bootstrap5 adapter renders
   ".dt-column-order" at 0.125 opacity on every orderable header all the
   time; DevOps's older DataTables build only shows its equivalent
   indicator on the actively-sorted column, plus on hover of the others).
   Scoped to the table id directly since both ids are stable. */
#example thead th .dt-column-order::before,
#example thead th .dt-column-order::after,
#example2 thead th .dt-column-order::before,
#example2 thead th .dt-column-order::after {
  opacity: 0 !important;
}

#example thead th:hover .dt-column-order::before,
#example thead th:hover .dt-column-order::after,
#example2 thead th:hover .dt-column-order::before,
#example2 thead th:hover .dt-column-order::after {
  opacity: 0.125 !important;
}

#example thead th.dt-ordering-asc .dt-column-order::before,
#example thead th.dt-ordering-desc .dt-column-order::after,
#example2 thead th.dt-ordering-asc .dt-column-order::before,
#example2 thead th.dt-ordering-desc .dt-column-order::after {
  opacity: 1 !important;
}

/* FIX: this table's headers render plain left-aligned instead of
   DevOps's centered ones - neither table carries a ".text-center"
   class, so DevOps must be centering its headers some other way (an
   older DataTables default, or a rule this repo's style-new.css copy
   never picked up - see the migration playbook's root cause #7 on
   style-new.css divergence). Restoring center to match its verified
   computed styles directly, same approach as the "#pto-request-que
   thead th" header-alignment fix above. */
#example thead th,
#example2 thead th {
  text-align: center !important;
}

/* FIX: DataTables 3 auto-detects each column's data type client-side
   and stamps a matching class onto every <td> in that column -
   "dt-type-numeric" for Approved/Hours/Pay/Hourly Rate (plain numbers,
   including the Approved checkbox's own 0/1 "data-search"/"data-order"
   values) and "dt-type-date" for Date (parsed as a date) - and its own
   CSS pairs those classes with "text-align: right". DevOps's older
   DataTables build has no such client-side type detection, so every
   column there (verified) renders plain left-aligned instead.
   This is more than a cosmetic mismatch here: the "Approved" checkbox
   is a custom-styled ".control--checkbox" whose visible square
   (".control__indicator") is "position: absolute; left: 30px" relative
   to its own <label> (style-new.css) - a fixed offset that assumes the
   label sits at its cell's *left* edge. Right-aligning the cell pushes
   the (inline, so alignment-sensitive) label to the cell's *right* edge
   instead, so the indicator's fixed 30px+20px offset from there
   overflows straight past the cell's right border and renders on top of
   the next column ("Denial Reason") instead of inside its own. */
#example tbody td,
#example2 tbody td {
  text-align: left !important;
}

/* FIX [FDCM-3547]: claim-management-settings/wc-employee-status.php reuses
   this same "#example" grid, but its checkbox column has no
   ".control__indicator" position-overflow risk (unlike the page the fix
   above targets) and its headers ("Sub Status", "Primary Status") are
   already centered by the "#example thead th" rule above - so the blanket
   "#example tbody td { text-align: left !important }" just leaves this
   page's body cells, particularly the plain-text "Primary Status" column,
   out of line with their own centered headers. Scoped via
   :has(#WcEmployeeStatus_ID) (this page's own "Status" <select> id, grepped
   as unique to this page) rather than promoted global, since "#example" is
   reused by ~794 pages sitewide and the fix above is still needed by
   whichever one of those has the checkbox-overflow issue. */
body:has(#WcEmployeeStatus_ID) #example tbody td {
  text-align: center !important;
}

/* HR Settings: Remove row padding for HR Setting pages where we have
   a menu box. */
.hr-settings.has-menu-box .row>* {
  padding-left: 0px !important;
  padding-right: 0px !important;
}
.hr-settings.has-menu-box .menu_box.training_top {
  left: 15px !important;
}
.select2 textarea {
  border: none !important;
}
.modal-header > .close {
    margin-left: auto !important;
}

/* FIX [FDCM-3547]: hr-settings/corrective-action-problems.php's grid
   (#example1) never got the same header treatment as #example/#example2
   above - same always-visible-sort-caret mismatch (DataTables' Bootstrap5
   adapter renders ".dt-column-order" at 0.125 opacity on every orderable
   header all the time; DevOps's older DataTables build only shows its
   equivalent indicator on the actively-sorted column, plus on hover of
   the others) and the same plain-left-aligned-instead-of-centered header
   text. Same fix, just scoped to this table's id.
   "#example1" alone is NOT a safe selector here - grepping the repo turns
   up 44 other pages reusing the exact same id for their own, unrelated
   grid (this is the same generic-id reuse pattern as "#example"/
   "#example2" below, which turn up on ~794/~190 pages respectively - see
   the memory note on this). Scoped via ".ns-corrective-action-problems",
   a namespace class added to this page's own outer
   "<div class="container rtd">", so this can only ever match this one
   page's table - same approach as the existing ".ns-support-approvers"
   namespace elsewhere in this file. */
.ns-corrective-action-problems #example1 thead th .dt-column-order::before,
.ns-corrective-action-problems #example1 thead th .dt-column-order::after {
  opacity: 0 !important;
}

.ns-corrective-action-problems #example1 thead th:hover .dt-column-order::before,
.ns-corrective-action-problems #example1 thead th:hover .dt-column-order::after {
  opacity: 0.125 !important;
}

.ns-corrective-action-problems #example1 thead th.dt-ordering-asc .dt-column-order::before,
.ns-corrective-action-problems #example1 thead th.dt-ordering-desc .dt-column-order::after {
  opacity: 1 !important;
}

.ns-corrective-action-problems #example1 thead th {
  text-align: center !important;
}

.ns-corrective-action-types .last-btn .save-btn a,
.ns-corrective-action-problems .last-btn .save-btn a {
  color: #fff;
}

@media (min-width: 1200px) {
	.hr-settings.ns-corrective-action-problems,
  .hr-settings.corrective-action-to-problem-assignment,
  .hr-settings.ns-corrective-action-note-to-file-form,
  .hr-settings.ns-corrective-action-form,
  .hr-settings.ns-corrective-action-types,
  .hr-settings.ns-general-notice-types,
  .hr-settings.ns-hr-support-settings,
  .hr-settings.ns-support-departments,
  .hr-settings.ns-support-types,
  .hr-settings.ns-support-users-settings,
  .hr-settings.ns-support-routing,
  .hr-settings.ns-support-approvers,
  .hr-settings.ns-hr-ticket-form-data-types,
  .hr-settings.ns-support-ticket-form-config,
  .hr-settings.ns-company-org-management,
  .hr-settings.ns-org-management-levels {
		margin-top: 35px !important;
	}
}

@media (min-width: 768px) and (max-width: 1199.98px) {
	.container.hr-settings.ns-corrective-action-problems > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-to-problem-assignment > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-note-to-file-form > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-form > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-types > .menu_box.training_top,
  .container.hr-settings.ns-general-notice-types > .menu_box.training_top,
  .container.hr-settings.ns-hr-support-settings > .menu_box.training_top,
  .container.hr-settings.ns-support-departments > .menu_box.training_top,
  .container.hr-settings.ns-support-types > .menu_box.training_top,
  .container.hr-settings.ns-support-users-settings > .menu_box.training_top,
  .container.hr-settings.ns-support-routing > .menu_box.training_top,
  .container.hr-settings.ns-support-approvers > .menu_box.training_top,
  .container.hr-settings.ns-hr-ticket-form-data-types > .menu_box.training_top,
  .container.hr-settings.ns-support-ticket-form-config > .menu_box.training_top,
  .container.hr-settings.ns-company-org-management > .menu_box.training_top,
  .container.hr-settings.ns-org-management-levels > .menu_box.training_top {
    position: relative !important;
    top: auto !important;
    left: auto !important;
    margin: 0 !important;
  }
}

@media (min-width: 768px) and (max-width: 1199.98px) {
	.container.hr-settings.ns-corrective-action-problems > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-to-problem-assignment > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-note-to-file-form > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-form > .menu_box.training_top,
  .container.hr-settings.ns-corrective-action-types > .menu_box.training_top,
  .container.hr-settings.ns-general-notice-types > .menu_box.training_top,
  .container.hr-settings.ns-hr-support-settings > .menu_box.training_top,
  .container.hr-settings.ns-support-departments > .menu_box.training_top,
  .container.hr-settings.ns-support-types > .menu_box.training_top,
  .container.hr-settings.ns-support-users-settings > .menu_box.training_top,
  .container.hr-settings.ns-support-routing > .menu_box.training_top,
  .container.hr-settings.ns-support-approvers > .menu_box.training_top,
  .container.hr-settings.ns-hr-ticket-form-data-types > .menu_box.training_top,
  .container.hr-settings.ns-support-ticket-form-config > .menu_box.training_top,
  .container.hr-settings.ns-company-org-management > .menu_box.training_top,
  .container.hr-settings.ns-org-management-levels > .menu_box.training_top {
    position: relative !important;
    top: auto !important;
    left: auto !important;
    margin: 0 !important;
  }
}

/* ================================================================
8. JQUERY UI DATEPICKER - DEVOPS DESIGN MATCH
================================================================ */

/* FIX: jquery-ui@1.14.2's "base" theme (the version this repo loads)
   defines ".ui-state-active" (the picked/current day in any ".calendar"
   datepicker sitewide) as a bright blue fill (#007fff bg, #003eff
   border, white text) - that's this theme version's own default, not a
   Bootstrap conflict. DevOps loads an older jquery-ui release whose
   default theme rendered the active day as white/grey instead (verified
   via its live computed styles: white background, #aaa border, #212121
   text - the same as every other day cell, distinguished only by the
   border). Global because every "<input class="calendar">" sitewide
   shares the same jquery-ui datepicker widget and theme CSS. */
.ui-state-active,
.ui-widget-content .ui-state-active,
.ui-widget-header .ui-state-active {
  background: #fff !important;
  border: 1px solid #aaa !important;
  color: #212121 !important;
  font-weight: normal !important;
}

.ui-state-active a,
.ui-state-active a:link,
.ui-state-active a:visited {
  color: #212121 !important;
}

/* FIX: work-order-billing-qc.php (and any other page reusing its inline
   ".event a { background:#42B373 !important }" pattern to mark calendar
   days that have work orders) needs the selected day to stay green when
   it's also flagged ".event" - confirmed live on devops vs fdcm-3547:
   Aug 8 there is both today/selected (ui-state-active) and an event day,
   and shows #42B373 green/white text on devops but the generic white
   override above (".ui-widget-content .ui-state-active", 2 classes) on
   fdcm, because it outranks the page's own ".event a" (1 class + 1
   element) by specificity even though both are !important. This block
   adds a higher-specificity selector so an event day keeps its green
   highlight even when also selected. */
.event a.ui-state-active,
.ui-widget-content .event a.ui-state-active,
.ui-widget-header .event a.ui-state-active {
  background: #42B373 !important;
  border-color: #42B373 !important;
  color: #fff !important;
  font-weight: normal !important;
}

/* ================================================================
9. .DISAGREE BUTTON ON <input> ELEMENTS - DEVOPS DESIGN MATCH
================================================================ */

/* FIX: style-new.css only styles ".Disagree" via the "button.Disagree"
   selector, which requires an actual <button> tag. Many pages (e.g.
   personnel/field-training-input.php's "ADD ROW"/"Save" controls) use
   "<input type="button" class="Disagree">" / "<input type="submit"
   class="Disagree">" instead - the element-scoped selector never
   matched those, so they fell back to the plain unstyled browser
   button look. DevOps styles these two differently by their "type"
   attribute rather than treating ".Disagree" as one look: type="button"
   (e.g. "Add Row") is its blue action-button style, while type="submit"
   (e.g. "Save") is a separate grey/default style (verified via each
   one's live computed styles). Global because this input/Disagree
   pairing is used across many pages sitewide, not just this one. */
input[type="button"].Disagree {
  background: var(--cds-button-primary, #0f62fe) !important;
  color: #fff !important;
  padding: 7px 18px !important;
  border: 1px solid #1b89e2 !important;
  border-radius: 3px !important;
}

input[type="submit"].Disagree {
  background: #efefef !important;
  color: #212121 !important;
  padding: 7px 18px !important;
  border: 1px solid #999 !important;
  border-radius: 3px !important;
}

/* ================================================================
10. BOOTSTRAP-MULTISELECT RESPONSIVE WIDTH - DEVOPS DESIGN MATCH
================================================================ */

/* FIX: bootstrap-multiselect measures the original <select>'s rendered
   width once, at ".multiselect()" init time, and locks its ".btn-group"
   toggle wrapper to that exact pixel value via an inline "width: Npx"
   style - it never recalculates on resize. A plain "<select>" (DevOps's
   own, unstyled, elsewhere in this migration) instead sizes fluidly
   with its <td>, shrinking at narrower viewports. On
   personnel/field-training-input.php's "ADD ROW" table specifically,
   this fixed-width lock is what turns a modest, page-level horizontal
   overflow (DevOps's ~70px, verified live at a 1024px viewport) into a
   ~360px one locally at that same width, since every multiselect column
   holds its full desktop width regardless of how little room is left -
   this is what read as the grid being "cut off". ":has()" scopes this
   to multiselect's own toggle wrapper so other, unrelated ".btn-group"
   instances sitewide aren't affected. */
@media (max-width: 1365px) {
  .btn-group:has(> .multiselect.dropdown-toggle) {
    width: 100% !important;
  }

  .ns-support-ticket-form-config .btn-group:has(> .multiselect.dropdown-toggle) {
    width: auto !important;
  }
}

@media (max-width: 1439px) {
  /* Start the grid below the floated form instead of shrinking beside it.
     Fill the viewport up to the existing desktop cap; retain grid scrolling. */
  .big-table.attendance-page {
    clear: both;
    width: 100% !important;
    max-width: 1350px !important;
    margin-left: auto !important;
    margin-right: auto !important;
  }

  /* Attendance's labeled filters use 400px dropdowns on ATS. The shared
     full-width rule above pushes them below their labels on laptop viewports.
     Keep their configured width, while allowing them to fit smaller screens. */
  body:has(.big-table.attendance-page) .Middle.payrl .btn-group:has(> .multiselect.dropdown-toggle) {
    width: 400px !important;
    max-width: 100%;
  }
}

.personnel-attendance-page .big-table.attendance-page #example8_wrapper .dt-table-scroll {
  overflow-y: hidden !important;
}

.personnel-attendance-page .big-table.attendance-page .records {
  margin-top: 10px;
}

.personnel-attendance-page .big-table.attendance-page .records .dt-search {
  margin-right: 16px;
}

/* FIX: hr/general-notice.php's Office/Position Title/Department multiselect
   buttons are deliberately matched, pixel-for-pixel, to the Personnel field
   right below them: all three ".multiselect()" calls pass "buttonWidth:
   '400px'", and Personnel's own Select2 init (added for FDCM-3084) sets
   "width: '400px'" with a comment explicitly calling out that it "matches
   buttonWidth:'400px' set on #offices/#positiontitle/#departments above" -
   this page's whole design assumes all four fields render at the same fixed
   400px, never stretching full-width like every other ".gen.mtb10" field on
   this page does. The responsive-width fix directly above (added for
   personnel/field-training-input.php's "ADD ROW" table overflow) is
   sitewide, so below its 1365px breakpoint it also overrides these three
   buttons' own 400px lock to 100% of their field column - stretching them
   to fill the row while Personnel's Select2 box stays fixed at 400px,
   breaking the matched-width design (confirmed live: >=1365px all four
   fields render at the same 400px; <1365px Office/Position Title/
   Department balloon out while Personnel doesn't, visibly mismatched).
   Restoring the plugin's own 400px lock here - scoped via :has(#notice_title)
   the same way as this page's other fixes above, and with a plain class
   selector plus that :has() (an ID-level match) so it outranks the sitewide
   rule's own !important without needing a wider, riskier selector - keeps
   this page's intended design without touching field-training-input.php's
   fix. */
@media (max-width: 1365px) {
  .Middle:has(#notice_title) .btn-group:has(> .multiselect.dropdown-toggle) {
    width: 400px !important;
  }
}

/* ================================================================
11. ".works_gap" TWO-COLUMN FIELD-PICKER SECTIONS - DEVOPS DESIGN MATCH
================================================================ */

/* FIX: same "Bootstrap 5 dropped the default float on .col-*" bug already
   fixed above for ".qc_mainPrat > .col-md-6/.col-md-8" (new-contractor.php
   etc.), on a different wrapper: ".works_gap" (style-new.css: "display:
   inline-block; width: 100%") is the shared two-column-section wrapper
   used by every "*-info-settings.php" field-picker page (asset-info-
   settings.php's Asset Information/Additional Data Fields/Office
   Information/etc. pairs, plus the identical auto-claim-info-settings.php,
   claim-search-settings.php, liability-claim-info-settings.php, workers-
   comp-claim-info-settings.php, vehicle-list-view-settings.php, and
   worker-comp-info-settings.php - grep for "works_gap" confirms all of
   them share this exact markup). Each pair of ".col-md-6"/".col-md-8"
   children depended on Bootstrap 3's float to sit side by side; without
   it they stack full-width instead, one above the other, leaving the
   right half of the page blank. Restoring just the float (not the width,
   which Bootstrap 5 still computes correctly) puts them back side by
   side, matching DevOps's Bootstrap 3 layout - same reasoning and the
   same added "position: relative" (Bootstrap 5 only sets that on an
   actual ".row" flex-item, which these columns aren't) as the
   ".qc_mainPrat" fix. Global rather than page-scoped since it's already
   confirmed shared by 6+ active pages.

   That float alone still leaves the two columns touching with no gap
   between them: same root cause as the ".work-type-s .col-md-6" fix
   above - Bootstrap 5 moved column gutter padding out of ".col-*" itself
   and onto ".row > *" (a child-combinator rule), so it never applies
   here since these columns' parent is ".works_gap", not ".row".
   Restoring Bootstrap 3's own 15px-per-side gutter reproduces DevOps's
   gap between "Asset Information"/"Additional Data Fields" etc. */
.works_gap > .col-md-6,
.works_gap > .col-md-8 {
  float: left;
  position: relative;
  padding-left: 15px;
  padding-right: 15px;
  box-sizing: border-box;
}

/* FIX [FDCM-3547]: Bootstrap 5 dropped float:left on ".col-*". Fuse still
   nests those columns inside permission / transfer-list wrappers with no
   ".row" (where BS5 now puts both flex and gutter padding), so they keep
   their width % but stack as block boxes down the left edge. Same restore
   as ".qc_mainPrat"/".works_gap"/".work-type-s" above.
   Patterns covered:
   - ".office_grp > .col-*" — create-new-user.php, create-new-usernew.php,
     permissions.php, Header/Settings boxes on permissions-user.php and
     permissions-group.php, user-association.php
   - ".office_grp > .mr > .col-*" — permissions-user.php top form (the
     extra ".mr" wrapper). permissions-group-update.php uses ".mr > .row"
     so its columns stay on Bootstrap 5 flex and are not selected here
   - ".office_grp > .cen > .col-*" — permissions-group.php Create New Group
   - nested ".col-* > .col-*" inside those boxes — Office/User Group
     sitting inside a wider sibling column
   - ".office_grp1"/".membors_off" > form > ".col-*" — interviewer,
     recruiters, supervisor-groups, custom-groups, assign-group-permission
     transfer lists. Pages that later set display:flex on ".membors_off"
     (contractor-groups, custom-groups) keep that layout: float is ignored
     on a flex item
   - ".qc_mainPrat fieldset > .col-*" / ".office_grp1" / ".office_box" —
     support-routing three-across picker. Direct children only, so nested
     full-width boxes inside a column are left alone
   Desktop-only so style-new.css max-width:767px stacked rules still win.
   Do not match ".row > .col-*". */
@media (min-width: 768px) {
  .office_grp,
  .office_grp1.membors_off > form {
    display: flow-root;
  }

  .office_grp > [class*="col-"],
  .office_grp > .mr > [class*="col-"],
  .office_grp > .cen > [class*="col-"],
  .office_grp [class*="col-"] > [class*="col-"],
  .office_grp1 > [class*="col-"],
  .office_grp1 > form > [class*="col-"],
  .membors_off > [class*="col-"],
  .membors_off > form > [class*="col-"],
  .qc_mainPrat fieldset > [class*="col-"],
  .qc_mainPrat fieldset > .office_grp1,
  .qc_mainPrat fieldset > .office_box {
    float: left;
    position: relative;
    padding-left: 15px;
    padding-right: 15px;
    box-sizing: border-box;
  }
}

/* FIX: same DataTables-2/3-vs-Bootstrap-3 "shared #example/#example2
   grid" mismatch already fixed above (see section 7, "#example"/
   "#example2" SHARED GRIDS) - asset-info-settings.php additionally
   inits four more grids page-locally (#example3 Office Information,
   #example4 Employee Information, #example5 Assignment Fields, #example6
   Assets Fields) using the exact same legacy "dom" string option
   (verified identical config, byte-for-byte, to sub_menu_head_table.php's
   shared #example/#example2 init) - so they need the identical set of
   fixes, just re-scoped to these four ids. */
#example3_wrapper .records > div,
#example4_wrapper .records > div,
#example5_wrapper .records > div,
#example6_wrapper .records > div {
  display: inline-block !important;
  vertical-align: middle !important;
}

#example3_wrapper .dt-search input,
#example4_wrapper .dt-search input,
#example5_wrapper .dt-search input,
#example6_wrapper .dt-search input {
  width: auto !important;
}

/* FIX: these #example3/4/5/6 selectors are unscoped IDs, so they also hit
   any other page that happens to reuse "#example3" etc for its own,
   unrelated table (e.g. timesheet-approval-loc.php), silently hiding its
   search label with no relation to asset-info-settings.php at all. Scope
   to a page that actually has all four ids together, like the other
   rules in this section already assume. */
body:has(#example4):has(#example5):has(#example6) #example3_wrapper .dt-length label,
#example4_wrapper .dt-length label,
#example5_wrapper .dt-length label,
#example6_wrapper .dt-length label,
body:has(#example4):has(#example5):has(#example6) #example3_wrapper .dt-search label,
#example4_wrapper .dt-search label,
#example5_wrapper .dt-search label,
#example6_wrapper .dt-search label {
  display: none;
}

#example3_wrapper .dt-paging,
#example4_wrapper .dt-paging,
#example5_wrapper .dt-paging,
#example6_wrapper .dt-paging {
  display: inline-block !important;
}

#example3_wrapper .dt-paging .page-link,
#example4_wrapper .dt-paging .page-link,
#example5_wrapper .dt-paging .page-link,
#example6_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

#example3_wrapper .dt-paging .page-link:hover,
#example4_wrapper .dt-paging .page-link:hover,
#example5_wrapper .dt-paging .page-link:hover,
#example6_wrapper .dt-paging .page-link:hover,
#example3_wrapper .dt-paging .page-link:focus,
#example4_wrapper .dt-paging .page-link:focus,
#example5_wrapper .dt-paging .page-link:focus,
#example6_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

#example3_wrapper .dt-paging .page-item.active .page-link,
#example4_wrapper .dt-paging .page-item.active .page-link,
#example5_wrapper .dt-paging .page-item.active .page-link,
#example6_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

#example3_wrapper .dt-paging .page-item.disabled .page-link,
#example4_wrapper .dt-paging .page-item.disabled .page-link,
#example5_wrapper .dt-paging .page-item.disabled .page-link,
#example6_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* FIX: same always-visible-sort-caret mismatch already fixed above for
   every other grid (DataTables 2/3's Bootstrap5 adapter renders
   ".dt-column-order" at 0.125 opacity on every orderable header all the
   time; DevOps's older DataTables build only shows its equivalent
   indicator on the actively-sorted column, plus on hover of the others).
   These four tables' first column ("<th></th>", the field-name column)
   carries no "no-sort" class, so it's still orderable and still gets the
   icon like "Enable" does. */
#example3 thead th .dt-column-order::before,
#example3 thead th .dt-column-order::after,
#example4 thead th .dt-column-order::before,
#example4 thead th .dt-column-order::after,
#example5 thead th .dt-column-order::before,
#example5 thead th .dt-column-order::after,
#example6 thead th .dt-column-order::before,
#example6 thead th .dt-column-order::after {
  opacity: 0 !important;
}

#example3 thead th:hover .dt-column-order::before,
#example3 thead th:hover .dt-column-order::after,
#example4 thead th:hover .dt-column-order::before,
#example4 thead th:hover .dt-column-order::after,
#example5 thead th:hover .dt-column-order::before,
#example5 thead th:hover .dt-column-order::after,
#example6 thead th:hover .dt-column-order::before,
#example6 thead th:hover .dt-column-order::after {
  opacity: 0.125 !important;
}

#example3 thead th.dt-ordering-asc .dt-column-order::before,
#example3 thead th.dt-ordering-desc .dt-column-order::after,
#example4 thead th.dt-ordering-asc .dt-column-order::before,
#example4 thead th.dt-ordering-desc .dt-column-order::after,
#example5 thead th.dt-ordering-asc .dt-column-order::before,
#example5 thead th.dt-ordering-desc .dt-column-order::after,
#example6 thead th.dt-ordering-asc .dt-column-order::before,
#example6 thead th.dt-ordering-desc .dt-column-order::after {
  opacity: 1 !important;
}

/* ================================================================
12. DATATABLES GRID CONTROLS - GENERIC, EVERY GRID (DEVOPS DESIGN MATCH)
================================================================ */

/* FIX [FDCM-3547]: DataTables 3 default header layout does not match
   DevOps / live (DT 1.x). Live headers are plain <th> text, so a page's
   "text-align: center" (import-users.php already has this) actually
   centers the label, and the sort glyph is a background-image on the
   right. DT 3 wraps every header in ".dt-column-header" (flex,
   space-between) and auto-tags date/numeric columns "dt-type-date" /
   "dt-type-numeric", which (1) sets "text-align: left" (or right) on
   the <th> itself, beating inherited centering, and (2) "flex-direction:
   row-reverse" on those type columns, which parks the CSS caret on the
   LEFT of the label - the "Import Date" column on personnel/import-users.php
   is the visible case. Sort carets also stay at 0.125 opacity on every
   orderable header all the time; DevOps only shows them on hover and on
   the actively-sorted column.
   Shared default (no !important on alignment, so a page can still force
   left/right via "#table thead th", ".dt-head-left"/".dt-head-right",
   or its own stylesheet): labels centered, carets pinned to the right
   edge, hidden until hover / active sort. */
table.dataTable thead th,
table.dataTable thead td {
  position: relative;
}

table.dataTable thead th:not(.dt-head-left):not(.dt-head-right):not(.dt-left):not(.dt-right),
table.dataTable thead td:not(.dt-head-left):not(.dt-head-right):not(.dt-left):not(.dt-right),
table.dataTable thead th.dt-type-numeric:not(.dt-head-left):not(.dt-head-right):not(.dt-left):not(.dt-right),
table.dataTable thead th.dt-type-date:not(.dt-head-left):not(.dt-head-right):not(.dt-left):not(.dt-right),
table.dataTable thead td.dt-type-numeric:not(.dt-head-left):not(.dt-head-right):not(.dt-left):not(.dt-right),
table.dataTable thead td.dt-type-date:not(.dt-head-left):not(.dt-head-right):not(.dt-left):not(.dt-right) {
  text-align: center;
}

/* Title follows the <th> alignment so a page-level text-align on the
   header cell still wins (DT 3's flex wrapper otherwise ignores it). */
table.dataTable thead th .dt-column-title,
table.dataTable thead td .dt-column-title {
  text-align: inherit;
  flex-grow: 1;
}

table.dataTable thead th.dt-type-numeric:not(.dt-head-right):not(.dt-right) div.dt-column-header,
table.dataTable thead th.dt-type-date:not(.dt-head-right):not(.dt-right) div.dt-column-header,
table.dataTable thead td.dt-type-numeric:not(.dt-head-right):not(.dt-right) div.dt-column-header,
table.dataTable thead td.dt-type-date:not(.dt-head-right):not(.dt-right) div.dt-column-header {
  flex-direction: row;
}

table.dataTable thead > tr > th.dt-orderable-asc .dt-column-order,
table.dataTable thead > tr > th.dt-orderable-desc .dt-column-order,
table.dataTable thead > tr > th.dt-ordering-asc .dt-column-order,
table.dataTable thead > tr > th.dt-ordering-desc .dt-column-order,
table.dataTable thead > tr > td.dt-orderable-asc .dt-column-order,
table.dataTable thead > tr > td.dt-orderable-desc .dt-column-order,
table.dataTable thead > tr > td.dt-ordering-asc .dt-column-order,
table.dataTable thead > tr > td.dt-ordering-desc .dt-column-order {
  position: absolute;
  right: 8px;
  left: auto;
  top: 0;
  bottom: 0;
  margin: 0;
  align-self: stretch;
}

/* Kill DT 1.x PNG sort sprites from style-new.css once DT 3's
   ".dt-column-order" caret is present - otherwise both glyphs stack. */
table.dataTable thead th:has(.dt-column-order),
table.dataTable thead td:has(.dt-column-order) {
  background-image: none !important;
}

/* Hidden unless the header is hovered or this column is the active sort.
   Uses DT 3's own opacity variables so a page can restore always-on
   carets with e.g. "#table { --dt-order-arrow_opacity: 0.125; }" or
   keep an existing "#table th .dt-column-order::before { opacity: ...
   !important }" override. */
table.dataTable thead > tr > th,
table.dataTable thead > tr > td {
  --dt-order-arrow_opacity: 0;
}

table.dataTable thead > tr > th:hover,
table.dataTable thead > tr > td:hover {
  --dt-order-arrow_opacity: 0.65;
}

table.dataTable thead > tr > th.dt-ordering-asc,
table.dataTable thead > tr > th.dt-ordering-desc,
table.dataTable thead > tr > td.dt-ordering-asc,
table.dataTable thead > tr > td.dt-ordering-desc {
  --dt-order-arrow_opacity-current: 1;
}

.import-users-page .input-group .input-group-btn {
  margin: 0 auto;
}

.import-users-page #exampleImport_wrapper div.dt-buttons,
.import-users-page #exampleImportChangeTechID_wrapper div.dt-buttons {
  margin-top: 0 !important;
}

.import-users-page #exampleImport_wrapper div.dt-info,
.import-users-page #exampleImportChangeTechID_wrapper div.dt-info {
  display: flex;
  justify-content: center;
  margin-top: 10px;
}

.import-users-page #exampleImport_wrapper div.dt-paging.paging_full_numbers,
.import-users-page #exampleImportChangeTechID_wrapper div.dt-paging.paging_full_numbers {
  display: flex !important;
  justify-content: center;
}

/* FIX: TimeSheet Auto Correction page search input box UI issue */
.personnel-timesheet-auto-correction-page div.dt-container div.dt-search input {
  margin-top: .5em;
  margin-right: .5em;
}

.personnel-timesheet-auto-correction-page table.dataTable td.dt-empty {
  text-align: center !important;
}

/* FIX: every "layout"/"dom"-configured DataTables grid sitewide shares
   this exact same "records" row (length + search + paging, using DT3's
   Bootstrap5 adapter markup: ".dt-length"/".dt-search"/".dt-paging"
   inside plain unclassed <div>s) - but until now, matching it to
   DevOps's design needed its own copy-pasted set of ID-scoped rules per
   grid (see "#example"/"#example2" above, then "#example3"-"#example6",
   then "#example8" - three near-identical copies of the same fix, and
   still not covering every grid: personnel/misc-pay.php's own
   "#employee_table"/"#employee_table2"/"#employee_table3" grids had no
   coverage at all and rendered broken - length/search/paging each
   stacked on its own line instead of one row, like DevOps's "Holiday
   Pay" grid ("#example8", already fixed above) renders. Root cause is
   the same one documented in the "#example"/"#example2" fix above: a
   bare <div> is block-level by default, and DataTables 3's own CSS
   doesn't make these particular wrapper <div>s inline, so each stacks
   instead of flowing into one row.
   Generalizing the fix to ".dt-container" (the wrapper DataTables 3's
   Bootstrap5 adapter puts on literally every grid, regardless of table
   id) covers every current AND future grid sitewide in one place,
   instead of needing a new copy-pasted, ID-scoped block every time a
   page adds another table. This is lower specificity than the existing
   ID-scoped rules above (class vs. ID selector), so those still win
   unchanged wherever a grid needs something different from the norm -
   this is only the shared default they were all copies of. */
.dt-container .records > div {
  display: inline-block !important;
  vertical-align: middle !important;
}

.dt-container .dt-search input {
  width: auto !important;
}

/* DevOps renders the length control and every Export button (plain
   "buttons-html5" single-format exports, and "buttons-collection"
   dropdown exports used where a grid offers more than one format) as
   flat bordered boxes, not Bootstrap 5's default rounded/shadowed
   <select> and dropdown-toggle. Generalized here (was previously
   copy-pasted per page, e.g. qc-settings.php) so every grid sitewide
   gets it without a new ID-scoped block each time. */
/* Export buttons use the same flat treatment as DevOps. Page-length
   controls are normalized once in the global rule near the top of this file. */
.dt-container .dt-buttons .buttons-html5,
.dt-container .dt-buttons .buttons-collection {
  display: inline-block !important;
  padding: 6.16px 12.32px !important;
  border: 1px solid #999 !important;
  border-radius: 0 !important;
  background: #e9e9e9 !important;
  color: #000 !important;
  font-size: 12.32px !important;
  line-height: normal !important;
  box-shadow: none !important;
}

.dt-container .dt-buttons .buttons-collection::after {
  display: none !important;
}

/* Bootstrap 5's DataTables adapter wraps 2+ export buttons in a
   ".btn-group", which uses a negative left margin to fuse adjacent
   buttons into one connected bar (no gap, shared border) - DevOps's
   plain ".dt-buttons" (no "btn-group") renders each export button as
   its own separate, gapped box. Restore that gap here rather than via
   the button's own border-radius (already flattened above). */
.dt-container .dt-buttons.btn-group .buttons-html5,
.dt-container .dt-buttons.btn-group .buttons-collection {
  margin-left: 4.1px !important;
}

.dt-container .dt-buttons.btn-group .buttons-html5:first-child,
.dt-container .dt-buttons.btn-group .buttons-collection:first-child {
  margin-left: 0 !important;
}

/* DevOps stripes every grid's body rows (odd rows shaded), which
   Bootstrap 5's plain ".table" reset dropped (no ".table-striped" class
   is added by the DataTables Bootstrap 5 integration by default). */
.dt-container table.dataTable > tbody > tr.odd > * {
  box-shadow: none !important;
  background-color: #f2f2f2 !important;
}

.dt-container table.dataTable > tbody > tr.even > * {
  box-shadow: none !important;
  background-color: #fff !important;
}

/* Keep an empty search label out of the layout. The length label stays
   visible so its "entries" text (label::after) shows on every grid. */
.dt-container .dt-search label:empty {
  display: none !important;
}

.dt-container .dt-paging {
  display: inline-flex !important;
  flex-wrap: wrap;
  align-items: stretch;
  flex: 0 0 auto !important;
  width: auto !important;
  gap: 0 !important;
  padding: 0 !important;
  background: transparent !important;
}

.dt-container .dt-paging .pagination {
  display: inline-flex !important;
  flex-direction: row !important;
  flex-wrap: wrap;
  align-items: stretch;
  flex: 0 0 auto !important;
  width: max-content !important;
  gap: 0 !important;
  margin: 0 !important;
  padding: 0 !important;
  border-radius: 0 !important;
  background: transparent !important;
  --bs-pagination-border-radius: 0;
}

.dt-container .dt-paging li.page-item,
.dt-container .dt-paging li.dt-paging-button {
  margin: 0 !important;
  padding: 0 !important;
  min-width: 0 !important;
  background: transparent !important;
  border: 0 !important;
}

.dt-container .dt-paging .page-link,
.dt-container .dt-paging button.page-link,
.dt-container .dt-paging button.dt-paging-button,
.dt-container .dt-paging a.dt-paging-button,
.records .dt-paging button,
.records button.page-link,
.records button.dt-paging-button {
  box-sizing: border-box !important;
  display: inline-flex !important;
  align-items: center !important;
  justify-content: center !important;
  height: 36px !important;
  min-height: 36px !important;
  min-width: 36px !important;
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 0 12px !important;
  margin: 0 0 0 -1px !important;
  box-shadow: none !important;
  line-height: 1 !important;
}

.dt-container .dt-paging .page-item:first-child .page-link,
.dt-container .dt-paging button.dt-paging-button:first-child {
  margin-left: 0 !important;
}

.dt-container .dt-paging .page-link:hover,
.dt-container .dt-paging .page-link:focus,
.dt-container .dt-paging button.dt-paging-button:hover:not(.disabled):not(.current),
.records .dt-paging button:hover:not(.disabled):not(.current) {
  background-color: #e8eefb !important;
  color: var(--cds-button-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

.dt-container .dt-paging .page-item.active .page-link,
.dt-container .dt-paging button.dt-paging-button.current,
.records .dt-paging button.current {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

.dt-container .dt-paging .page-item.disabled .page-link,
.dt-container .dt-paging button.dt-paging-button.disabled,
.records .dt-paging button.disabled {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* Work Order Billing QC: retain the full-width Bootstrap 3 page geometry.
   The upgraded Bootstrap 5 stack otherwise constrains .Middle to 1140px,
   which shifts the filters, calendar and DataTable to the right and clips
   the export/action columns. */
body:has(#update_qc_frm) .Middle,
body:has(#update_qc_frm) #update_qc_frm,
body:has(#update_qc_frm) #update_qc_frm > div,
body:has(#update_qc_frm) #update_qc_frm > div > .row,
body:has(#update_qc_frm) #update_qc_frm > div > .row > .col-md-12 {
  width: 100% !important;
  max-width: none !important;
  margin-left: 0 !important;
  margin-right: 0 !important;
}

body:has(#update_qc_frm) .Middle {
  float: left !important;
}

body:has(#update_qc_frm) #update_qc_frm .row.mr15.wid-auto {
  width: auto !important;
}

body:has(#update_qc_frm) #update_qc_frm .filter_list.col-sm-3,
body:has(#update_qc_frm) #update_qc_frm .pad-right-0.col-md-3 {
  flex: 0 0 25% !important;
  width: 25% !important;
  max-width: 25% !important;
}

body:has(#update_qc_frm) #update_qc_frm .heading_bold {
  width: 100% !important;
}

body:has(#update_qc_frm) #update_qc_frm .big-table {
  margin-left: auto !important;
  margin-right: auto !important;
}

body:has(#update_qc_frm) #wbwc1 {
  width: 120px !important;
  min-width: 120px !important;
  box-sizing: border-box;
  padding-right: 6px !important;
  padding-left: 6px !important;
  overflow: visible !important;
  text-align: center !important;
}

body:has(#update_qc_frm) .name-sl.ne_title > ul {
  display: flex !important;
  align-items: flex-start !important;
  justify-content: center !important;
}

body:has(#update_qc_frm) .name-sl.ne_title > ul > li {
  flex: 0 0 45px;
}

body:has(#update_qc_frm) .name-sl.ne_title > ul > li.top-date,
body:has(#update_qc_frm) .name-sl.ne_title > ul > li.top-date > p {
  width: 120px !important;
  flex-basis: 120px !important;
}

/* Billing QC table controls: Search + Show entries sit together at the
   top-left (next to the export buttons at top-right), matching the live
   devops reference - confirmed via its DOM/computed styles on 2026-09-03.
   A prior version of this fix assumed devops used a compact single-pager
   toolbar below the grid with First/Last hidden; that assumption was
   wrong (devops shows full Previous/1/Next paging with First/Last visible
   below the grid, and Search/Show above it), so the flex-centering and
   ".first"/".last" display:none rules that enforced it have been removed
   - the corrected `dataTableLayout` in work-order-billing-qc.php now
   places these features in their own slots without needing this CSS to
   force them together. */
body:has(#update_qc_frm) #dataTables-example_wrapper
  > .row:first-child {
  min-height: 66px !important;
  align-items: center !important;
}

body:has(#update_qc_frm) #dataTables-example_wrapper
  > .row:first-child .dt-layout-end {
  height: auto !important;
  align-items: center !important;
}

body:has(#update_qc_frm) #dataTables-example_wrapper
  .dt-buttons .buttons-html5 {
  display: inline-block !important;
  padding: 6.16px 12.32px !important;
  border: 1px solid #999 !important;
  background: #e9e9e9 !important;
  color: #000 !important;
  font-size: 12.32px !important;
  line-height: normal !important;
}

/* Bootstrap 5's table reset removes the Bootstrap 3 cell padding and the
   blue nested-grid heading used by DevOps. Restore it on this grid only. */
body:has(#update_qc_frm) #dataTables-example {
  border: 1px solid #ddd !important;
}

body:has(#update_qc_frm) #dataTables-example > thead > tr > th {
  padding: 8px 18px !important;
  vertical-align: bottom !important;
  background-color: transparent !important;
}

body:has(#update_qc_frm) #dataTables-example > tbody > tr > td {
  padding: 8px !important;
  vertical-align: top !important;
  background-color: transparent !important;
}

body:has(#update_qc_frm) #dataTables-example > tbody > tr > td table > thead > tr > th {
  padding: 8px 18px !important;
  vertical-align: bottom !important;
  background-color: #d9edf7 !important;
}

body:has(#update_qc_frm) #dataTables-example > tbody > tr > td table > tbody > tr > td {
  padding: 8px !important;
  vertical-align: top !important;
  background-color: transparent !important;
}

/* FIX: the "Select All" header checkbox uses the sitewide custom
   ".control--checkbox" pattern, whose ".control__indicator" square is
   "position:absolute; left:10px" (see ".select-all" below) - 10px+20px
   wide reaches 30px into the label, but this label's own inline
   "padding-left:16px" only reserves 16px before its text starts, so the
   indicator's right edge overlaps the first ~14px of "Select All" (the
   "l" in "Select" was rendered under the checkbox box). Confirmed live
   against devops on 2026-09-03: devops renders this with more spacing
   before the text. Widen the reserved padding so the indicator clears
   the text, scoped to this table's header only. */
body:has(#update_qc_frm) #dataTables-example thead .control.control--checkbox {
  padding-left: 34px !important;
}

/* FIX: DataTables 3 layout needs an explicit centered toolbar for Order Management. */
.pending-bury-page #dataTables-example_wrapper
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* Live gray Bootstrap 3 ".btn-default" actions map to Carbon tertiary
   (outlined Blue 60, fill on hover). Markup keeps the class name. */
.btn-default {
  color: var(--cds-button-tertiary, #0f62fe) !important;
  background-color: transparent !important;
  border-color: var(--cds-button-tertiary, #0f62fe) !important;
}

.btn-default:hover,
.btn-default:focus {
  color: #fff !important;
  background-color: var(--cds-button-tertiary-hover, #0353e9) !important;
  border-color: var(--cds-button-tertiary-hover, #0353e9) !important;
}

/* FIX: DataTables 3 needs an explicit centered toolbar on Self QC grids. */
body:has(#img_details_frm):has(#pending_download_table)
  #example8_wrapper
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* Self QC uses Bootstrap 3's fixed-width container and float grid. Restore
   that geometry without affecting the other #example8 tables on the site. */
@media (min-width: 992px) {
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd {
    width: 970px !important;
    max-width: 970px !important;
    padding-right: 15px !important;
    padding-left: 15px !important;
  }

  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd > .row {
    display: block !important;
    margin-right: -15px !important;
    margin-left: -15px !important;
  }

  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd > .row::before,
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd > .row::after {
    display: table;
    content: " ";
  }

  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd > .row::after {
    clear: both;
  }

  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd .col-md-1,
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd .col-md-2,
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd .col-md-4,
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd .col-md-5,
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd .col-md-6,
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd .col-md-12 {
    position: relative;
    float: left !important;
    box-sizing: border-box;
    padding-right: 15px;
    padding-left: 15px;
  }

  body:has(#img_details_frm):has(#pending_download_table) .col-md-1 { width: 8.33333333%; }
  body:has(#img_details_frm):has(#pending_download_table) .col-md-2 { width: 16.66666667%; }
  body:has(#img_details_frm):has(#pending_download_table) .col-md-4 { width: 33.33333333%; }
  body:has(#img_details_frm):has(#pending_download_table) .col-md-5 { width: 41.66666667%; }
  body:has(#img_details_frm):has(#pending_download_table) .col-md-6 { width: 50%; }
  body:has(#img_details_frm):has(#pending_download_table) .col-md-12 { width: 100%; }

  body:has(#img_details_frm):has(#pending_download_table) .col-md-12.p-0 {
    padding-right: 0 !important;
    padding-left: 0 !important;
  }
}

@media (min-width: 1200px) {
  body:has(#img_details_frm):has(#pending_download_table)
    > .container.rtd {
    width: 1170px !important;
    max-width: 1170px !important;
  }
}

body:has(#img_details_frm):has(#pending_download_table) #example8_wrapper {
  width: 100% !important;
  margin-right: 0 !important;
  margin-left: 0 !important;
}

body:has(#img_details_frm):has(#pending_download_table) #example8 thead tr,
body:has(#img_details_frm):has(#pending_download_table) #example8 thead th {
  height: auto !important;
}

body:has(#img_details_frm):has(#pending_download_table) .display-details-cls {
  display: block !important;
}

body:has(#img_details_frm):has(#pending_download_table) .display-details-cls::before,
body:has(#img_details_frm):has(#pending_download_table) .display-details-cls::after {
  display: table;
  content: " ";
}

body:has(#img_details_frm):has(#pending_download_table) .display-details-cls::after {
  clear: both;
}

/* Bootstrap 5's .form-control disables native checkbox appearance. The
   input state was correct, but the checkmark was therefore invisible. */
body:has(#img_details_frm):has(#pending_download_table)
  #example8 input.itemDetails[type="checkbox"].form-control {
  appearance: auto !important;
  -webkit-appearance: checkbox !important;
  display: inline-block !important;
  padding: 0 !important;
  border: 0 !important;
}

/* Schedule Work Order Import's reference layout keeps all three controls on
   one row: search left, record count centered, and export buttons right. */
body:has(#schedule_task):has(#fileToUpload)
  #exampleImport_wrapper
  .dt-layout-full:has(> .dt-search):has(> .dt-length):has(> .dt-buttons) {
  display: flex !important;
  align-items: center !important;
  justify-content: space-between !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
  width: 100% !important;
}

body:has(#schedule_task):has(#fileToUpload)
  #exampleImport_wrapper .dt-search {
  order: 1;
  text-align: left !important;
}

body:has(#schedule_task):has(#fileToUpload)
  #exampleImport_wrapper .dt-search input {
  width: 213px !important;
}

body:has(#schedule_task):has(#fileToUpload)
  #exampleImport_wrapper .dt-length {
  display: flex !important;
  align-items: center !important;
  order: 2;
  white-space: nowrap;
}

body:has(#schedule_task):has(#fileToUpload)
  #exampleImport_wrapper .dt-buttons {
  order: 3;
  float: none !important;
  margin-top: 0 !important;
}

/* Match the legacy DataTables export-button treatment used by DevOps on all
   Schedule Work Order Import views. */
body:has(#schedule_task):has(#fileToUpload)
  :is(#exampleImport_wrapper, #exampleorderImport_wrapper, #examplebulkImport_wrapper)
  .dt-buttons .buttons-html5 {
  margin: 0 .333em 0 0 !important;
  border: 1px solid #999 !important;
  border-radius: 2px !important;
  background: linear-gradient(to bottom, #fff 0%, #e9e9e9 100%) !important;
  color: #000 !important;
  font-size: 12.32px !important;
  line-height: 17.6px !important;
  box-shadow: none !important;
}

body:has(#schedule_task):has(#fileToUpload)
  #exampleImport_wrapper .dt-length select {
  width: 75px !important;
  min-width: 75px !important;
}

/* FIX [FDCM-3547]: hr/general-notice.php's two DataTables ("Recurring
   Notices" #example_103, "Onetime Notice" #example_104 - both init with a
   legacy "dom": 'lBfrtip' string, not the newer "layout" object, so unlike
   #exampleImport_wrapper above they get DataTables 3's flat sibling markup
   (".dt-length", ".dt-buttons", ".dt-search" as plain successive <div>s
   directly under the wrapper, no ".dt-layout-full" row to hang a single
   flex rule on) - reused the sitewide "div.dt-buttons { float: right
   !important; margin-top: -36px !important; }" rule from style-new.css.
   That rule was written for the OLD DataTables 1.x/Bootstrap 3 layout,
   where "l"/"f" rendered inside a shared Bootstrap ".row" and the negative
   margin pulled the Buttons extension and search box up to visually align
   with the length dropdown's row instead of stacking below it. DataTables
   3's Bootstrap 5 build still reuses the ".dt-buttons" class name, so the
   old hack still applies - but there's no ".row" to align within anymore,
   so it just pulls the "Excel Export"/"PDF Export" buttons 36px up into
   the length dropdown directly below them, leaving ~7px between the two
   (confirmed live) instead of the intended shared-row spacing - reading as
   the buttons and dropdown crowding each other.
   Explicit flex + "order" (same tool as the #exampleImport_wrapper fix
   above) rebuilds the intended two-row toolbar without the fragile
   float/negative-margin trick: row 1 is Buttons (left) and Search (pushed
   right via "margin-left: auto"), row 2 is the length dropdown alone
   ("flex-basis: 100%" forces its own line) - matching this page's own
   reference design. The processing indicator, the table itself, and the
   info/paging rows are also direct children of the same wrapper under this
   "dom" string; giving them one shared, later "order" and "flex-basis:
   100%" keeps them full-width and in their own original relative sequence
   below the toolbar (flex preserves DOM order among equal "order"
   values) instead of also being pulled into the flex-wrap row above. */
body:has(#notice_title) #example_103_wrapper,
body:has(#notice_title) #example_104_wrapper {
  display: flex !important;
  flex-wrap: wrap !important;
  align-items: center !important;
  column-gap: 14px !important;
  row-gap: 12px !important;
}

body:has(#notice_title) #example_103_wrapper > .dt-buttons,
body:has(#notice_title) #example_104_wrapper > .dt-buttons {
  order: 1 !important;
  float: none !important;
  position: static !important;
  margin-top: 0 !important;
}

body:has(#notice_title) #example_103_wrapper > .dt-search,
body:has(#notice_title) #example_104_wrapper > .dt-search {
  order: 2 !important;
  margin-left: auto !important;
}

body:has(#notice_title) #example_103_wrapper > .dt-length,
body:has(#notice_title) #example_104_wrapper > .dt-length {
  order: 3 !important;
  flex-basis: 100% !important;
}

body:has(#notice_title) #example_103_wrapper > .dt-processing,
body:has(#notice_title) #example_104_wrapper > .dt-processing,
body:has(#notice_title) #example_103_wrapper > table,
body:has(#notice_title) #example_104_wrapper > table,
body:has(#notice_title) #example_103_wrapper > .dt-info,
body:has(#notice_title) #example_104_wrapper > .dt-info,
body:has(#notice_title) #example_103_wrapper > .dt-paging,
body:has(#notice_title) #example_104_wrapper > .dt-paging {
  order: 4 !important;
  flex-basis: 100% !important;
}

/* Order Management keeps a fixed filter sidebar and reserves its width with
   padding on the main container. DevOps uses a full-viewport Bootstrap 3
   container here; Bootstrap 5's 1320px max-width applies the same inset to a
   much narrower box and leaves only ~1100px for the 1500px orders grid. */
.container.rtd.big-srn.pending-bury-page {
  width: 100% !important;
  max-width: none !important;
  margin-top: -39px !important;
  padding-right: 15px !important;
  margin-right: 0 !important;
  margin-left: 0 !important;
}

.container.rtd.big-srn.pending-bury-page > .Middle {
  float: left !important;
  width: 100% !important;
  max-width: none !important;
}

/* FIX: order-management.php's grid (".order-management-grid", scaled to
   the full ".Middle" width via its own "width:100%" rule) was squeezed
   into the sitewide ".Middle{width:1140px!important}" cap above,
   crushing the DataTables header text together ("Tech IDTechnician",
   "Job #Points" running into each other) and forcing a horizontal
   scrollbar - devops renders this grid edge-to-edge with the "Daily
   Totals" panel, confirmed live on 2026-09-03. This is the exact same
   defect the ".pending-bury-page" rules above already describe in their
   own comment ("Order Management keeps a fixed filter sidebar...1500px
   orders grid") - that comment was written about this page, but the
   selector only ever scoped it to pending-bury-orders.php's own
   ".pending-bury-page" class, so order-management.php itself never
   actually got the fix. Reapplying the same container + Middle pair
   here, scoped to this page's own class. */
.container.rtd.big-srn.order-management-page {
  width: 100% !important;
  max-width: none !important;
  padding-right: 15px !important;
  margin-right: 0 !important;
  margin-left: 0 !important;
}

.container.rtd.big-srn.order-management-page > .Middle {
  float: left !important;
  width: 100% !important;
  max-width: none !important;
}

.pending-bury-page #form_update,
.pending-bury-page #dataTables-example_wrapper {
  width: 100% !important;
  max-width: none !important;
}

.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15 {
  display: block !important;
}

.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15::before,
.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15::after {
  display: table;
  content: " ";
}

.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15::after {
  clear: both;
}

.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15 .col-sm-2,
.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15 .col-sm-4,
.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15 .col-sm-6,
.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15 .col-sm-8 {
  position: relative;
  float: left !important;
  box-sizing: border-box;
  padding-right: 15px !important;
  padding-left: 15px !important;
}

.container.rtd.big-srn.pending-bury-page > .Middle > .row.mr15 > .col-sm-2.flr {
  float: right !important;
}

/* DataTables 3's Bootstrap 5 adapter removes the horizontal header padding
   that separated the labels in DevOps, making pairs such as Tech ID /
   Technician and Job # / Points appear concatenated. */
.pending-bury-page #dataTables-example thead th {
  box-sizing: border-box;
  padding-right: 18px !important;
  padding-left: 18px !important;
}

/* FIX: same "Tech ID/Technician", "Job #/Points" concatenation as the
   ".pending-bury-page" rule above - that rule's own comment names these
   exact column pairs, which only exist on order-management.php, not
   pending-bury-orders.php, so this page never actually received the fix
   its describes. Reapplied here scoped to this page's own class,
   confirmed live against devops on 2026-09-03. */
.order-management-page #dataTables-example thead th {
  box-sizing: border-box;
  padding-right: 18px !important;
  padding-left: 18px !important;
}

/* FIX: DataTables 3 needs a centered responsive toolbar on Work Order Search. */
body:has(#adv_search):has(#sch_text_term)
  #dataTables-example_wrapper
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* FIX: DataTables 3 needs centered responsive controls on invoicing grids. */
body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper,
    #reverted_invoices_modal_table_wrapper
  )
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* FIX: same DataTables-2-vs-Bootstrap-3 pagination color mismatch as the
   "#background-drug_wrapper"/"#pto-request-que_wrapper" blocks above -
   style-new.css's sitewide "ATS brand" rule (search "ATS brand — DataTables
   / Bootstrap pagination") paints every ".dt-paging .page-link" solid blue
   text on white instead of just the active page, so work-orders-invoicing's
   Invoiced/Unbilled/Customer Invoice grids lost their bordered pagination
   buttons and First/boxed-number look devops still has. Scoped via the same
   body:has(#schedule_report):has(#customer_invoiced_table_data) selector as
   the layout fix above (this page reuses "#exampleImport1"/
   "#unbilled_table_data"/"#customer_invoiced_table_data" with other pages),
   Carbon Blue 60 pager, matching carbon-theme.css. Confirmed live against
   devops on 2026-09-04. */
body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-paging {
  display: inline-block !important;
}

body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-paging .page-link:hover,
body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* FIX: devops centers both the "Showing X to Y of Z entries" text and the
   pager underneath the grid; on fdcm they sat flush left. The "layout"
   config for these tables (see woInvoiceDataTableLayout()) puts "info" and
   "paging" in their own separate bottom rows, each rendered as a single
   ".dt-layout-full" flex item that already spans the row's full width (a
   Bootstrap ".col-md" child) - centering the ROW does nothing since there's
   no extra space to distribute around a full-width item. The fix is
   swapping THIS element's own "justify-content: space-between" (a single
   child never needs space-between) for "center", which centers its actual
   text/button content. Confirmed live against devops on 2026-09-04. */
body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-layout-full:has(.dt-info),
body:has(#schedule_report):has(#customer_invoiced_table_data)
  :is(
    #exampleImport1_wrapper,
    #unbilled_table_data_wrapper,
    #customer_invoiced_table_data_wrapper
  )
  .dt-layout-full:has(.dt-paging) {
  justify-content: center !important;
}

/* FIX: DataTables 3 needs centered responsive controls on Final Reconcile. */
body:has(#frm_dectype):has(#fileToUpload)
  #example_wrapper
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* FIX: Bootstrap 5 form controls must remain inline inside reconcile rows. */
body:has(#frm_dectype):has(#fileToUpload) #example tbody td > :is(a, input, img) {
  display: inline-block;
}

/* FIX: DataTables 3 needs centered responsive controls on Pending Bury grids. */
.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* FIX: same "Bootstrap 5 dropped the default float:left on .col-*"
   regression documented throughout this file (see the ".gen"/".qc_mainPrat"
   fixes above) - hr/support-users-settings.php's Office/Departments/Support
   Types picker is three "col-md-4 office_box" divs sitting directly inside
   a bare <fieldset> (no ".row" wrapper, which is where Bootstrap 5's grid
   gutter/float actually lives). Bootstrap 5 still gives each one its
   width:33.3333% (that's set directly on ".col-md-4", not dependent on a
   ".row" parent) but never floats them, so instead of sitting three across
   they stack one per row, each hugging the left edge with the rest of the
   row left blank - exactly the reported screenshot. Restoring float plus
   Bootstrap 3's old per-column gutter padding (Bootstrap 5 puts gutter
   padding on ".row > *" instead, which doesn't match here) puts them back
   three across. "overflow:hidden" on the <fieldset> replaces the
   ".qc_mainPrat" clearfix that only clears ITS OWN direct children, not a
   float nested one level deeper inside <fieldset>, so it would otherwise
   collapse to near-zero height. Scoped via :has(#all_support_notice_types)
   - this page's "Select Employee" <select> id, unique to it - since
   ".qc_mainPrat"/".office_box" are both reused sitewide. */
body:has(#all_support_notice_types) .qc_mainPrat fieldset {
  overflow: hidden;
}
body:has(#all_support_notice_types) .qc_mainPrat .office_box {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* FIX: hr/support-users-settings.php's Select Employee / Support Email /
   Support Phone row was a bare "<table>" with no defined column widths, so
   each "<tr>" sized its own columns purely from that row's own content -
   the row with "Select Employee" (paired with a wide multiselect dropdown)
   and the row below (two short "<h4>" labels paired with plain text
   inputs) ended up with completely different column widths, so nothing
   lined up between the two rows and "Support Email"/"Support Phone" looked
   scattered instead of each label sitting right next to its own field.
   The table was replaced with a flex row of three label+field pairs
   ("support-settings-toprow" > "support-settings-field", see
   hr/support-users-settings.php) so every label sits directly before its
   own input/select, all three pairs on one row. Scoped via
   :has(#all_support_notice_types) - unique to this page. */
body:has(#all_support_notice_types) .support-settings-toprow {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  gap: 28px;
  margin: 40px 0;
}
body:has(#all_support_notice_types) .support-settings-field {
  display: flex;
  align-items: center;
  gap: 10px;
}
body:has(#all_support_notice_types) .support-settings-field h4 {
  margin: 0;
  white-space: nowrap;
}

/* FIX: office/office-info.php's "Add Secondary Office address" row
   (".off-add.off-ad-check") pairs a ".col-sm-5" (the label text) with a
   ".col-sm-1" (the checkbox) directly inside ".gen" - not a ".row" - so
   Bootstrap 5's missing default float on ".col-*" (needs an actual
   ".row" flex parent, same regression fixed repeatedly elsewhere in this
   migration) leaves the checkbox stacking on its own line below the
   text, at the left edge, instead of sitting right next to it like
   uat.i-t-g.net's reference build. Scoped to this specific row via its
   own two classes together so other ".gen"/".col-sm-*" combinations
   elsewhere keep their existing layout. */
.off-add.off-ad-check > .col-sm-5,
.off-add.off-ad-check > .col-sm-1 {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
  box-sizing: border-box;
}

/* FIX: ".upload-date" (style-new.css: "margin-bottom: 50px", plus its
   own "clearfix" class in the markup - a strong signal its children were
   always meant to float) is a shared "Upload File / Effective Date /
   Expiration Date [/ Edit]" row used across ~35 pages sitewide (office-
   info.php, vendor-info.php, client-info.php, medical-facilities.php,
   etc.), pairing several ".col-sm-*" columns directly inside itself -
   not a ".row". Same missing-float-without-a-".row"-parent regression as
   every other instance of this bug fixed in this migration: each column
   (Choose File/Upload button, Effective Date field, Expiration Date
   field, and any trailing "Edit" link) stacks on its own full-width line
   instead of sitting in one row like uat.i-t-g.net's reference build.
   Global (not page-scoped) since the class and the bug are the same
   everywhere it's used. */
.upload-date.clearfix > [class*="col-sm-"] {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
  box-sizing: border-box;
}

/* FIX: same missing-float regression one level deeper inside that same
   shared "Upload File / Effective Date / Expiration Date" widget: each of
   the three columns floated above wraps its own label and field in a
   ".form-inline"/".gen" pair - "<div class="gen"><label class="col-sm-6">
   Add Contract Documents</label><div class="col-sm-6">...</div></div>" -
   again two ".col-sm-6" boxes with no ".row" parent. Without float, the
   label renders on its own line above the field instead of beside it
   (reported on medical-facilities.php; identical markup confirmed on
   vendor-info.php, client-info.php, office-info.php, etc.). Scoped to
   ".upload-date.clearfix .gen" (not a bare ".gen" fix) since ".gen" is
   reused sitewide with row shapes of its own, already covered by other
   page-scoped fixes elsewhere in this file - this only targets the
   ".gen" rows belonging to this specific shared widget. Global (not
   page-scoped) for the same reason as the fix above: the class and the
   bug are the same everywhere this widget is used.

   Deliberately NOT the usual 15px-both-sides gutter used elsewhere in this
   file: this ".gen" is already nested one level inside a ".col-sm-3"/
   ".col-sm-4" column that got its own 15px-both-sides float fix above, and
   Bootstrap's real grid would normally cancel that outer padding via a
   nested ".row"'s -15px margin (there is no ".row" here, per the whole
   premise of this bug). Stacking a second full 15px+15px gutter on top of
   the first left too little room on the narrowest column (End Date, ".col-
   sm-3") for its date-picker "<input>" - itself forced to a fixed ~156px
   "width: auto" by the ".form-inline .form-control" fix further down this
   file - so the input overflowed past the widget's own right edge. A
   single small gap at the label/field seam (instead of full gutters on
   all four edges) keeps every column's usable width close to its floated
   box width, which is enough for that fixed-width input to fit.

   That still left the End Date field's right edge only ~2px from the
   widget's own right edge (no visible margin at all, reported as the
   field "touching the border") - the fixed ~156px input is wider than
   its 50%-of-".gen" field column even with zero padding, so it overflows
   that column regardless, and the End Date column is the outermost one
   (its right edge IS the widget's right edge), so that overflow ran
   straight up against it with nothing left to absorb it. Rather than
   shrinking the input further (it needs to stay wide enough to show a
   full date), the fix below gives that last outer column extra
   padding-right - pushing its whole label+field group left, which gives
   the overflow room to land inside the widget instead of at its edge,
   restoring a normal-looking right margin to match "Add Contract
   Documents"' left margin. */
.upload-date.clearfix .gen > [class*="col-sm-"] {
  float: left;
  padding-left: 0 !important;
  padding-right: 0 !important;
  box-sizing: border-box;
}
.upload-date.clearfix .gen > [class*="col-sm-"]:first-child {
  padding-right: 4px !important;
}
.upload-date.clearfix > [class*="col-sm-"]:last-child {
  padding-right: 45px !important;
}

/* FIX: DataTables 3 needs centered responsive controls on the Postcall Queue. */
body:has(#dataTables-example):has(#call_modal):not(:has(#dataTables-example2))
  #dataTables-example_wrapper
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* FIX: asset-pages/asset-assignment.php — DataTables 3 layout pushed
   paging into a narrow right column so buttons stacked vertically;
   center the bottom toolbar and keep pagination horizontal. */
body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-layout-row:has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  flex-wrap: wrap !important;
  gap: 14px !important;
  width: 100% !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-layout-row:has(.dt-paging)
  .dt-layout-start,
body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-layout-row:has(.dt-paging)
  .dt-layout-end {
  margin-left: 0 !important;
  margin-right: 0 !important;
  width: auto !important;
  flex: 0 0 auto !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging {
  display: inline-block !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging .pagination {
  display: flex !important;
  flex-direction: row !important;
  flex-wrap: wrap !important;
  justify-content: center !important;
  margin-bottom: 0 !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging .page-link {
  background-color: #fff !important;
  color: var(--cds-interactive, #0f62fe) !important;
  border: 1px solid #ddd !important;
  border-radius: 0 !important;
  padding: 6px 12px !important;
  margin-top: 0 !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging .page-link:hover,
body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging .page-link:focus {
  background-color: #eee !important;
  color: var(--cds-link-primary-hover, #0043ce) !important;
  border-color: #ddd !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging .page-item.active .page-link {
  background-color: var(--cds-interactive, #0f62fe) !important;
  color: #fff !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-paging .page-item.disabled .page-link {
  background-color: #fff !important;
  color: #777 !important;
  border-color: #ddd !important;
}

/* FIX: asset-assignment "Show Only entered Quantities" — checkbox was
   labeled control--radio so the custom indicator rendered as a circle. */
body:has(#frm_dectype):has(#onlyQty) .en-de-btn .control.control--checkbox {
  position: relative;
  display: inline-block;
  padding-left: 30px;
  cursor: pointer;
}

body:has(#frm_dectype):has(#onlyQty) .en-de-btn .control.control--checkbox
  .control__indicator {
  border-radius: 0 !important;
  left: 0 !important;
  top: 2px !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-layout-row:has(.dt-search) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  flex-wrap: wrap !important;
  gap: 14px !important;
  width: 100% !important;
}

body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-layout-row:has(.dt-search)
  .dt-layout-start,
body:has(#frm_dectype):has(#onlyQty):has(#VehicleID)
  #dataTables-example_wrapper .dt-layout-row:has(.dt-search)
  .dt-layout-end {
  margin-left: 0 !important;
  margin-right: 0 !important;
  width: auto !important;
  flex: 0 0 auto !important;
}

/* The reference places the result count above a separately centered
   pagination row. */
body:has(#exampleImport):has(#schedule_task)
  :is(#exampleImport_wrapper, #exampleorderImport_wrapper, #examplebulkImport_wrapper)
  .dt-layout-full:has(> .dt-info):has(> .dt-paging) {
  display: flex !important;
  flex-direction: column !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 4px !important;
  width: 100% !important;
}

/* DataTables 3 adds explicit numeric/date alignment and removes the legacy
   table cell padding. DevOps keeps these import grids uniformly centered,
   8px padded, and uses Bootstrap 3's #f9f9f9 odd-row stripe. */
body:has(#exampleImport):has(#schedule_task)
  :is(#exampleImport, #exampleorderImport, #examplebulkImport) :is(th, td) {
  padding: 8px !important;
  text-align: center !important;
}

body:has(#exampleImport):has(#schedule_task)
  :is(#exampleImport, #exampleorderImport, #examplebulkImport).table-striped
  > tbody > tr:nth-of-type(2n+1) > * {
  background-color: #f9f9f9 !important;
  box-shadow: none !important;
}

/* FIX: DataTables 3 bottom controls need one centered responsive row on Billing Reconcile Import. */
.billing-reconcile-import-schedule-page
  :is(#dataTables-example_wrapper, #dtable_schedule_wrapper, #example3_wrapper)
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* FIX: DataTables 3 bottom controls need one centered responsive row on Work Order Billing QC. */
body:has(#dataTables-example):has(#update_qc_frm):not(:has(#dtable_schedule))
  #dataTables-example_wrapper
  .dt-layout-full:has(.dt-length):has(.dt-search):has(.dt-paging) {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
}

/* ================================================================
9. hr/support-routing.php
================================================================ */

/* FIX: same "Bootstrap 5 dropped the default float:left on .col-*"
   regression documented throughout this file (see the ".gen"/".Middle"
   blocks above for the full mechanism) - the Support Type / Add and
   Support Contact rows are each a bare "<div class="form-group
   col-sm-12"><div class="col-sm-4">label</div><div class="col-sm-6">
   select</div><div class="col-sm-2">button</div></div>", never wrapped
   in a ".row". Under Bootstrap 3 these three columns floated left, side
   by side, with a 15px-per-side gutter, so "Support Type"/the dropdown/
   the "Add" button all sit on one line; Bootstrap 5's ".col-sm-*" only
   sets flex-basis/width (no float) and moved the gutter padding onto
   ".row > *" (a child-combinator rule that never matches here), so with
   no ".row" parent the three columns stack label-over-field-over-button
   with no gap instead, confirmed against uat.i-t-g.net's reference
   build. Restoring Bootstrap 3's own float+gutter reproduces it.
   ".form-group.col-sm-12" is reused sitewide (including plain single-
   column rows elsewhere), so rather than promote this globally it's
   scoped via :has(#support_Contact):has(#support_types) - both ids are
   unique to this page's own request (a few near-identical backup/test
   copies of this page also define them, but those aren't part of the
   live app and share this same regression anyway); on this page itself
   every ".form-group.col-sm-12" row is one of these two multi-column
   rows, so no further ":has()" guard is needed. */
body:has(#support_Contact):has(#support_types) .form-group.col-sm-12 > [class*="col-sm-"] {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* FIX: floating ".form-group.col-sm-12"'s children (immediately above)
   pulls them out of normal flow, so the parent - with no other content
   of its own - collapses to zero height instead of wrapping around
   them (the classic "floated children, unclearfixed parent" collapse).
   That left both rows rendering with no real box of their own, so the
   Support Type/Support Contact rows sat with almost no gap between them
   and butted straight up against the grey ".qc_mainPrat" table card
   below with no breathing room at all. "display: flow-root" gives the
   row its own block formatting context so it clears its floated
   children and reports their real height again, same as "overflow:
   hidden" would - but without hidden's side effect of clipping the
   bootstrap-multiselect dropdown panel each "<select>" opens (that
   panel renders taller than the row and escapes its box on purpose;
   "overflow: hidden" here was first tried and silently clipped it to
   nothing, making both dropdowns appear to not open at all). The
   margin restores visible spacing both between the two rows and before
   the table card, matching uat.i-t-g.net's reference build. Same
   scoping as the float fix above - both rules only make sense
   together. */
body:has(#support_Contact):has(#support_types) .form-group.col-sm-12 {
  display: flow-root;
  margin-bottom: 22px;
}

/* FIX: Bootstrap 3's ".table" had no background-color of its own at
   all, so wrapping one in ".qc_mainPrat" (background: #e6e6e6 - see the
   ".qc_mainPrat" rule far above) let that grey card show straight
   through every cell, exactly like uat.i-t-g.net's reference build
   below the Support Type/Support Contact grid. Bootstrap 5's ".table"
   instead sets "--bs-table-bg: var(--bs-body-bg)" (white) and DataTables
   3's Bootstrap 5 adapter paints that variable onto every cell directly
   ("table.table.dataTable>:not(caption)>*>*{background-color:var(--bs-
   table-bg)}" in dataTables.bootstrap5.min.css), so the whole grid
   (header row and every "IT Support"/"Marc Lafleur" data row alike)
   renders solid white instead of the grey card showing through around
   each cell. Overriding the variable back to transparent on this
   table only - scoped via :has(#support_Contact):has(#support_types),
   same as the row-layout fix above - restores the grey card look
   without touching every other ".qc_mainPrat"-wrapped DataTable
   sitewide (several of those are deliberately white bordered grids and
   shouldn't change). */
body:has(#support_Contact):has(#support_types) #example.dataTable {
  --bs-table-bg: transparent !important;
}

/* FIX: same "Bootstrap 5 dropped the default float:left on .col-*"
   regression already fixed above for support-users-settings.php's
   Office/Departments/Support Types picker (see that ".qc_mainPrat
   fieldset"/".office_box" block, scoped via :has(#all_support_notice_types),
   for the full mechanism) - this page's own "Edit Office Routing" panel
   (loaded into "#edit_section" by edit(), see the "$html .= ..." block
   building it server-side) has the exact same shape: three columns -
   "<div class="col-md-4 office_grp1 membors_off">" (Offices Assigned),
   "<div class="col-md-4 office_box boxArea_in">" (Add/Remove), "<div
   class="col-md-4 office_box">" (Available Offices) - sitting directly
   inside a bare "<fieldset>" with no ".row" wrapper. Bootstrap 5 still
   gives each its width:33.3333% but never floats them, so they stacked
   one per row (Add/Remove floating/overlapping over the Offices
   Assigned list box, Available Offices pushed below, Save/Cancel
   detached off to the side) instead of three across like uat.i-t-g.net's
   reference build. Restoring float plus Bootstrap 3's own per-column
   gutter padding puts them back side by side; "display: flow-root" on
   the fieldset (rather than "overflow: hidden", which clipped this
   same page's Select Support Type/Support Contact dropdown panels when
   tried above - see the ".form-group.col-sm-12" fix) clears the floats
   without risking clipping anything similar in here. The first column
   is "office_grp1", not "office_box", so both are targeted; the
   ".office_box" descendant selector also reaches the nested "col-md-12
   office_box" (100%-wide "Offices Assigned" box one level inside the
   first column) same as it does on support-users-settings.php, which
   is harmless since it's already full width. Scoped via
   :has(#support_Contact):has(#support_types), same as this page's other
   fixes above, since ".qc_mainPrat"/".office_box" are both reused
   sitewide. */
body:has(#support_Contact):has(#support_types) .qc_mainPrat fieldset {
  display: flow-root;
}
body:has(#support_Contact):has(#support_types) .qc_mainPrat fieldset > .office_grp1,
body:has(#support_Contact):has(#support_types) .qc_mainPrat .office_box {
  float: left;
  padding-left: 15px;
  padding-right: 15px;
}

/* ================================================================
10. hr/jobs.php
================================================================ */

/* FIX: the "Job Status" Active/Inactive filter row rendered pinned to
   the left edge instead of centered under the "Job Status" label like
   uat.i-t-g.net's reference build. Markup is
   "<div class="en-de-btn middle"><form id="frm_filter_data"
   class="form-inline"><strong><p>Job Status</p></strong><div
   class="form-group"><span>...Active label/input...</span></div><div
   class="form-group"><span>...Inactive...</span></div></form></div>".
   "text-align: center" is already present the whole way down (from
   ".middle"/".en-de-btn" in style-new.css) - that part isn't broken.
   What's missing is Bootstrap 3's own ".form-inline .form-group {
   display: inline-block; ... }" rule (real Bootstrap 3 CSS, applied at
   >=768px): with it, each ".form-group" sat on the same line as an
   inline-block, so the ancestor "text-align: center" centered the pair
   of them as a unit. This "hr" module loads no Bootstrap 3 at all (see
   fdcm-3547-migration-architecture), so ".form-inline" is now an inert
   leftover class and ".form-group" falls back to its plain
   "display: block" (full width) - each radio row becomes its own
   100%-wide block, and the "float: left" already set on the ".control
   control--radio"'s wrapping span (style-new.css's
   ".en-de-btn.middle span" rule) then docks it hard against that
   block's left edge instead of being centered, since floats position
   off the container edge and ignore the parent's text-align. Restoring
   Bootstrap 3's own inline-block behavior on ".form-group" puts the
   two radio rows back on one line and lets the existing
   "text-align: center" center them, confirmed against uat.i-t-g.net's
   reference build. Scoped via :has(#frm_filter_data):has(#dt_for_job_listing) -
   "#frm_filter_data" alone is reused by this same filter widget on
   several other pages (drivers-license-management, vehicle-leasing,
   the recruiting pages, etc.), but "#dt_for_job_listing" is unique to
   this page's own results table. */
body:has(#frm_filter_data):has(#dt_for_job_listing) #frm_filter_data .form-group {
  display: inline-block;
  vertical-align: middle;
  margin-bottom: 0;
}

/* ================================================================
11. hr/support-que.php - "Custom Search" modal (#search_modal)
================================================================ */

/* FIX: the Custom Search popup (opened by the "Custom Search" button,
   markup "<div id="search_modal" ...><form class="form-horizontal"
   id="search_form"><div class="form-group"><label class="control-label
   col-sm-2">Start Date:</label><div class="col-sm-3">...</div><label
   class="control-label col-sm-2">Personnel:</label><div
   class="col-sm-3">...</div></div>...") rendered as a single narrow
   stacked column - one label, then one full-width field, one after
   another - instead of the intended two-label/two-field-per-row layout
   (e.g. "Start Date" / "Personnel" side by side, "End Date" /
   "Department" side by side, etc.) seen on uat.i-t-g.net.
   This is the same root cause as the other pages logged in this file
   (see fdcm-3547-migration-architecture): the markup is pure Bootstrap
   3 grid ("form-horizontal" + "control-label col-sm-2" + "col-sm-3"
   pairs living directly inside ".form-group", with no wrapping ".row").
   In Bootstrap 3 that was enough - ".form-group" was its own clearfix
   context and "col-sm-*" columns floated, so no ".row" ancestor was
   needed. Bootstrap 5's grid replaced floats with flexbox: "col-sm-*"
   only becomes a flex item (and lays out side-by-side) when its parent
   has "display: flex", which normally comes from ".row". Since this
   markup never wraps its columns in a ".row", every "col-sm-3" div
   stays at its plain default "display: block" (confirmed via computed
   style), so each one forces its own full-width line - which is what
   stacked every label/field into its own row. Restoring
   "display: flex; flex-wrap: wrap" on ".form-group" (mirroring what
   ".row" would have supplied) puts each label + its "col-sm-3" field,
   plus the next label + field, back on one row together, matching the
   two-column layout in the reference build.
   Two more knock-on issues fixed in the same pass, both only visible
   once the two-column layout was restored and screenshot-compared
   against uat.i-t-g.net:
   - The modal itself was capped at Bootstrap 5's default
     ".modal-dialog { max-width: 500px }", squeezing the now-two-column
     rows into an unreadably narrow box. This page's own
     "hr/css/index.css" already had "#search_modal .modal-dialog
     { width: 100% }" meant to make it full-width, but "width: 100%" is
     powerless against a "max-width" cap from another rule - so
     "max-width" needs overriding directly.
   - The plain "<select>" fields with no explicit width (Ticket Type,
     Department, and especially Form Field, whose options include some
     very long strings) fell back to browser intrinsic sizing and
     rendered wider than their "col-sm-3" container, overflowing past
     the edge of the modal instead of filling their column like the
     "cs_input"-classed text inputs already do (that class hardcodes
     "width: 300px" in hr/css/index.css). Forcing "width: 100%" on
     selects inside these columns keeps them inside their column like
     every other field.
   Scoped via :has(#search_form):has(#tbl_ticket_list) - "#search_modal"
   itself is a generic id reused by dozens of unrelated pages
   (work-order-pages, payroll, construction, client, etc.) for their own
   differently-structured search modals, but "#search_form" (this
   modal's own form) and "#tbl_ticket_list" (this page's main ticket
   grid, present at initial page load) are both unique to
   hr/support-que.php. */
body:has(#search_form):has(#tbl_ticket_list) #search_modal .modal-dialog {
  max-width: none;
}
body:has(#search_form):has(#tbl_ticket_list) #search_modal .form-group {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  margin-bottom: 15px;
}
body:has(#search_form):has(#tbl_ticket_list) #search_modal .form-group > div.col-sm-3 > select,
body:has(#search_form):has(#tbl_ticket_list) #search_modal .form-group > div.col-sm-3 select {
  width: 100%;
  box-sizing: border-box;
}

/* FIX: the ticket-grid toolbar above "#tbl_ticket_list" (Search input +
   "Filter Ticket type" + "Filter Status" dropdowns + Filter/Clear
   buttons) rendered as one full-width control per line instead of all
   inline on a single row. Markup is "<div class="custom-dropdown
   text-left"><div class="form-inline"><div class="form-group"><input
   id="filter_text" ...></div><div class="form-group"><select
   id="tableTicketTypeFilter" ...></div><div class="form-group"><select
   id="filter_waiting" ...></div><div class="form-group"><button
   class="ticketstablesearch">Filter</button><button
   class="ticketstableresetsearch">Clear</button></div></div></div>" -
   the exact same pattern already fixed for "hr/jobs.php"'s "Job Status"
   filter above (see section 10): Bootstrap 3's own
   ".form-inline .form-group { display: inline-block; ... }" rule (real
   BS3 CSS, >=768px) is what put each ".form-group" on the same line;
   this "hr" module loads no Bootstrap 3 (fdcm-3547-migration-
   architecture), so ".form-group" fell back to plain "display: block"
   and each input/select/button-pair took its own full-width row
   (confirmed via computed style: "display: block", "width: 1045px"
   inside a ~1077px container). Restoring the inline-block behavior
   puts all four groups back on one line. Also restoring Bootstrap 3's
   ".form-inline .form-control { width: auto; }" alongside it - without
   it, BS5's own ".form-control { width: 100% }" would fight the now
   shrink-to-fit ".form-group" and size the input/selects unpredictably
   instead of to their natural content width like the reference build.
   Scoped the same way as the rest of this page's fixes
   (:has(#search_form):has(#tbl_ticket_list)), narrowed further to
   ".form-inline:has(#filter_text)" since "#tbl_ticket_list" is also
   inside the same "body" as an unrelated "#frm_placeholder" form and
   the modal's own "#search_form" (a "form-horizontal", not
   "form-inline", so unaffected anyway) - "#filter_text" pins this rule
   to this one toolbar specifically. */
body:has(#search_form):has(#tbl_ticket_list) .form-inline:has(#filter_text) .form-group {
  display: inline-block;
  vertical-align: middle;
  margin-bottom: 0;
  margin-right: 10px;
}
body:has(#search_form):has(#tbl_ticket_list) .form-inline:has(#filter_text) .form-control {
  display: inline-block;
  width: auto;
  vertical-align: middle;
}

/* FIX: hr/drivers_license_management.php's "Expired / Approaching Expiration /
   Pending Submission / ..." status filter uses Bootstrap 5's
   ".form-check-input[type=radio]" (border-radius: 50%, drawn as a circle), but
   style-new.css carries a sitewide Bootstrap-3-era reset -
   "button, input, select, textarea { border-radius: 3px !important; border:
   1px solid #999 !important; }" - that predates the Bootstrap 5 migration and
   applies to every <input> on every page, including radios. Its !important
   border-radius beats BS5's un-!important 50%, so every ".form-check-input"
   radio sitewide renders as a small rounded square instead of a circle (this
   affects any BS5 radio group, not just this page). Restoring just the shape
   and the checked-state border color (also silently overridden the same way)
   here rather than touching or removing the sitewide reset, which countless
   buttons/inputs/selects still depend on for their borders. */
.form-check-input[type="radio"] {
  border-radius: 50% !important;
}
.form-check-input:checked {
  border-color: #0d6efd !important;
}

/* FIX [FDCM-3547]: hr-settings/support-approvers.php - "Add"/"Delete" button
   clicks show no visual feedback. Root cause is sitewide: style-new.css's
   ".btn-primary { background-color: #2296f3 !important; ... }" has no
   :hover/:focus/:active variant, and Bootstrap 5.3.8 implements those states
   by swapping CSS custom properties (--bs-btn-hover-bg etc.) that the base
   ".btn" rule reads - a flat "!important" background always wins over that
   regardless of state, so no page's .btn-primary ever visibly responds to
   hover/click. That's true everywhere .btn-primary appears, not just here -
   deliberately NOT fixing it sitewide (unlike the analogous .btn-success/
   .btn-default restores above, which reuse Bootstrap 3's own well-known
   default hover shades for those variants). #2296f3 is a custom brand blue
   with no existing darker variant anywhere in style-new.css or this file to
   reuse, and changing every button on the site's hover behavior on a guessed
   color is a bigger call than this one page's report - so scoped to just
   this page via the ".ns-support-approvers" namespace class added to its
   own "<div class="container">" wrapper. Darker shade computed the same way
   Bootstrap 3's own ".button-variant" mixin derives :hover/:active from a
   button's base color: -10% HSL lightness for the background (-12% for the
   border), applied to #2296f3 (hsl(207, 90%, 54%)) rather than sampled from
   a live reference - adjust if it doesn't match the actual brand hover
   color. */
.ns-support-approvers .btn-primary:hover,
.ns-support-approvers .btn-primary:focus,
.ns-support-approvers .btn-primary:active {
  background-color: #0c7bd6 !important;
  border-color: #0b76cd !important;
}

/* ================================================================
12a. HR SETTINGS PAGE-SCOPED UI FIXES
================================================================ */

/* Common typography for the three corrective-action pages. The body
   signatures are unique to each page, preventing the reused #frm_dectype
   id from affecting unrelated HR settings forms. */
:is(
  body:has([name="CNFSupervisorStatement"]),
  body:has(#IssueCorrectiveAction_ID),
  body:has([name="CorrectiveActionTypesResult[]"])
) #frm_dectype,
:is(
  body:has([name="CNFSupervisorStatement"]),
  body:has(#IssueCorrectiveAction_ID),
  body:has([name="CorrectiveActionTypesResult[]"])
) #frm_dectype :is(input, select, textarea, label) {
  font-family: Conv_MyriadPro-Light, "Open Sans", Arial, sans-serif !important;
  color: #222 !important;
}

body:has([name="CorrectiveActionTypesResult[]"]) #frm_dectype table {
  width: 100% !important;
  border-collapse: collapse !important;
}

body:has([name="CorrectiveActionTypesResult[]"]) #frm_dectype :is(th, td) {
  vertical-align: middle !important;
}

/* general-notice-types.php */
.ns-general-notice-types button.Disagree {
  transition: background-color .15s ease, border-color .15s ease, box-shadow .15s ease;
}

.ns-general-notice-types button.Disagree:hover,
.ns-general-notice-types button.Disagree:focus {
  background-color: #0c7bd6 !important;
  box-shadow: 0 0 0 2px rgba(34, 150, 243, .25);
}

.ns-general-notice-types button.Disagree:active {
  background-color: #0969b7 !important;
  box-shadow: inset 0 2px 4px rgba(0, 0, 0, .25);
  transform: translateY(1px);
}

/* ATS reference reserves 50px between the title and first form panel. */
.ns-general-notice-types > .Middle > .heading_bold h2 {
  margin-bottom: 50px !important;
}

/* support-users-settings-new.php */
.ns-support-users-settings-new #ajax_body fieldset {
  display: flex;
  flex-wrap: wrap;
  gap: 15px;
}

.ns-support-users-settings-new #ajax_body .office_box {
  float: none;
  flex: 1 1 300px;
  max-width: 100%;
}

.ns-support-users-settings-new :is(
  .Box-UserW,
  .select_div,
  .box_input,
  #support_email,
  #support_phone
) {
  width: 100%;
  box-sizing: border-box;
}

.ns-support-users-settings-new #upper_tbl {
  max-width: 100%;
  overflow-x: auto;
}

/* support_ticket_form_config.php */
.ns-support-ticket-form-config > .container.rtd.big-srn {
  margin-top: 57px !important;
}

.ns-support-ticket-form-config .rtd > .Middle > .row {
  display: flex;
  flex-wrap: wrap;
}

.ns-support-ticket-form-config .rtd > .Middle > .row > .col-md-3 {
  margin-left: 0 !important;
}

.ns-support-ticket-form-config .rtd > .Middle > .row > .col-md-8 {
  min-width: 0;
  margin-left: 0 !important;
}

.ns-support-ticket-form-config #dropArea {
  width: 100% !important;
  box-sizing: border-box;
}

.ns-support-ticket-form-config .qc_mainPrat > div {
  max-width: 100%;
  overflow-x: auto !important;
}

@media (min-width: 992px) {
  /* The dropdown is rendered by bootstrap-multiselect outside the hidden
     select's zero-height heading wrapper. Use the page's full available
     width for the builder and undo the generic 1140px desktop .Middle cap. */
  .ns-support-ticket-form-config > .container.rtd.big-srn {
    width: 100% !important;
    max-width: none !important;
    margin-right: 0 !important;
    margin-left: 0 !important;
    padding-right: 0 !important;
    padding-left: 0 !important;
  }

  .ns-support-ticket-form-config > .container.rtd.big-srn > .Middle {
    float: none !important;
    width: 100% !important;
    max-width: none !important;
    margin-right: 0 !important;
    margin-left: 0 !important;
  }

  /* Restore this page's Bootstrap 3 grid geometry. The legacy form uses
     explicit 30px/50px column offsets and a 943px design canvas; replacing
     those offsets with a generic flex gap shifted both panels and narrowed
     the canvas. */
  .ns-support-ticket-form-config .rtd > .Middle > .row {
    flex-wrap: nowrap;
  }

  .ns-support-ticket-form-config .rtd > .Middle > .row > .col-md-3 {
    flex: 0 0 25%;
    width: 25%;
    margin-left: 30px !important;
  }

  .ns-support-ticket-form-config .rtd > .Middle > .row > .col-md-8 {
    flex: 0 0 66.66666667%;
    width: 66.66666667%;
    margin-left: 50px !important;
  }

  .ns-support-ticket-form-config #dropArea {
    width: 943px !important;
  }
}

/* FDCM-3547: contain these wide corrective-action tables inside their
   content area on narrow viewports. Do not override .page-link here:
   DevOps intentionally keeps Bootstrap's 6px 12px padding, white
   background, and 1px border around the previous/next arrow images.
   "#example1" is scoped via ".ns-corrective-action-problems" (a plain
   descendant selector now, no ":has()" needed - the namespace class
   already sits on an ancestor of "#example1_wrapper") since 44 other
   pages reuse this id; "#myexample" is left as a bare id since it's
   unique to this one page. */
.ns-corrective-action-problems #example1_wrapper,
body:has(#myexample) #myexample_wrapper,
body:has(#myexample) .adjust-textar {
  max-width: 100%;
  overflow-x: auto;
}

/* FIX [FDCM-3547]: the "overflow-x: auto" fix above (containing this wide
   grid so it can't break the page's own layout) is what makes the
   following bug visible as an actual scrollbar - the grid's own content
   was already overflowing its wrapper even on DevOps, just invisibly,
   since DevOps's "#example1_wrapper" has no overflow containment at all
   ("overflow-x: visible" there, confirmed live) and there happens to be
   enough blank page space to its right to swallow the overflow with no
   scrollbar appearing.
   Root cause: this page's own markup wraps the grid in a
   "<div class="assets_tabil ebel_chek">" (see corrective-action-
   problems.php), reusing a class name from the Assets module's own table
   styling. That module's own "#custom-drop"-style checkbox centering
   hack - ".assets_tabil .control.control--checkbox { left: 36%; }"
   (style-new.css) - was written assuming a narrower checkbox column than
   this page's DataTables-stretched "Enable"/"Disable" columns actually
   render at; a "left: 36%" shift on a "position: relative" element with
   "display: block; width: 100%" pushes the *entire* checkbox label
   (already as wide as its cell) further right by 36% of that same width,
   so it (and DataTables' own 100%-wide table with it) overflows well past
   the cell/table's right edge - confirmed live: at this page's ~260px
   Enable/Disable column width that's a ~94px overflow, accounting for
   essentially all of it.
   Fix: override the inherited ".assets_tabil" rule for just this grid's
   checkboxes, dropping the fragile percentage-based shift in favor of
   letting the already-centered ".gap-part"/table cell (DataTables 3 +
   this page's own ".text-center"/centered th) center a shrink-to-fit
   inline-block checkbox naturally - it can't overflow past its own cell
   this way regardless of column width. Scoped via the same
   ".ns-corrective-action-problems" namespace as the rule above, since
   ".assets_tabil" (and "#example1") are both reused sitewide. */
.ns-corrective-action-problems #example1 .control.control--checkbox {
  display: inline-block !important;
  left: 0 !important;
  width: auto !important;
}

/* FDCM-3547: work-order-pages/billing-reconcile-import_schedule_SP.php's
   "Failed Import Results" modal (#search_modal / table #example3) design
   match. Scoped via ".billing-reconcile-import-schedule-page", a namespace
   class on the modal's own body wrapper - "id=example3"/"#example3_wrapper"
   are reused by hundreds of other pages sitewide, so a bare selector on
   either would leak there too; same reasoning as ".ns-corrective-action-
   problems"/".ns-support-approvers" above. Verified live in the browser
   (this page's local edits don't reflect on the deployed environment, so
   checked by mocking the modal's real markup/JS/CSS in the console against
   the actual live page first) before writing here. */
.billing-reconcile-import-schedule-page {
  position: relative;
}

.billing-reconcile-import-schedule-page .search-modal-close {
  position: absolute;
  top: 4px;
  right: 4px;
  color: #2296f3;
  font-weight: 600;
  font-size: 16px;
  text-decoration: none;
  border: none;
  background: transparent;
  padding: 4px;
}

.billing-reconcile-import-schedule-page .search-modal-close:hover,
.billing-reconcile-import-schedule-page .search-modal-close:focus {
  color: #0c7bd6;
  text-decoration: none;
}

.billing-reconcile-import-schedule-page #example3 thead th {
  background-color: #eaf4fd;
  border: 1px solid #cfe4f7;
  font-weight: 600;
  padding: 10px;
}

.billing-reconcile-import-schedule-page #example3 thead th .dt-column-order::before,
.billing-reconcile-import-schedule-page #example3 thead th .dt-column-order::after {
  opacity: 0.3;
}

.billing-reconcile-import-schedule-page #example3 tbody tr {
  background: #fff;
}

.billing-reconcile-import-schedule-page #example3 tbody td {
  border: 1px solid #e2e2e2;
  padding: 10px 14px;
}

/* FIX: Bootstrap's own "#form-control:disabled" rule (background #e9ecef
   plus a visible border) beats a plain, non-important override regardless
   of selector specificity - confirmed live (the row still showed the gray
   disabled fill and border until !important was added here). Needed to get
   the "plain text in a white card" look instead of a second, inner input
   border nested inside the row's own border. */
.billing-reconcile-import-schedule-page #example3 tbody td input.form-control:disabled {
  border: none !important;
  background: transparent !important;
  box-shadow: none !important;
  padding: 0 !important;
  color: #333 !important;
}

/* "Show N" / Search / pager / "Export To" as one non-wrapping row so the
   pager doesn't fold onto a second line - confirmed live this happened at
   the modal's old (default Bootstrap, ~500px) width; widened via
   "modal-lg" on .modal-dialog (see the page's own HTML), and this backs
   that up regardless of viewport width. */
.billing-reconcile-import-schedule-page #example3_wrapper .row.mt-2.justify-content-between {
  flex-wrap: nowrap;
}

.billing-reconcile-import-schedule-page #example3_wrapper .dt-layout-full {
  flex-wrap: nowrap !important;
  justify-content: flex-start !important;
  gap: 16px;
}

.billing-reconcile-import-schedule-page #example3_wrapper .dt-paging .pagination {
  flex-wrap: nowrap;
  margin: 0;
}

.billing-reconcile-import-schedule-page #example3_wrapper .exportappend2 {
  margin-left: auto;
}

/* ================================================================
13. COMPONENT-LEVEL BOOTSTRAP 3/4 CLASSES - GLOBAL BASELINE (LOW SPECIFICITY)
================================================================ */

/* Added 2026-08-31. Every rule in this section was deliberately left out of
   section 0 the first time around: unlike a plain utility class (a float, a
   text-align, an offset), these are real Bootstrap components with their own
   colors/dimensions/spacing, and this codebase's style-new.css has already
   drifted from stock Bootstrap 3 in undocumented places (see the several
   page-specific ".panel"/".form-inline" overrides further up in this file,
   each verified against that one page's actual look) - so a textbook value
   here isn't guaranteed to match this site's real design everywhere.

   Restoring them anyway, on explicit direction, as a low-specificity GLOBAL
   BASELINE rather than a verified fix: every bare-class selector below is
   less specific than the existing page-scoped overrides elsewhere in this
   file (those use ID-anchored/:has()/compound-class selectors), so on pages
   the team has already verified, this section changes nothing - the more
   specific rule keeps winning. What it does change is every OTHER, not yet
   individually checked use of these classes: instead of rendering with zero
   styling at all (the current state, per the sitewide audit that found
   them), they get Bootstrap 3's own real values (Bootstrap 4's, for the two
   classes marked below that Bootstrap 3 never had) as a reasonable default.
   Treat any of these as a starting point, not a verified match - if a
   specific page still looks wrong, that's the same "verify against the real
   page, patch it there" pattern already used throughout this file, same as
   the ".new_left_bar .panel" / ".form-inline:has(#filter_text)"-style fixes
   above; it'll cleanly override this baseline via specificity, no conflict
   to untangle first. */

/* ---- Panels (Bootstrap 3; renamed/restructured to .card in Bootstrap 4+,
   dropped in 5). Contextual color variants use Bootstrap 3's own default
   palette (its "brand-*" Less variables), same source as everywhere else
   in this file that reuses stock B3 variant colors (e.g. the .btn-default/
   .btn-success restores earlier in this file). */
.panel {
  margin-bottom: 20px !important;
  background-color: #fff !important;
  border: 1px solid transparent !important;
  border-radius: 4px !important;
  box-shadow: 0 1px 1px rgba(0, 0, 0, .05) !important;
}

.panel-body {
  padding: 15px !important;
}

.panel-heading {
  padding: 10px 15px !important;
  border-bottom: 1px solid transparent !important;
  border-top-left-radius: 3px !important;
  border-top-right-radius: 3px !important;
}

.panel-title {
  margin-top: 0 !important;
  margin-bottom: 0 !important;
  font-size: 16px !important;
  color: inherit !important;
}

.panel-footer {
  padding: 10px 15px !important;
  background-color: #f5f5f5 !important;
  border-top: 1px solid #ddd !important;
  border-bottom-right-radius: 3px !important;
  border-bottom-left-radius: 3px !important;
}

.panel-default {
  border-color: #ddd !important;
}

.panel-default > .panel-heading {
  color: #333 !important;
  background-color: #f5f5f5 !important;
  border-color: #ddd !important;
}

.panel-primary {
  border-color: var(--cds-interactive, #0f62fe) !important;
}

.panel-primary > .panel-heading {
  color: #fff !important;
  background-color: var(--cds-interactive, #0f62fe) !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
}

.panel-success {
  border-color: #d6e9c6 !important;
}

.panel-success > .panel-heading {
  color: #3c763d !important;
  background-color: #dff0d8 !important;
  border-color: #d6e9c6 !important;
}

.panel-info {
  border-color: #bce8f1 !important;
}

.panel-info > .panel-heading {
  color: #31708f !important;
  background-color: #d9edf7 !important;
  border-color: #bce8f1 !important;
}

.panel-warning {
  border-color: #faebcc !important;
}

.panel-warning > .panel-heading {
  color: #8a6d3b !important;
  background-color: #fcf8e3 !important;
  border-color: #faebcc !important;
}

.panel-danger {
  border-color: #ebccd1 !important;
}

.panel-danger > .panel-heading {
  color: #a94442 !important;
  background-color: #f2dede !important;
  border-color: #ebccd1 !important;
}

/* ---- Well (Bootstrap 3; dropped outright in Bootstrap 4+, no direct
   replacement - closest is a plain ".card"/".card-body" with padding). */
.well {
  min-height: 20px !important;
  padding: 19px !important;
  margin-bottom: 20px !important;
  background-color: #f5f5f5 !important;
  border: 1px solid #e3e3e3 !important;
  border-radius: 4px !important;
  box-shadow: inset 0 1px 1px rgba(0, 0, 0, .05) !important;
}

/* ---- Thumbnail (Bootstrap 3; dropped outright in Bootstrap 4+, closest is
   a plain ".card" wrapping an image). */
.thumbnail {
  display: block !important;
  padding: 4px !important;
  margin-bottom: 20px !important;
  line-height: 1.42857143 !important;
  background-color: #fff !important;
  border: 1px solid #ddd !important;
  border-radius: 4px !important;
}

/* ---- Navbar hamburger toggle (Bootstrap 3; renamed .navbar-toggler with a
   different icon approach in Bootstrap 4+). */
.navbar-toggle {
  position: relative !important;
  float: right !important;
  padding: 9px 10px !important;
  margin-top: 8px !important;
  margin-right: 15px !important;
  margin-bottom: 8px !important;
  background-color: transparent !important;
  background-image: none !important;
  border: 1px solid transparent !important;
  border-radius: 4px !important;
}

.navbar-toggle .icon-bar {
  display: block !important;
  width: 22px !important;
  height: 2px !important;
  border-radius: 1px !important;
  background-color: #888 !important;
}

.navbar-toggle .icon-bar + .icon-bar {
  margin-top: 4px !important;
}

/* ---- Input group addon (Bootstrap 3; renamed .input-group-text in
   Bootstrap 4+ with a different box model). Aliased to the CURRENT
   Bootstrap 5 ".input-group-text" look rather than Bootstrap 3's own
   table-cell-based values on purpose: the surrounding ".input-group" is
   Bootstrap 5's flex-based one now (that part came with the framework
   upgrade, nothing left of the old table layout to match), so this makes
   ".input-group-addon" a visual alias for its Bootstrap 5 replacement
   instead of reintroducing a table/flex mismatch. */
.input-group-addon {
  display: flex !important;
  align-items: center !important;
  padding: .375rem .75rem !important;
  font-size: 1rem !important;
  font-weight: 400 !important;
  line-height: 1.5 !important;
  color: #212529 !important;
  text-align: center !important;
  white-space: nowrap !important;
  background-color: #e9ecef !important;
  border: 1px solid #ced4da !important;
  border-radius: .375rem !important;
}

/* ---- Labels (Bootstrap 3; renamed/restructured to ".badge" in Bootstrap
   4+, contextual colors changed there too - these keep Bootstrap 3's own
   original palette). */
.label {
  display: inline !important;
  padding: .2em .6em .3em !important;
  font-size: 75% !important;
  font-weight: 700 !important;
  line-height: 1 !important;
  color: #fff !important;
  text-align: center !important;
  white-space: nowrap !important;
  vertical-align: baseline !important;
  border-radius: .25em !important;
}

.label-default {
  background-color: #777 !important;
}

.label-primary {
  background-color: var(--cds-interactive, #0f62fe) !important;
}

.label-success {
  background-color: #5cb85c !important;
}

.label-info {
  background-color: #5bc0de !important;
}

.label-warning {
  background-color: #f0ad4e !important;
}

.label-danger {
  background-color: #d9534f !important;
}

/* ---- Media object (Bootstrap 3; dropped outright in Bootstrap 4+, closest
   is a plain flex layout built by hand). Table-cell based, same as
   Bootstrap 3's own source - not a flex rewrite. */
.media {
  margin-top: 15px !important;
}

.media:first-child {
  margin-top: 0 !important;
}

.media-body,
.media-left,
.media-right {
  display: table-cell !important;
  vertical-align: top !important;
}

.media-body {
  width: 10000px !important;
}

.media-left,
.media > .pull-left {
  padding-right: 10px !important;
}

.media-right,
.media > .pull-right {
  padding-left: 10px !important;
}

.media-object {
  display: block !important;
}

.media-heading {
  margin-top: 0 !important;
  margin-bottom: 5px !important;
}

/* ---- Checkbox/radio wrapper divs (Bootstrap 3; restructured to
   ".form-check" in Bootstrap 4+ with a different markup pattern this
   codebase's existing HTML doesn't use, so that replacement can't just
   apply automatically). */
.checkbox,
.radio {
  position: relative !important;
  display: block !important;
  margin-top: 10px !important;
  margin-bottom: 10px !important;
}

.checkbox label,
.radio label {
  min-height: 20px !important;
  padding-left: 20px !important;
  margin-bottom: 0 !important;
  font-weight: 400 !important;
  cursor: pointer !important;
}

.checkbox input[type="checkbox"],
.radio input[type="radio"] {
  position: absolute !important;
  margin-top: 4px !important;
  margin-left: -20px !important;
}

/* ---- Horizontal-form label (Bootstrap 3; renamed .col-form-label in
   Bootstrap 4+, and only meaningful today paired with ".form-horizontal",
   itself a Bootstrap 3 class with no Bootstrap 5 equivalent). Scoped to the
   ".control-label" class itself (not a bare "label" element) to avoid
   re-styling every plain <label> sitewide, most of which were never
   Bootstrap-3-styled in the first place. */
.control-label {
  display: inline-block !important;
  max-width: 100% !important;
  margin-bottom: 5px !important;
  font-weight: 700 !important;
}

.form-horizontal .control-label {
  padding-top: 7px !important;
  margin-bottom: 0 !important;
  text-align: right !important;
}

/* ---- Inline forms (Bootstrap 3; restructured to flex utility classes in
   Bootstrap 4+, ".form-inline" itself dropped in 5). Real Bootstrap 3
   source, gated behind the same ">=768px" breakpoint Bootstrap 3 used - at
   narrower widths ".form-inline" was identical to a plain stacked form, so
   there's nothing to restore below that width. */
@media (min-width: 768px) {
  .form-inline .form-group {
    display: inline-block !important;
    margin-bottom: 0 !important;
    vertical-align: middle !important;
  }

  .form-inline .form-control {
    display: inline-block !important;
    width: auto !important;
    vertical-align: middle !important;
  }

  .form-inline .input-group {
    display: inline-table !important;
    vertical-align: middle !important;
  }

  .form-inline .input-group .input-group-addon,
  .form-inline .input-group .input-group-btn,
  .form-inline .input-group .form-control {
    width: auto !important;
  }

  .form-inline .input-group > .form-control {
    width: 100% !important;
  }

  .form-inline .control-label {
    margin-bottom: 0 !important;
    vertical-align: middle !important;
  }

  .form-inline .radio,
  .form-inline .checkbox {
    display: inline-block !important;
    margin-top: 0 !important;
    margin-bottom: 0 !important;
    vertical-align: middle !important;
  }

  .form-inline .radio label,
  .form-inline .checkbox label {
    padding-left: 0 !important;
  }

  .form-inline .radio input[type="radio"],
  .form-inline .checkbox input[type="checkbox"] {
    position: relative !important;
    margin-left: 0 !important;
  }
}

/* ---- Deliberately NOT included: ".custom-control"/".custom-checkbox"/
   ".custom-radio"/".custom-switch"/".custom-file" (Bootstrap 4 classes this
   codebase has only ~13 combined uses of). Unlike everything else in this
   section, these aren't purely visual - Bootstrap 4's real implementation
   paired specific CSS with a small JS snippet (updating a custom-file
   input's visible label to the chosen filename, wiring the custom checkbox/
   radio's focus-visible state to its hidden native input). A CSS-only
   restore here would look plausible while quietly not doing that part,
   which is worse than the current honestly-broken state. Left for the same
   case-by-case, verify-the-real-page treatment as the rest of this file's
   history, given how few pages are actually affected. ".custom-select" has
   zero uses found sitewide - nothing to restore. */

/* FIX: hr/drivers_license_management.php's "Send Drivers License Renewal to
   Personnel" modal (#renewdl_modal, its body populated by AJAX from
   include/dl_renew_popup.php) lays out its label/input rows as a bare
   "<table><tr><td>Personnel ID</td><td class="quantitiy"><input></td></tr>"
   with no wrapper grid at all. The CSS this table originally relied on for
   column widths (".quantitiy { width: 15%; float: left; }" in style-new.css)
   has been commented out there for a while, so the label/input columns are
   left entirely to the browser's default table auto-layout - which sizes
   both columns from actual rendered content/control width and doesn't keep
   the label column reliably wide enough for its own longest label. Result:
   "Personnel ID"/"Personnel Name" wrap onto two lines while the other rows'
   shorter first-column content doesn't, and each row's input ends up a
   different width instead of one clean aligned column. Fixing this modal's
   table specifically (rather than reviving the shared, already-dead
   ".quantitiy" rule other markup may not expect back) with a fixed label
   column wide enough for "License Expiration" (its longest label) and
   disabling wrap restores the single two-column layout. */
#renewdl_modal #renewdlform > table td:first-child {
  width: 170px;
  white-space: nowrap;
  vertical-align: middle;
  padding-right: 10px;
}
#renewdl_modal #renewdlform > table td.quantitiy {
  width: auto;
}

/* FIX: in the same "Send Drivers License Renewal to Personnel" modal
   (#renewdl_modal), the Personnel ID / Personnel Name fields
   (include/dl_renew_popup.php) are plain "<input disabled readonly>" with no
   class at all - they're meant to just display read-only data, matching the
   plain white look of every other field on the form. But with no class to
   carry any override, Chrome's native UA stylesheet for disabled inputs wins
   (confirmed via computed style: background-color rgba(239,239,239,.3),
   color #545454), rendering as a faded gray box unlike the rest of the form.
   Restoring a plain white background/normal text color for disabled inputs
   in this modal only. */
#renewdl_modal input:disabled {
  background-color: #fff !important;
  color: #555 !important;
  opacity: 1 !important;
}

/* FIX: "Personnel Documents" page accordion row title break issue */
.faq-cat-content .row {
  width: auto !important;
}

/* FIX: onb/contractor_doc_review.php's page wrapper is a bare
   "<div class="Middle" style="margin:0px; overflow:auto;">" - the exact
   shape the first, unscoped ".Middle" rule higher up in this file (added
   for attendance.php's filter panel) also matches. At >=1366px viewports
   that rule caps ".Middle" at a fixed 1140px and centers it, which left
   this page's Office/Contractor filter table, the Review Pending/Complete/
   Bypassed radios and the DataTable all hugging the left edge of a narrow
   box with a large dead gap on the right (this page's own
   "<div class="container" style="min-width:100% !important;">" already
   neutralizes the separate Bootstrap ".container" max-width cap - per the
   CSS width algorithm, min-width wins over max-width when it's the larger
   value - so this ".Middle" rule was the only remaining cap). Scoped via
   :has(#view_modal_start_contractor), the Start Contractor modal's id,
   unique to this page's family, since #view_modal_start_contractor sits
   as a sibling of ".Middle" (after </div></div>), not a descendant, so
   the :has() has to be anchored on "body" rather than ".Middle" itself. */
body:has(#view_modal_start_contractor) .Middle {
  float: left !important;
  width: 100% !important;
  max-width: 100% !important;
  margin-left: 0 !important;
  margin-right: 0 !important;
}

/* Pending Bury Orders: retain the upgraded date navigator while matching the
   DevOps page geometry and DataTables control placement. */
@media (min-width: 768px) {
  .container.rtd.big-srn.pending-bury-page {
    margin-top: 53px !important;
  }

  .pending-bury-page .pending-bury-main {
    margin-left: 25% !important;
  }

  .pending-bury-page .pending-bury-main .name-sl.ne_title {
    width: 100% !important;
    max-width: none !important;
    text-align: center !important;
  }

  .pending-bury-page .pending-bury-main .name-sl.ne_title > ul {
    display: flex !important;
    align-items: flex-start !important;
    justify-content: center !important;
    width: 100% !important;
  }
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper) {
  width: 100% !important;
  max-width: none !important;
  position: relative !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  table.dataTable thead th {
  box-sizing: border-box;
  height: 44px !important;
  padding: 10px 18px !important;
  text-align: center !important;
  vertical-align: middle !important;
  line-height: 22px !important;
  white-space: normal !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  table.dataTable thead th .dt-column-header {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 5px;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  table.dataTable tbody tr {
  height: 46px !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  table.dataTable tbody td {
  box-sizing: border-box;
  padding: 8px 10px !important;
  text-align: center !important;
  vertical-align: middle !important;
  line-height: 22px !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-layout-row:first-child {
  display: flex !important;
  align-items: center !important;
  justify-content: space-between !important;
  min-height: 48px;
  padding: 5px 10px !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-buttons {
  position: static !important;
  display: flex !important;
  margin: 0 !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-search {
  display: flex !important;
  align-items: center !important;
  gap: 6px;
  margin: 0 !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-search input {
  width: 165px !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-search .btn {
  margin: 0 !important;
  white-space: nowrap;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-layout-row:last-child {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 14px;
  padding: 8px 10px !important;
}

.pending-bury-page #form_search {
  display: flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 4px;
  width: 100% !important;
}

.pending-bury-page .pending-bury-section-title {
  font-size: 22px !important;
  line-height: 1.25 !important;
  margin-top: 10px !important;
  margin-bottom: 6px !important;
}

.pending-bury-page :is(#dataTables-example_wrapper, #dataTables-example2_wrapper)
  .dt-buttons .buttons-html5 {
  background: #fff !important;
  border: 1px solid #999 !important;
  border-radius: 0 !important;
  color: #212121 !important;
  box-shadow: none !important;
  font-size: 12px !important;
  padding: 7px 14px !important;
}

/* Pending Bury order search: Bootstrap 5 otherwise caps this dialog at 500px,
   while the DevOps implementation uses the full available page width. */
.pending-bury-search-modal {
  --bs-modal-width: 100% !important;
}

.pending-bury-search-modal .modal-dialog {
  width: 100% !important;
  max-width: none !important;
  margin: 30px 0 !important;
}

.pending-bury-search-modal .modal-content {
  overflow: hidden !important;
}

.pending-bury-search-modal .modal-body {
  padding: 14px 24px !important;
}

/* Billing Reconciliation Import View: the dense reconciliation grids use
   the full viewport in the reference layout. Override the generic 1140px
   .Middle migration cap on this page only. */
.billing-reconciliation-import-view > #update_frm > .Middle {
  float: left !important;
  width: 100% !important;
  max-width: none !important;
  margin-right: 0 !important;
  margin-left: 0 !important;
}

/* Billing Reconcile Import: retain the centered Bootstrap 3-sized settings
   form while allowing the schedule and import-history grids below it to use
   the full page width shown by the reference implementation. */
.billing-reconcile-import-schedule-page > .Middle {
  float: left !important;
  width: 100% !important;
  max-width: none !important;
  margin-right: 0 !important;
  margin-left: 0 !important;
}

.billing-reconcile-import-schedule-page > .real-page-content.big-table {
  width: 100% !important;
  max-width: none !important;
  margin-right: 0 !important;
  margin-left: 0 !important;
}

@media (min-width: 1200px) {
  .billing-reconcile-import-schedule-page > .Middle > .container {
    width: 1170px !important;
    max-width: 1170px !important;
  }
}

/* Restore the centered, vertically stacked import controls from the legacy
   input-group layout. Bootstrap 5 treats input-group-btn as an unknown inline
   child, which left-aligns this entire block. */
.billing-reconcile-import-schedule-page .total-expenses > .bottom_div,
.billing-reconcile-import-schedule-page .total-expenses > .bottom_div .input-group {
  display: flex !important;
  justify-content: center !important;
  width: 100% !important;
}

/* FIX: DevOps's two ".bottom_div" blocks (upload form, download link) are
   natively "display: inline-block" - the whitespace text node between
   their adjacent closing/opening tags renders as a ~7px gap between them.
   Forcing them to "display: flex; width: 100%" above (to fix the left-
   align regression) collapses that whitespace, so the buttons now sit
   flush against each other. Restored explicitly since it's no longer a
   free byproduct of inline-block layout. */
.billing-reconcile-import-schedule-page .total-expenses > .bottom_div + .bottom_div {
  margin-top: 7px !important;
}

.billing-reconcile-import-schedule-page .total-expenses .input-group-btn,
.billing-reconcile-import-schedule-page #frmimport {
  display: flex !important;
  flex-direction: column !important;
  align-items: center !important;
  width: 400px !important;
}

.billing-reconcile-import-schedule-page #frmimport > .work-type-s {
  width: 100% !important;
}

/* FIX: the sitewide ".fileUpload.btn { border-radius: 0 }" rule assumes
   DevOps renders this button square - confirmed live on THIS page that's
   not the case: DevOps's "Select here to upload..." and "Download Sample
   File" buttons both render at Bootstrap 5's own default radius (4px) and
   16px font, not the 0px/14px this page was getting from the sitewide flat-
   button rules. Restored here, scoped to this page only, so the sitewide
   rule (which may still be correct for other pages) is left untouched. */
.billing-reconcile-import-schedule-page .total-expenses .fileUpload.btn {
  border-radius: 4px !important;
  font-size: 16px !important;
}

/* FIX: the rules this replaces targeted ".dt-layout-row"/".dt-layout-cell" -
   real class names DataTables 3 can generate, but NOT the ones its
   Bootstrap5 adapter actually renders for these two tables (confirmed live,
   directly on the deployed page: the real markup is
   ".row.mt-2.justify-content-between" > ".dt-layout-full"/".dt-layout-
   start"/".dt-layout-end"). Those rules never matched anything, which is
   why the centering never took effect despite being "already fixed" here.
   Scoped to #dtable_schedule_wrapper only (the "Processing/Failed/Qued/
   Done/All" status grid) per current direction - the OTHER grid's missing
   pagination is the slow/hanging "get-reconcile-billing-import.php" call
   (confirmed live: with a fast mock ajax response, its pagination renders
   fine using the *unchanged* existing layout), not a layout/CSS problem,
   so left untouched here.
   "bottomStart"/"bottomEnd" are combined into one "bottom" region (info +
   paging together) in billingReconcileScheduleTableLayout() above so they
   share a single flex row instead of sitting in Bootstrap's
   justify-content-between opposite corners; centered here the same way
   verified earlier on this page's "Failed Import Results" modal (3-track
   grid: info pinned left in track 1, paging centered in track 2, track 3
   left empty to balance it) - confirmed live via getBoundingClientRect,
   0px offset from the row's true center. */
.billing-reconcile-import-schedule-page #dtable_schedule_wrapper
  .row.mt-2.justify-content-between:has(.dt-info, .dt-paging) {
  display: grid !important;
  grid-template-columns: 1fr auto 1fr;
  align-items: center;
}

.billing-reconcile-import-schedule-page #dtable_schedule_wrapper
  .dt-layout-full:has(.dt-info) {
  grid-column: 1;
  justify-self: start;
  margin: 0 !important;
}

.billing-reconcile-import-schedule-page #dtable_schedule_wrapper
  .dt-layout-full:has(.dt-paging) {
  grid-column: 2;
  justify-self: center;
  margin: 0 !important;
}

/* FIX: the sitewide ".dt-buttons .buttons-html5" rule (above) flattens
   every export button to a solid #e9e9e9 fill with square corners and no
   hover/active feedback. DevOps's own Buttons 1.3.1 CSS ("buttons.
   dataTables.min.css", confirmed live) actually renders these with a
   subtle top-to-bottom gradient, 2px corners, and distinct hover/active
   gradients - restored here for this table's Excel/PDF export buttons
   only, leaving the sitewide flat rule (and other pages relying on it)
   untouched. */
.billing-reconcile-import-schedule-page #dtable_schedule_wrapper .dt-buttons .buttons-html5 {
  border-radius: 2px !important;
  background: #e9e9e9 !important;
  background-image: linear-gradient(to bottom, #fff 0%, #e9e9e9 100%) !important;
}

.billing-reconcile-import-schedule-page #dtable_schedule_wrapper .dt-buttons .buttons-html5:hover {
  border: 1px solid #666 !important;
  background: #e0e0e0 !important;
  background-image: linear-gradient(to bottom, #f9f9f9 0%, #e0e0e0 100%) !important;
}

.billing-reconcile-import-schedule-page #dtable_schedule_wrapper .dt-buttons .buttons-html5:active {
  background: #e2e2e2 !important;
  background-image: linear-gradient(to bottom, #f3f3f3 0%, #e2e2e2 100%) !important;
  box-shadow: inset 1px 1px 3px #999 !important;
}

/* FIX: Bootstrap 5 adds "a:not([href]):not([class]) { color: inherit;
   text-decoration: none }" (absent in Bootstrap 3), which this codebase
   never accounted for - it relies heavily on styled "<a onclick=...>"
   elements with neither "href" nor "class" (e.g. work-order-view.php's
   "Show Status" link) that get their color from a more specific
   ancestor-scoped rule like ".heading_bold a { color:#0082ea }". Under
   Bootstrap 5 that ancestor rule loses to the new reset by specificity
   (two ":not()" pseudo-classes outrank one descendant class), so every
   such link renders in plain body-text color instead of blue. Restore
   it, confirmed live against devops on 2026-09-03 (work-order-view.php
   "Show Status": #212121 -> #0082ea). */
.heading_bold a {
  color: #0082ea !important;
  font-weight: 600 !important;
}

/* FIX: the "Order Status" popup (work-order-view.php's "Show Status"
   link, "#order_status_modal") rendered as a cramped, narrow Bootstrap 5
   default modal (max-width:500px, thick flat 10px border, no
   border-radius/box-shadow) with its own inner-cell scrollbars, instead
   of the wide, rounded, soft-shadowed dialog devops uses. Base dialog
   sizing is now restored sitewide further down this file (FDCM-3547);
   these rules keep this modal's own chrome (4px border, radius, shadow)
   on top of that shared sizing. Confirmed live against devops on
   2026-09-03. */
#order_status_modal .modal-dialog {
  width: 80% !important;
  max-width: none !important;
  margin: 30px auto !important;
}

#order_status_modal .modal-content {
  border: 4px solid var(--cds-interactive, #0f62fe) !important;
  border-radius: 14px !important;
  box-shadow: 0 16px 42px rgba(20, 63, 104, 0.22) !important;
  overflow: hidden !important;
}

/* FIX: the "Order Status" grid's header row (loaded via
   ajax/get_order_status_data.php's "#example6") rendered with a
   transparent background, right-aligned text, and the default Bootstrap
   5 heavier font-weight, instead of devops's light-blue header band
   with centered, medium-weight, blue-tinted text. Scoped to this modal
   since "#example6" is reused by other unrelated pages (e.g.
   work-order-settings/work-order-field.php) with their own styling.
   Confirmed live against devops on 2026-09-03. */
#order_status_modal #example6 thead th {
  background-color: #edf6ff !important;
  color: #1f7fbd !important;
  text-align: center !important;
  font-weight: 600 !important;
}

/* FIX: the date filter row in the "Work Order Search" page
   (work-order-pages/work-order-search.php) with their own styling.
   Confirmed live against devops on 2026-09-03. */
.work-order-search .gen.mtb10 {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
}

/* FIX: work-order-pages/work-order-search.php's results grid (#dataTables-
   example, an ID reused sitewide) initializes with a "layout" object
   grouping search + the length dropdown + the Excel/PDF buttons into one
   row and "Showing X to Y of Z entries" + full First/Previous/.../Next/
   Last paging into another - same reference pattern as this file's
   "#exampleImport_wrapper" fix above (schedule-work-order-import.php's
   scheduleImportTableLayout()). DataTables 3's Bootstrap 5 build renders
   each row as a plain ".dt-layout-full" block, stacking its children
   instead of placing them side by side like devops. Reused the exact same
   flex + "order" treatment, scoped to this page's own ".work-order-search"
   wrapper class since "#dataTables-example_wrapper" is not unique. */
.work-order-search #dataTables-example_wrapper .dt-layout-full:has(> .dt-search):has(> .dt-length):has(> .dt-buttons) {
  display: flex !important;
  align-items: center !important;
  justify-content: space-between !important;
  gap: 14px !important;
  flex-wrap: wrap !important;
  width: 100% !important;
}

.work-order-search #dataTables-example_wrapper .dt-search {
  order: 1;
  text-align: left !important;
}

.work-order-search #dataTables-example_wrapper .dt-length {
  display: flex !important;
  align-items: center !important;
  order: 2;
  white-space: nowrap;
}

.work-order-search #dataTables-example_wrapper .dt-buttons {
  order: 3;
  float: none !important;
  margin-top: 0 !important;
}

/* Bottom row: "Showing X to Y of Z entries" above centered pagination,
   matching devops instead of DataTables 3's default stacked-left layout. */
.work-order-search #dataTables-example_wrapper .dt-layout-full:has(> .dt-info):has(> .dt-paging) {
  display: flex !important;
  flex-direction: column !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 4px !important;
  width: 100% !important;
}

/* FIX: work-order-pages/work-orders-invoicing.php's ".container" (no
   ".rtd" wrapper here, unlike most other migrated pages) steps through
   Bootstrap 5's responsive max-width table and lands on 1320px at this
   viewport; DevOps behaves like a Bootstrap 3 container, capped at
   1170px. That extra ~150px cascades down through "Middle" > the
   centered ".col-md-6.offset-md-3" filter form > its "Start Date"/"End
   Date" ".col-md-6" pair, so both date fields end up further apart than
   DevOps. Same root cause and fix as the ".work-type-s" container rule
   above, scoped here to "#wo_invoice_show_log_btn" (unique to this page
   and, unlike "#wo_invoice_all_btn"/"#invoice_by_job", always rendered
   regardless of checkout/permission state) since ".work-type-s" doesn't
   exist on this page. Confirmed live against devops on 2026-09-04. */
.container:has(#wo_invoice_show_log_btn) {
  max-width: 1170px !important;
  padding-left: 15px !important;
  padding-right: 15px !important;
}

/* FIX: the sitewide ".form-control[readonly]" rule earlier in this file
   restores Bootstrap 3's grey "background-color: #eee" for read-only
   fields (confirmed correct there for genuinely non-interactive fields
   like office-info.php's read-only "Office Name"). But a
   ".calendar.ii[readonly]" field is a jQuery UI datepicker input -
   "readonly" here only blocks typing, not clicking to open the picker,
   and DevOps renders it with a plain white background so it doesn't
   read as disabled. Confirmed live on work-orders-invoicing.php's "Start
   Date"/"End Date" fields against devops on 2026-09-04. Not scoped to
   this page: ".calendar.ii[readonly]" is the same reused datepicker
   component sitewide, always with this same click-to-open interaction,
   so every instance should get the same white treatment DevOps gives it
   rather than fixing this one page and leaving the same regression on
   every other page using the identical component. */
.calendar.ii[readonly] {
  background-color: #fff !important;
}

/* FIX: work-order-pages/work-orders-invoicing.php's "Show Log" and
   "View Log" modals (".wo_invoice_checkout_log_modal"'s inline
   "style=width:80%" and "#invoice_status_Log_modal"'s inline
   "style=width:100%") both get capped at Bootstrap 5's default
   ".modal-dialog{max-width:500px}" - "max-width" always wins over a
   smaller "width", so the inline style is powerless against it, same
   root cause as the ".work-type-s" modal fix earlier in this file.
   Without it, "Show Log"'s 5-column table and "View Log"'s 5-column
   table were both squeezed into an unreadably narrow 500px box.
   "#invoice_status_Log_modal" is reused by other, unrelated pages
   (construction/CustomerInvoicing*.php), so it's scoped via
   "#wo_invoice_show_log_btn" (unique to this page, see the ".container"
   fix above); "#wo_invoice_checkout_log_modal" is already unique to
   this page on its own. Confirmed live against devops on 2026-09-04. */
#wo_invoice_checkout_log_modal .modal-dialog {
  max-width: 80% !important;
}

body:has(#wo_invoice_show_log_btn) #invoice_status_Log_modal .modal-dialog {
  max-width: 100% !important;
}

/* FIX: same "#assign_invoice{max-width:500px}" cap as above, but this
   modal's ".modal-dialog" has no inline "width"/"max-width" style at
   all - devops's own plain ".modal-dialog" (no modifier class, no
   inline style) simply has no max-width, so the box fills its ".modal"
   parent (confirmed live: 1905px wide with 0 side margin at this
   viewport, i.e. full-bleed). Bootstrap 5's default 500px cap squeezed
   the "Invoice Line Items" view's plain HTML "<table>" (fixed-width
   "style=width:150px" inputs in "Customer Name"/"Address Line 1"/etc.
   cells) into a box a third that width, so cells overlapped instead of
   sitting in their own row. "#assign_invoice" is reused by dozens of
   unrelated construction/ invoice pages, so scoped the same way as
   "#invoice_status_Log_modal" above. Confirmed live against devops on
   2026-09-04. */
body:has(#wo_invoice_show_log_btn) #assign_invoice .modal-dialog {
  max-width: 100% !important;
}

/* FIX (FDCM-3547, sitewide): Bootstrap 5 caps every ".modal-dialog" at
   "max-width: 500px" (via --bs-modal-width). DevOps's deployed
   style-new.css used ".modal-dialog { width: 80%; margin: 30px auto }"
   with no max-width, which is also how Bootstrap 3 sized dialogs once
   this app's own CSS overrode the 600px default. Width alone cannot
   beat a max-width cap, so tables, col-sm grids, and the 420px
   ajax-upload widget spilled past the blue ".modal-content" border
   (Change Order New Item, search filters, and every other unmarked
   dialog). Restore the devops sizing globally, keep Bootstrap size
   modifiers, and contain overflow so children scroll inside the border
   instead of painting over it.

   Also restore two Bootstrap 3 layout behaviors that only show up
   inside these wider dialogs:
   - ".form-group" rows that hold ".col-*" children but never wrap them
     in a ".row" (BS3 floated columns; BS5 does not, so each column
     stacks). Flex on just those form-groups puts the fields back on
     one row without restyling stacked label-above-input groups.
   - "<input class='btn'>" in a wide table cell: "display: flex /
     inline-flex" on a replaced input fills the cell (stretched
     "Add New Item"). Force width:auto / inline-block on input buttons.

   No !important on dialog width, so inline styles (e.g. Import Task's
   "width: fit-content") and the more-specific per-modal overrides
   above still win. */ 
.modal {
  --bs-modal-width: 80%;
}

.modal-dialog {
  --bs-modal-width: 80%;
  width: 80%;
  max-width: none !important;
  margin: 30px auto;
  box-sizing: border-box;
}

.modal-dialog.modal-sm {
  --bs-modal-width: 300px;
  width: 300px;
  max-width: 300px !important;
}

.modal-dialog.modal-lg {
  --bs-modal-width: 900px;
  width: 900px;
  max-width: 900px !important;
}

.modal-dialog.modal-xl {
  --bs-modal-width: 1140px;
  width: 1140px;
  max-width: 1140px !important;
}

@media (max-width: 767px) {
  .modal-dialog,
  .modal-dialog.modal-sm,
  .modal-dialog.modal-lg,
  .modal-dialog.modal-xl {
    width: auto;
    max-width: none !important;
    margin: 10px;
  }
}

/* Personnel Information: keep every AJAX-loaded section on one centered axis. */
.personnel-information-page {
  width: 100%;
  max-width: 1170px !important;
  margin-left: auto;
  margin-right: auto;
}

.personnel-information-page .Middle.emp-transfer > .container {
  width: 100%;
  max-width: 1170px;
  margin-left: auto;
  margin-right: auto;
}

.personnel-information-page #ajaxResp {
  width: 100%;
  max-width: 1140px;
  margin-left: auto;
  margin-right: auto;
  float: none;
  padding-left: 0;
  padding-right: 0;
}

.personnel-information-page #ajaxResp > #frm_dectype {
  display: block;
  width: 100%;
  max-width: 1110px;
  margin-left: auto;
  margin-right: auto;
}

.FedMainBoxL.custo_info .FedInpMain .FedISec input[type="text"] {
  border: none !important;
}

.gap-div td:nth-child(odd) {
  padding-left: 20px;
}

.personnel-information-page .last-btn .save-btn:nth-child(2) button {
  color: #fff !important;
}

@media (max-width: 767px) {
  .personnel-information-page,
  .personnel-information-page .Middle.emp-transfer > .container,
  .personnel-information-page #ajaxResp {
    width: 100%;
    max-width: none;
    padding-left: 10px !important;
    padding-right: 10px !important;
  }

  .personnel-information-page #ajaxResp > #frm_dectype {
    max-width: none;
  }
}

/* Badge Type / Personnel Status Type: separate Search from pagination. */
.badge-type-page #example_wrapper .dt-search,
.personnel-status-type-page #examplenew_wrapper .dt-search {
  margin-right: 12px !important;
}

/* Personnel Status Type intentionally uses 90%-wide nested containers.
   Remove Bootstrap 5's desktop max-width cap so it matches the legacy page. */
.personnel-status-type-page,
.personnel-status-type-page .Middle.payrl.bonus-category > .container {
  max-width: none !important;
}

.personnel-status-type-page #examplenew_wrapper .dt-table-scroll,
.personnel-status-type-page #examplenew_wrapper .dt-scroll-body,
.personnel-status-type-page #examplenew_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

/* Personnel Status Type: Header Menu Permission modal. */
body:has(.personnel-status-type-page) #personnel_status_modal .modal-dialog {
  width: min(760px, calc(100% - 30px)) !important;
  max-width: 760px !important;
}

body:has(.personnel-status-type-page) #personnel_status_modal .modal-content {
  max-height: calc(100vh - 40px);
  overflow: hidden;
}

body:has(.personnel-status-type-page) #personnel_status_modal .personnel-status-permission-header {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  min-height: 58px;
  border-bottom: 1px solid #ddd;
}

body:has(.personnel-status-type-page) #personnel_status_modal .modal-title {
  width: 100%;
  margin: 0;
  text-align: center;
}

body:has(.personnel-status-type-page) #personnel_status_modal .btn-close {
  position: absolute !important;
  top: 50% !important;
  transform: translateY(-50%);
}

body:has(.personnel-status-type-page) #personnel_status_modal .modal-body {
  overflow-y: auto;
}

body:has(.personnel-status-type-page) #personnel_status_modal .filter_list.qc_mainPrat {
  margin: 0;
}

body:has(.personnel-status-type-page) #personnel_status_modal #SelectText {
  display: block;
  margin: 0 0 10px;
  padding-left: 0;
}

body:has(.personnel-status-type-page) #personnel_status_modal .permission-menu-row-inner {
  display: grid;
  grid-template-columns: minmax(0, 1fr) 48px;
  align-items: center;
  gap: 12px;
  width: 100%;
}

body:has(.personnel-status-type-page) #personnel_status_modal :is(.permission-menu-name, .permission-menu-check) {
  width: auto;
  padding: 0;
  margin-bottom: 10px;
}

body:has(.personnel-status-type-page) #personnel_status_modal .permission-menu-check {
  align-items: center;
  justify-content: center;
  min-height: 38px;
}

body:has(.personnel-status-type-page) #personnel_status_modal .permission-menu-check .control {
  margin: 0;
}

#personnel_status_modal button.btn-link {
  border: none !important;
}

#personnel_status_modal button.btn-default {
  background-color: #0f62fe !important;
  color: hsl(0, 0%, 100%) !important;
  border-color: #0f62fe !important;
}

@media (max-width: 768px) {
  .badge-type-page #example_wrapper .records,
  .personnel-status-type-page #examplenew_wrapper .records {
    display: flex;
    align-items: center;
    justify-content: center;
    flex-wrap: wrap;
    gap: 8px;
  }

  .badge-type-page #example_wrapper .dt-search,
  .personnel-status-type-page #examplenew_wrapper .dt-search {
    margin-right: 0 !important;
  }

  .container.personnel-status-type-page,
  .personnel-status-type-page .Middle.payrl.bonus-category > .container,
  .personnel-status-type-page .work-regions,
  .personnel-status-type-page .real-page-content {
    width: 100% !important;
  }
}

.modal-content {
  max-width: 100%;
  box-sizing: border-box;
  overflow-x: auto;
}

.modal-body {
  max-width: 100%;
  min-width: 0;
  box-sizing: border-box;
  overflow-x: auto;
}

.modal-body .table,
.modal-body table {
  max-width: 100%;
}

.modal-body .form-control,
.modal-body select,
.modal-body .form-select,
.modal-body .select2-container {
  max-width: 100%;
  box-sizing: border-box;
}

.modal .ajax-upload-dragdrop,
.modal [id^="fileuploader"] {
  max-width: 100%;
  box-sizing: border-box;
}

.modal .form-group:has(> [class*="col-"]) {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
}

.modal .form-group:has(> [class*="col-"]) > [class*="col-"] {
  box-sizing: border-box;
  min-width: 0;
  max-width: 100%;
}

.modal .form-group:has(> [class*="col-"]) .form-control,
.modal .form-group:has(> [class*="col-"]) select {
  width: 100%;
  max-width: 100%;
  box-sizing: border-box;
}

.modal input.btn,
.modal input[type="button"],
.modal input[type="submit"] {
  width: auto !important;
  max-width: 100%;
  display: inline-block !important;
}

/* Boxed modal "X" links ("<a class='btn btn-default'>X</a>") keep the
   Bootstrap/Carbon button border. Strip it sitewide; modal-close.js
   also promotes these to .erp-modal-close once data-bs-dismiss is
   treated like data-dismiss. */
.modal a.btn.btn-default[data-dismiss="modal"],
.modal a.btn.btn-default[data-bs-dismiss="modal"],
.modal a.btn.btn-secondary[data-dismiss="modal"],
.modal a.btn.btn-secondary[data-bs-dismiss="modal"],
.modal a.btn.erp-modal-close,
.modal .erp-modal-close.btn {
  background: transparent !important;
  border: 0 !important;
  border-color: transparent !important;
  box-shadow: none !important;
  color: #2296f3 !important;
}

/* FDCM-3547: notice modals (class erp-notice-modal: Support, Approval, Issue
   Corrective Action, Contractor Recruiting, PAN, Expense Approval, Badge Expiry)
   render row actions as ".save-btn > a.btn.btn-default" View / OK links. The X-link
   reset above (and its carbon-theme.css twin) caught every one carrying
   data-dismiss and turned it into bare text; the rest fell through to Carbon's
   outlined .btn-default. Show them as filled buttons like ATS, in the FDCM blue. */
.modal.erp-notice-modal .save-btn > a.btn.btn-default {
  display: block !important;
  background: var(--cds-button-primary, #0f62fe) !important;
  border: 1px solid var(--cds-button-primary, #0f62fe) !important;
  color: var(--cds-text-on-color, #fff) !important;
  border-radius: 3px !important;
  padding: 5px 33px !important;
  text-align: center;
  text-decoration: none !important;
  box-shadow: none !important;
}

.modal.erp-notice-modal .save-btn > a.btn.btn-default:hover,
.modal.erp-notice-modal .save-btn > a.btn.btn-default:focus {
  background: var(--cds-button-primary-hover, #0043ce) !important;
  /* full border, not just border-color: carbon-theme.css's dismiss-link :hover sets
     border:0 !important, which shrank OK (data-dismiss) by 2px on hover. */
  border: 1px solid var(--cds-button-primary-hover, #0043ce) !important;
  color: var(--cds-text-on-color, #fff) !important;
}

/* Some pages style every ".save-btn" for their own button rows (e.g.
   construction-project-summary.php: "display:flex !important; margin-left:40%";
   project-qc*.php: "display:inline-block"), which squeezed the notice-modal
   View/OK wrappers and pushed them off-centre. Keep them full-width blocks. */
.modal.erp-notice-modal td > .save-btn {
  display: block !important;
  margin-left: 0 !important;
  float: none !important;
}

/* FDCM-3547: "Acknowledge All" header checkbox. style-new.css puts the box at
   left:30px, past the edge of its 15%-wide float, so it lands on the
   "Acknowledge All" text (footer.php had per-modal left: nudges for a few of
   these). Pin the box -- and the invisible input that takes the click -- to the
   right edge of its float instead, leaving a gap before the text. */
.modal.erp-notice-modal h2 .control--checkbox input,
.modal.erp-notice-modal h2 .control--checkbox .control__indicator {
  left: auto !important;
  right: 8px !important;
}

/* Pages that load payroll.css get ".control--checkbox { margin-left:-20px; left:30% }",
   which shifts and stretches the label past its float, so the box pinned above
   landed on "Acknowledge All" again (e.g. manage-invoices.php,
   contractor_recruiting.php). Keep the label inside its float. */
.modal.erp-notice-modal h2 .control--checkbox {
  margin-left: 0 !important;
  left: 0 !important;
}

/* FDCM-3547: notice-modal grids put the pager right against the search box.
   margin-top: pages that load que-local.css get ".form-control { margin-top:-5px }",
   and the grid's overflow:auto .records row clipped the top 5px of the box. 1px is
   what the modal already gets everywhere else (style-new.css .form-control).
   (The "Search" placeholder is set by js/modal-close.js.) */
.modal.erp-notice-modal .dt-search input {
  margin-top: 1px !important;
  margin-right: 12px !important;
}

/* Recruit Data modal (onb/recruting_live.php): style-new.css
   "td input:not([type=radio]) { width: 97% }" stretches the Notes Add
   control and action buttons to the full cell. Keep the classic compact
   row. Honor inline display:none on Send Offer Letter / View Application /
   Re-generate so they stay hidden until the page makes them visible. */
#recruit_modal td input.btn,
#recruit_modal td input[type="button"],
#recruit_modal td input[type="submit"] {
  width: auto !important;
  max-width: none !important;
  height: auto !important;
  min-height: 0 !important;
  margin-bottom: 4px !important;
  display: inline-block !important;
  white-space: nowrap !important;
  box-sizing: border-box;
}

#recruit_modal td.quantitiy input.btn,
#recruit_modal td.quantitiy input[type="button"] {
  width: auto !important;
  display: inline-block !important;
}

#recruit_modal .row > [class*="col-"] > table {
  width: auto !important;
  max-width: 100%;
}

#recruit_modal .row > [class*="col-"] > table td {
  width: auto !important;
  white-space: nowrap;
  padding-right: 8px;
  vertical-align: middle;
}

#recruit_modal input.btn[style*="display:none"],
#recruit_modal input.btn[style*="display: none"],
#recruit_modal input[type="button"][style*="display:none"],
#recruit_modal input[type="button"][style*="display: none"] {
  display: none !important;
}

/* FIX (FDCM-3547): absence-reason.php layout and modal parity with
   DevOps. These rules are page-scoped to preserve the existing theme. */
.absence-reason-page #example_wrapper .records .dt-search {
  margin-right: 10px !important;
}

.absence-reason-page .dt-table-scroll, 
.absence-reason-page  .dt-container div:has(> table.dataTable) {
  overflow-x: hidden !important;
}

/* FIX (FDCM-3547): supervisor-groups.php layout and modal parity with
   DevOps. These rules are page-scoped to preserve the existing theme. */
.supervisor-groups-page.container,
.supervisor-groups-page .container.Middle,
.supervisor-groups-page .sup-tab,
.supervisor-groups-page #example5_wrapper {
  width: 100% !important;
  max-width: none !important;
}

.supervisor-groups-page #example5_wrapper .dt-table-scroll,
.supervisor-groups-page #example5_wrapper .dt-scroll-body,
.supervisor-groups-page #example5_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

.supervisor-groups-page .EmployeeTop_box {
  width: min(836px, 100%) !important;
}

.supervisor-groups-page .EmpTBoxR {
  display: flex;
  align-items: flex-start;
  flex-wrap: nowrap;
  gap: 5px;
}

.supervisor-groups-page .EmpTBoxR .btn-group,
.supervisor-groups-page .EmpTBoxR .multiselect { min-width: 0; }

.supervisor-groups-page .EmpTBoxR .small-add {
  flex: 0 0 auto;
  white-space: nowrap;
}

.supervisor-groups-page .small-adding {
  color: #fff !important;
  background-color: #0f62fe !important;
  border-color: #0f62fe !important;
}

.supervisor-groups-page #example5_wrapper .records {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 8px;
}

.supervisor-groups-page #example5_wrapper .records > div,
.supervisor-groups-page #example5_wrapper .records .dt-search,
.supervisor-groups-page #example5_wrapper .records .dataTables_filter,
.supervisor-groups-page #example5_wrapper .records .dt-paging,
.supervisor-groups-page #example5_wrapper .records .dataTables_paginate {
  float: none !important;
  margin: 0 !important;
}

.supervisor-groups-page #example5_wrapper .dt-search input,
.supervisor-groups-page #example5_wrapper .dataTables_filter input {
  margin: 0 0 0 4px !important;
}

/* Supervisor Groups: center the action-column headings only. */
.supervisor-groups-page #example5.dataTable thead th.dt-head-center .dt-column-title {
  padding-left: 20px;
}

body:has(.supervisor-groups-page) #manageOfficeModal .modal-dialog {
  width: min(700px, calc(100% - 30px));
}

body:has(.supervisor-groups-page) #manageOfficeModal .modal-content { min-height: 560px; }

body:has(.supervisor-groups-page) #manageOfficeModal .modal-body {
  min-height: 430px;
  overflow: visible;
}

body:has(.supervisor-groups-page) #manageOfficeModal .multiselect-container {
  max-height: 360px !important;
}

body:has(.supervisor-groups-page) #manage_modal #sp_tbl { width: 100% !important; }

body:has(.supervisor-groups-page) #manage_modal #sp_tbl thead th {
  color: #1685d1;
  background: #edf7ff;
  border-bottom: 1px solid #c9e3f7;
  text-align: center;
  white-space: nowrap;
}

body:has(.supervisor-groups-page) #manage_modal #sp_tbl_wrapper .dt-search,
body:has(.supervisor-groups-page) #manage_modal #sp_tbl_wrapper .dataTables_filter {
  margin: 12px 0 !important;
}

@media (max-width: 767px) {
  .supervisor-groups-page .EmpTBoxR {
    align-items: stretch;
    flex-wrap: wrap;
  }

  .supervisor-groups-page .EmpTBoxR .btn-group {
    flex: 1 1 100%;
    width: 100%;
  }

  .supervisor-groups-page .EmpTBoxR .multiselect { width: 100% !important; }
  .supervisor-groups-page .sup-tab { overflow-x: auto; }

  body:has(.supervisor-groups-page) #manageOfficeModal .modal-content,
  body:has(.supervisor-groups-page) #manageOfficeModal .modal-body { min-height: 520px; }
}

/* The shared calendar is appended to body; keep it above the pay-setup modal
   (z-index: 99999) only while that modal is open on contractor groups. */
body:has(#exampleContractorGroup1):has(#myModal.show) #ui-datepicker-div {
  z-index: 100000 !important;
}

/* Let the contractor grid fit its rows and controls without a fixed blank area. */
body:has(#exampleContractorGroup1)
  .qc_mainPrat.assets_tabil.sup-tab:has(#exampleContractorGroup1) {
  height: auto !important;
  min-height: 0;
  max-height: none !important;
  overflow-y: hidden !important;
}

@media (max-width: 767px) {
  body:has(#exampleContractorGroup1)
    .qc_mainPrat.assets_tabil.sup-tab:has(#exampleContractorGroup1) {
    min-height: 0;
    overflow-x: auto !important;
    overflow-y: hidden !important;
  }
}

/* FIX (FDCM-3547): custom-groups.php's Edit Group Members section used
   Bootstrap 3 floated columns through an intervening form. Bootstrap 5 no
   longer floats those columns, which breaks the three-column transfer layout.
   Restore that layout without changing the page's existing theme colors. */
.custom-groups-page .qc_mainPrat:has(#user-list):has(#user2-list) fieldset,
.custom-groups-page .qc_mainPrat:has(#user-list):has(#user2-list) .membors_off {
  width: 100%;
  min-width: 0;
}

.custom-groups-page .qc_mainPrat:has(#user-list):has(#user2-list) .membors_off {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
}

.custom-groups-page .membors_off > form,
.custom-groups-page .membors_off > .office_box {
  min-width: 0;
  box-sizing: border-box;
}

.custom-groups-page .membors_off > form > .office_box {
  width: 100% !important;
  max-width: none;
}

.custom-groups-page .Box-UserW,
.custom-groups-page .select_div {
  width: 100%;
  min-width: 0;
}

.custom-groups-page :is(#user-list, #user2-list) :is(.user-item, .user-item2) {
  display: flex;
  align-items: center;
  width: 100%;
  min-width: 0;
}

.custom-groups-page :is(#user-list, #user2-list) :is(.user-item, .user-item2) > .control {
  position: relative;
  flex: 0 0 24px;
  width: 24px;
  min-width: 24px;
  height: 24px;
  margin: 0;
  padding: 0;
}

.custom-groups-page :is(#user-list, #user2-list) :is(.user-item, .user-item2)
  > .control > .checktxt {
  display: none !important;
}

.custom-groups-page :is(#user-list, #user2-list) :is(.user-item, .user-item2)
  > .control > .control__indicator {
  top: 0 !important;
  right: auto !important;
  left: 0 !important;
}

.custom-groups-page :is(#user-list, #user2-list) .box_lable {
  float: none !important;
  flex: 1 1 auto;
  width: auto;
  min-width: 0;
  padding-left: 10px !important;
  overflow-wrap: anywhere;
}

.custom-groups-page .boxArea_in .button_bx {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 10px;
}

.custom-groups-page .boxArea_in .button_bx br { display: none; }

@media (min-width: 768px) {
  .custom-groups-page .membors_off > form,
  .custom-groups-page .membors_off > .office_box {
    flex: 0 0 33.333333%;
    width: 33.333333%;
    max-width: 33.333333%;
  }
}

@media (max-width: 767px) {
  .custom-groups-page .qc_mainPrat:has(#user-list):has(#user2-list) {
    overflow-x: hidden;
  }

  .custom-groups-page .membors_off > form,
  .custom-groups-page .membors_off > .office_box {
    flex: 0 0 100%;
    width: 100%;
    max-width: 100%;
  }

  .custom-groups-page .boxArea_in .button_bx {
    flex-direction: row;
    padding: 16px 0;
  }
}

/* FIX (FDCM-3547): position-title.php sizing and DataTables parity with
   DevOps. All selectors are page-scoped and retain the existing palette. */
body:has(.position-title-page) > .container,
.position-title-page,
.position-title-page > .container,
.position-title-page .work-regions,
.position-title-page .real-page-content,
.position-title-page #frm_dectype,
.position-title-page #example_title_wrapper {
  width: 100% !important;
  max-width: none !important;
}

.position-title-page .work-regions > .qc_mainPrat:first-child {
  width: 100% !important;
  min-width: 0;
}

.position-title-page #form table {
  width: 100% !important;
  table-layout: auto;
}

/* Bootstrap 5 contributes a background chevron while the browser also draws
   the native select arrow. Keep only the native arrow used on DevOps. */
.position-title-page #form #ManagementLevel,
.position-title-page #form #LaborCategory,
.position-title-page #frm_dectype select[name^="ManagemetLevel-"],
.position-title-page #frm_dectype select[name^="LaborCategory-"] {
  background-image: none !important;
  appearance: auto !important;
  -webkit-appearance: menulist !important;
}

.position-title-page .real-page-content > .qc_mainPrat {
  width: 100% !important;
  min-height: 510px;
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

.position-title-page #frm_dectype .records,
.position-title-page #example_title_wrapper {
  max-height: none !important;
  overflow-y: hidden !important;
}

.position-title-page #example_title_wrapper .records {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 8px;
}

.position-title-page #example_title_wrapper .records > div,
.position-title-page #example_title_wrapper .dt-search,
.position-title-page #example_title_wrapper .dataTables_filter,
.position-title-page #example_title_wrapper .dt-paging,
.position-title-page #example_title_wrapper .dataTables_paginate {
  float: none !important;
  margin: 0 !important;
}

.position-title-page #example_title_wrapper .dt-search input,
.position-title-page #example_title_wrapper .dataTables_filter input {
  margin: 0 0 0 4px !important;
}

body:has(.position-title-page) #position_title_description_modal .modal-title {
  width: 100%;
  text-align: center !important;
}

body:has(.position-title-page) :is(#position_title_description_modal, #position_title_log_modal) .modal-header {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
}

body:has(.position-title-page) :is(#position_title_description_modal, #position_title_log_modal) .modal-header .close {
  position: absolute !important;
  top: 50% !important;
  right: 15px !important;
  left: auto !important;
  float: none !important;
  margin: 0 !important;
  transform: translateY(-50%);
}

body:has(.position-title-page) #position_title_log_modal .modal-title {
  width: 100%;
  text-align: center !important;
}

/* The filter multiselect already renders its own .caret element. Suppress the
   Bootstrap 5 dropdown-toggle pseudo-caret so only one icon is visible. */
.position-title-page .position-title-filter-btn-group .multiselect.dropdown-toggle::after {
  display: none !important;
  content: none !important;
}

.position-title-page .en-de-btn > ul {
  display: flex !important;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 10px 20px;
}

.position-title-page .en-de-btn > ul > li,
.position-title-page .position-title-view-filter,
.position-title-page .position-title-view-filter form {
  display: inline-flex !important;
  align-items: center;
  margin-top: 0 !important;
}

.position-title-page .position-title-view-filter {
  gap: 8px;
  flex: 0 0 100% !important;
  width: 100%;
  justify-content: center;
}

.position-title-page .position-title-view-filter form {
  gap: 12px;
}

.position-title-page .en-de-btn > ul > li > label {
  margin-right: 4px;
}

body:has(.position-title-page) #frm_dectype > .records,
body:has(.position-title-page) #example_title_wrapper,
body:has(.position-title-page) #example_title_wrapper :is(.dt-scroll, .dt-scroll-body, .dataTables_scroll, .dataTables_scrollBody) {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

body:has(.position-title-page) #position_title_log_modal #position_title_log_table {
  overflow-x: auto !important;
}

body:has(.position-title-page) #position_title_log_modal #status_log_table {
  width: 100% !important;
  table-layout: fixed;
}

body:has(.position-title-page) #position_title_log_modal #status_log_table thead th {
  color: #1685d1;
  background: #edf7ff;
  border-bottom: 1px solid #c9e3f7;
  text-align: center;
}

body:has(.position-title-page) #position_title_log_modal #status_log_table th:nth-child(1),
body:has(.position-title-page) #position_title_log_modal #status_log_table td:nth-child(1) { width: 27%; }

body:has(.position-title-page) #position_title_log_modal #status_log_table th:nth-child(2),
body:has(.position-title-page) #position_title_log_modal #status_log_table td:nth-child(2) { width: 27%; }

body:has(.position-title-page) #position_title_log_modal #status_log_table th:nth-child(3),
body:has(.position-title-page) #position_title_log_modal #status_log_table td:nth-child(3) { width: 46%; }

body:has(.position-title-page) #position_title_log_modal #status_log_table tbody td {
  vertical-align: top;
  overflow-wrap: anywhere;
}

body:has(.position-title-page) div.position-title-filter-btn-group .btn.btn-secondary {
  background-color: #fff;
  color: #000;
}

body:has(.position-title-page) .dt-table-scroll,
body:has(.position-title-page) .dt-container div:has(> table.dataTable) {
  overflow-y: hidden;
}

/* FIX (FDCM-3547): contractor-groups.php edit/view subpages lost their
   Bootstrap 3 column layout after the upgrade. Restore the member transfer
   row and the 9/3 content/sidebar split without altering the theme palette. */
body:has(#exampleContractorGroup1) .contractor-group-edit-left,
body:has(#exampleContractorGroup1) .contractor-group-personnel-left {
  flex: 0 0 75%;
  width: 75%;
  max-width: 75%;
  padding-right: 15px !important;
}

body:has(#exampleContractorGroup1) .contractor-group-personnel-left {
  padding-left: 15px !important;
}

body:has(#exampleContractorGroup1) .contractor-group-edit-right,
body:has(#exampleContractorGroup1) .contractor-group-personnel-right {
  flex: 0 0 25%;
  width: 25%;
  max-width: 25%;
  padding-left: 0 !important;
  padding-right: 15px !important;
}

.personnel-contractor-groups-page .EmployeeTop_box .EmpTBoxR .btn-group {
  top: 0px;
  width: 300px !important;
}

/* Line the Edit Group Members gray box's left edge up with the groups grid
   box above it. The grid sits in the centred Bootstrap container (1110px of
   content at 1200-1399px, 1290px from 1400px), so its left edge is half the
   leftover row width in: padding % resolves against the row's width. The
   sidebar card on the right keeps its 25% column. */
@media (min-width: 1200px) {
  body:has(#exampleContractorGroup1) .contractor-group-edit-left {
    padding-left: max(12px, calc(50% - 555px)) !important;
  }
}

@media (min-width: 1400px) {
  body:has(#exampleContractorGroup1) .contractor-group-edit-left {
    padding-left: max(12px, calc(50% - 645px)) !important;
  }
}

body:has(#exampleContractorGroup1) .contractor-group-edit-left .membors_off {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  width: 100%;
  padding: 20px !important;
}

body:has(#exampleContractorGroup1) .contractor-group-edit-left .membors_off > form,
body:has(#exampleContractorGroup1) .contractor-group-edit-left .membors_off > .office_box {
  flex: 0 0 33.333333%;
  width: 33.333333%;
  max-width: 33.333333%;
  min-width: 0;
  box-sizing: border-box;
}

body:has(#exampleContractorGroup1) .contractor-group-edit-left .membors_off > form > .office_box,
body:has(#exampleContractorGroup1) .contractor-group-edit-left :is(.Box-UserW, .select_div) {
  width: 100% !important;
  max-width: none !important;
  min-width: 0;
}

body:has(#exampleContractorGroup1) .contractor-group-edit-left :is(.box1.Box-UserW, .box2.Box-UserW) {
  width: 270px !important;
  max-width: calc(100% - 20px) !important;
  margin-left: auto;
  margin-right: auto;
}

body:has(#exampleContractorGroup1) .contractor-group-edit-left .boxArea_in .button_bx {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 10px;
}

body:has(#exampleContractorGroup1) .contractor-group-edit-left .boxArea_in .button_bx br {
  display: none;
}

body:has(#exampleContractorGroup1) #exampleContractorGroup1_wrapper .records,
body:has(#exampleContractorGroup1) #exampleContractorGroupPersonnel_wrapper .records {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 8px;
}

body:has(#exampleContractorGroup1) :is(#exampleContractorGroup1_wrapper, #exampleContractorGroupPersonnel_wrapper)
  :is(.dt-search, .dataTables_filter, .dt-paging, .dataTables_paginate) {
  float: none !important;
  margin: 0 !important;
}

body:has(#exampleContractorGroup1) :is(#exampleContractorGroup1_wrapper, #exampleContractorGroupPersonnel_wrapper)
  :is(.dt-search, .dataTables_filter) input {
  margin: 0 0 0 6px !important;
}

body:has(#exampleContractorGroup1) #exportPersonnel {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  color: #fff !important;
  background: var(--cds-interactive, #0f62fe) !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
  text-align: center;
}

body:has(#exampleContractorGroup1) .contractor-side-card-button {
  color: #fff !important;
  background: var(--cds-interactive, #0f62fe) !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
  text-align: center;
}

body:has(#exampleContractorGroup1)
  :is(#exampleContractorGroup1_wrapper, #exampleContractorGroupPersonnel_wrapper)
  :is(.dt-table-scroll, .dt-scroll, .dt-scroll-body, .dataTables_scroll, .dataTables_scrollBody) {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

body:has(#exampleContractorGroup1) #exampleContractorGroup1_wrapper .records {
  overflow: visible;
  margin-bottom: 0;
}

@media (max-width: 767px) {
  body:has(#exampleContractorGroup1) .contractor-group-edit-left,
  body:has(#exampleContractorGroup1) .contractor-group-edit-right,
  body:has(#exampleContractorGroup1) .contractor-group-personnel-left,
  body:has(#exampleContractorGroup1) .contractor-group-personnel-right,
  body:has(#exampleContractorGroup1) .contractor-group-edit-left .membors_off > form,
  body:has(#exampleContractorGroup1) .contractor-group-edit-left .membors_off > .office_box {
    flex: 0 0 100%;
    width: 100%;
    max-width: 100%;
  }

  body:has(#exampleContractorGroup1) .contractor-group-edit-right,
  body:has(#exampleContractorGroup1) .contractor-group-personnel-right {
    padding-left: 15px !important;
    margin-top: 16px;
  }

  body:has(#exampleContractorGroup1) .contractor-group-edit-left {
    padding-left: 15px !important;
  }

  body:has(#exampleContractorGroup1) .contractor-group-edit-left .boxArea_in .button_bx {
    flex-direction: row;
    padding: 16px 0;
  }
}

@media (max-width: 767px) {
  body:has(.position-title-page) > .container,
  .position-title-page,
  .position-title-page > .container {
    padding-left: 10px !important;
    padding-right: 10px !important;
  }

  .position-title-page .work-regions > .qc_mainPrat:first-child,
  .position-title-page .real-page-content > .qc_mainPrat {
    overflow-x: auto !important;
    overflow-y: hidden !important;
  }

  .position-title-page .real-page-content > .qc_mainPrat {
    min-height: 550px;
  }
}

/* FIX [FDCM-3547]: work-orders-invoicing.php's "Reverted Invoice Log"
   modal (#reverted_invoices_modal, table #reverted_invoices_modal_table)
   had the same DataTables-3-vs-DevOps mismatches already fixed
   elsewhere in this file for other grids (see "#pto-request-que" and
   "#example"/"#example2" above), all confirmed live against devops on
   2026-09-09. Its JS init now reuses woInvoiceDataTableLayout()/
   woInvoiceDataTablePaginate (see those above reverted_invoices()),
   the same helpers already used - and confirmed against devops - for
   this page's Invoiced/Unbilled/Customer Invoice grids, so this modal
   also gets First/Previous/Next/Last pager labels and centered
   Showing-X-of-Y/pagination rows "for free" from the existing
   "body:has(#schedule_report):has(#customer_invoiced_table_data) ...
   .dt-paging"/".dt-layout-full:has(.dt-info)" blocks above (those
   selectors match on ids that exist on every load of this page, not
   just this modal, so no change was needed there). What's fixed here
   is everything specific to *this* grid/modal:

   1. Header/body text rendered left/right-aligned instead of centered.
      The table carries Bootstrap's ".text-center" utility, but that
      only sets text-align on the <table> for descendants to *inherit* -
      DataTables 3's own CSS stamps an explicit "text-align: left" onto
      every <th> and, per column, "text-align: right" onto every
      dt-type-numeric/dt-type-date <td> (Amount/Retainage as numbers,
      Reverted On as a date). An explicit rule on the element itself
      always wins over an inherited value, regardless of specificity, so
      those columns fought the inherited centering. This is also what
      made the header row look like "RetainageNote" ran together with no
      gap: right-aligned "Retainage" text sat flush against its column's
      right edge, immediately next to left-aligned "Note" text flush
      against the following column's left edge - centering both closes
      that gap.
   2. Header/body cells also inherited style-new.css's
      ".table-wid-adjust td, .table-wid-adjust th { padding: 0; }" (see
      the "#frm_dectype table.table-wid-adjust" fix above - same rule,
      different page, so it needs its own scoped restoration here too),
      leaving every row a visibly shorter ~22px instead of DevOps's
      ~37px and making the whole grid read as "compacted".
   3. The Excel/PDF export buttons rendered as bordered grey Bootstrap
      buttons (DataTables 3's Bootstrap5 adapter stamps "btn btn-secondary"
      onto them) instead of DevOps's plain blue text links with no
      button chrome.
   4. woInvoiceDataTableLayout() puts pageLength in its own row ("top2")
      and search/buttons together in the next row ("topStart"/"topEnd",
      rendered side by side via "d-md-flex justify-content-between"
      instead of DevOps's three separate, individually centered stacked
      lines ("Show 5 entries" / "Excel Export PDF Export" / "Search:") -
      forcing that second row into a centered column (and swapping its
      visual order, since DevOps shows the buttons before the search
      box) reproduces DevOps's stacked layout. */
#reverted_invoices_modal_table thead th,
#reverted_invoices_modal_table tbody td {
  text-align: center !important;
  padding: 8px !important;
}

#reverted_invoices_modal .buttons-excel,
#reverted_invoices_modal .buttons-pdf {
  background: transparent !important;
  border: 0 !important;
  box-shadow: none !important;
  color: #337ab7 !important;
  padding: 0 !important;
  margin: 0 6px !important;
  font-size: 14px !important;
}

#reverted_invoices_modal .buttons-excel:hover,
#reverted_invoices_modal .buttons-pdf:hover {
  color: #23527c !important;
  text-decoration: underline !important;
}

#reverted_invoices_modal .dt-container > .row:first-child .dt-layout-full {
  text-align: center !important;
}

#reverted_invoices_modal .dt-container > .row:nth-child(2) {
  flex-direction: column !important;
  margin-top: 20px !important;
}

#reverted_invoices_modal .dt-container > .row:nth-child(2) .dt-layout-start,
#reverted_invoices_modal .dt-container > .row:nth-child(2) .dt-layout-end {
  width: 100% !important;
  max-width: 100% !important;
  margin: 4px 0 !important;
  justify-content: center !important;
  text-align: center !important;
  flex: none !important;
}

#reverted_invoices_modal .dt-container > .row:nth-child(2) .dt-layout-end {
  order: 1;
}

#reverted_invoices_modal .dt-container > .row:nth-child(2) .dt-layout-start {
  order: 2;
}

#reverted_invoices_modal div.dt-buttons {
  margin: 0 !important;
}

/* FIX [FDCM-3547]: at the modal's real (non-mobile) width the "Showing X
   to Y of Z entries" and pagination rows still sat flush left, not
   centered like DevOps, plus the pagination row touched the modal's
   bottom edge with no breathing room. Centering ".dt-container > .row"
   itself (the outer Bootstrap row) does nothing here: that row already
   has exactly one child - ".dt-layout-full" - which DataTables/Bootstrap
   stretches to the row's full width ("col-md" with no sibling to share
   the row with), so "justify-content: center" on the OUTER row has no
   extra space to redistribute (its single child already fills 100% of
   it). The actual positioning of the "Showing X of Y"/pager *content*
   within that already-full-width child comes from ".dt-layout-full"'s
   own flex "justify-content: space-between" (Bootstrap5's
   "d-md-flex justify-content-between") - overriding THAT to "center" is
   what actually centers the visible content, same fix already applied
   (and confirmed against devops) to the sibling Invoiced/Unbilled/
   Customer Invoice grids via ".dt-layout-full:has(.dt-info)"/
   ".dt-layout-full:has(.dt-paging)" - see the
   "body:has(#schedule_report):has(#customer_invoiced_table_data)" block
   above (not extended to include this modal's wrapper id there, since
   this modal needed the extra bottom-margin fix below too; scoped
   separately here instead). */
#reverted_invoices_modal .dt-layout-full:has(.dt-info),
#reverted_invoices_modal .dt-layout-full:has(.dt-paging) {
  justify-content: center !important;
}

#reverted_invoices_modal .dt-container > .row:has(.dt-paging) {
  margin-bottom: 16px !important;
}

/* FIX [FDCM-3547]: "Show 5 entries" rendered as just "Show 5" with the
   trailing "entries" word missing, unlike DevOps. This grid's DataTables-
   generated ".dt-length label" carries no real text of its own - "Show"
   comes from a "::before" on ".dt-length" and "entries" from a "::after"
   on the label (see the ".dt-container .dt-length::before"/"label::after"
   rules earlier in this file, which exist specifically to normalize every
   grid's wording to "Show [select] entries"). A later, more specific
   sitewide rule - ".dt-container .dt-length label:empty { display: none
   !important; }" (meant only to collapse *genuinely* empty accessibility
   labels so they don't add stray layout height) - also matches this label,
   because CSS's ":empty" only considers actual child nodes/text, not
   "::after" generated content: the label counts as empty even though it
   visibly renders "entries", so it gets hidden and takes the "entries"
   text with it. Overriding back to visible here, scoped to this modal, so
   the many other grids relying on that sitewide "label:empty" hide (for
   labels that are genuinely empty, with no generated content) are
   unaffected. ".dt-search label" is included defensively for the same
   reason even though this modal's search label already has real "Search:"
   text (so ":empty" never matches it today). */
#reverted_invoices_modal .dt-length label:empty,
#reverted_invoices_modal .dt-search label:empty {
  display: inline !important;
}

/* ================================================================
"#erp_global_dialog_modal" SITEWIDE ALERT/CONFIRM/PROMPT DIALOG
(include/footer.php)
================================================================ */

/* FIX [FDCM-3547]: new sitewide replacement for native alert()/confirm()/
   prompt() (see include/footer.php for the markup/JS - "erp_global_dialog
   _modal" + window.erpAlert()/erpConfirm()/erpPrompt()). Without any
   styling this inherits the sitewide default ".modal-content { border:
   10px solid ... }" (style-new.css) - a thick, square-cornered, shadowless
   box, not the rounded/bordered/soft-shadowed card the reported
   screenshot showed. Values match this app's existing equivalent "devops
   modal" theming already established for work-orders-invoicing.php's
   modals (see ".modal:has(.wo-invoicing-modal-body)" above) for visual
   consistency, since devops's own rules for this specific dialog couldn't
   be safely read (see the include/footer.php comment for why). */
#erp_global_dialog_modal .modal-content {
  background: #ffffff;
  border: 4px solid var(--cds-interactive, #0f62fe) !important;
  border-radius: 14px;
  box-shadow: 0 16px 42px rgba(20, 63, 104, 0.22);
  overflow: hidden;
  width: 100%;
  margin: 0 auto;
}

/* Width lives on .modal-dialog; a percentage on .modal-content shrank the
   card to ~190px (40% of the 480px dialog), squeezing short messages.
   !important is required: the sitewide ".modal-dialog { max-width: none
   !important }" rule above otherwise stretches the alert to full width. */
#erp_global_dialog_modal .modal-dialog {
  max-width: 560px !important;
  width: calc(100vw - 32px);
}

#erp_global_dialog_modal .modal-header {
  align-items: center;
  background: #ffffff;
  border-bottom: 1px solid #dbe9f6 !important;
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  min-height: 44px;
  padding: 10px 24px 10px;
  position: relative;
}

#erp_global_dialog_modal .modal-header .close {
  align-items: center;
  background: transparent !important;
  border: 0 !important;
  border-radius: 4px;
  box-shadow: none !important;
  color: var(--cds-interactive, #0f62fe);
  display: flex;
  font-size: 28px;
  font-weight: 400;
  height: 32px;
  justify-content: center;
  line-height: 1;
  opacity: 1;
  position: absolute;
  right: 14px;
  top: 12px;
  width: 32px;
  z-index: 2;
}

#erp_global_dialog_modal .modal-title {
  color: #1f7fbd;
  display: block;
  font-size: 18px;
  font-weight: 700;
  line-height: 1.3;
  margin: 0;
  padding-right: 44px;
  text-align: center;
  width: 100%;
}

#erp_global_dialog_modal .modal-body {
  background: #ffffff;
  color: #222222;
  padding: 20px 24px;
  min-height: 75px;
}

#erp_global_dialog_modal .erp-global-dialog-message {
  font-size: 15px;
  line-height: 1.5;
  white-space: pre-line;
}

#erp_global_dialog_modal .erp-global-dialog-prompt-wrap {
  margin-top: 14px;
}

#erp_global_dialog_modal .modal-footer {
  background: #ffffff;
  border-top: 1px solid #dbe9f6 !important;
  padding: 12px 24px;
}

#erp_global_dialog_modal .erp-global-dialog-ok {
  background-color: var(--cds-interactive, #0f62fe) !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
  width: 75px;
}

#erp_global_dialog_modal .erp-global-dialog-cancel {
  background-color: #ffffff !important;
  border-color: #ccc !important;
  color: #333333 !important;
}

/* ================================================================
"#log_modal" PERSONNEL PTO LOG MODAL (personnel/pto-request-personnel.php)
================================================================ */

/* FIX [FDCM-3547]: this modal's title ("Personnel PTO Log") and its "X"
   close link used to live inside the same ".filter_list.qc_mainPrat" div
   as the log grid itself (personnel/pto-request-personnel.php) - that
   div's own ".qc_mainPrat { background: #e6e6e6; padding: 20px; }"
   (style-new.css) painted the ash-grey background behind the title/close
   row too, and being one shared block gave no seam for a divider line
   between them and the grid below. The title/close markup was moved out
   into its own ".log-modal-header" sibling (see that file), so this is
   just the matching visual treatment: white background, centered title,
   a bottom border standing in for DevOps's divider line, and the close
   link repositioned as a small boxed button in the corner instead of a
   bare floated "X". */
#log_modal.pto-request-personnel-page-modal .log-modal-header {
  background: #ffffff;
  border-bottom: 1px solid #ddd;
  padding: 12px 20px;
  position: relative;
  text-align: center;
}

#log_modal.pto-request-personnel-page-modal .log-modal-header h2 {
  margin: 0;
  padding: 0;
  font-size: 20px;
  font-weight: bold;
  color: #1f7fbd;
}

#log_modal.pto-request-personnel-page-modal .log-modal-close {
  position: absolute;
  right: 16px;
  top: 10px;
  margin: 0;
}

/* FIX [FDCM-3547]: personnel/ajax/get_pto_log_data.php's "#example15"
   grid uses the legacy DataTables "dom" string (not the newer "layout"
   API other already-fixed grids in this file use), which under DataTables
   3 renders its length/search/paging controls as ".records > div"
   (unclassed) children - already forced inline-block sitewide (see
   "#example_wrapper .records > div" above), so length/search/paging sit
   in one row here rather than stacking. With zero margin between them,
   though, the search box and the pagination controls sat flush against
   each other. "#example15" itself is reused by several unrelated pages
   (grep for id="example15" - claim-management-settings, risk-safety,
   personnel's own other stat/notification grids, etc.), so this rule can
   apply wherever another page's own "#example15" grid happens to share
   the same legacy-dom/".records" markup shape too - a plain margin-right
   before the search box is low-risk there either way, so no ":has()"
   cross-page guard was added purely for that. */
#log_modal.pto-request-personnel-page-modal #example15_wrapper .records > div:has(.dt-search) {
  margin-right: 20px;
}

/* FIX [FDCM-3547]: this grid's header/body cells (personnel/ajax/
   get_pto_log_data.php's "#example15") had almost no cell padding
   ("thead th { padding: 0 5px; }", "tbody td { padding: 1px; }" -
   computed, not from any rule authored for this table specifically),
   leaving adjacent columns' text sitting nearly flush against each other
   with no visual gap to show where one column ends and the next begins -
   most noticeable between "Date Requested"/"Hours Requested" and between
   the data rows' own values. Scoped to "#log_modal #example15" (rather
   than the bare "#example15" id used for the search/pagination spacing
   fix above) since padding changes shift column widths more than a
   margin tweak would, and this table only actually renders inside
   "#log_modal" on this page. */
#log_modal.pto-request-personnel-page-modal #example15 th,
#log_modal.pto-request-personnel-page-modal #example15 td {
  padding: 8px 12px !important;
}

/* FIX [FDCM-3547]: payroll/timesheet-audit-local.php. Live (DT 1.10) put
   Search input + Search/Clear Filter buttons, length, and Export To on one
   toolbar row. DT 3 renders search as ".dt-search" (no "#timesheetExample_filter"
   id) and splits length/search across layout cells, so the custom buttons
   never attached and the controls no longer lined up. */
#timesheetExample_wrapper > .dt-layout-row:first-child,
#timesheetExample_wrapper > .row:first-child {
  display: flex !important;
  align-items: center !important;
  justify-content: flex-start !important;
  flex-wrap: wrap;
  gap: 10px;
  min-height: 44px;
  padding: 6px 10px !important;
}

#timesheetExample_wrapper .dt-layout-start,
#timesheetExample_wrapper .dt-layout-end {
  display: flex !important;
  align-items: center !important;
  flex: 0 0 auto !important;
  width: auto !important;
  margin: 0 !important;
  float: none !important;
}

#timesheetExample_wrapper .dt-layout-end:has(.dt-search),
#timesheetExample_wrapper .dt-layout-end:has(.dataTables_filter) {
  order: -1;
  margin-right: auto !important;
}

#timesheetExample_wrapper .dt-search,
#timesheetExample_wrapper .dataTables_filter,
#timesheetExample_filter {
  display: flex !important;
  align-items: center !important;
  gap: 6px;
  margin: 0 !important;
  float: none !important;
}

#timesheetExample_wrapper .dt-search input,
#timesheetExample_wrapper .dataTables_filter input,
#timesheetExample_filter input {
  width: 165px !important;
  height: 34px !important;
  margin: 0 0 0 10px !important;
}

#timesheetExample_wrapper .dt-search .btn,
#timesheetExample_wrapper .dataTables_filter .btn,
#timesheetExample_filter .btn {
  margin: 0 !important;
  white-space: nowrap;
}

#timesheetExample_wrapper .dt-length,
#timesheetExample_wrapper .dataTables_length {
  margin-left: auto !important;
}

#timesheetExample_wrapper .exportappend {
  display: inline-flex !important;
  align-items: center;
  margin-left: 8px;
}

#timesheetExample_wrapper .exportappend select {
  height: 34px;
  padding: 4px 8px;
}

/* Office Payroll Status: Go/Reset were appended to ".dataTables_filter",
   which DT 3 no longer creates. Keep search + buttons on one row. */
#Payroll_Status_table_wrapper .dt-search,
#Payroll_Status_table_wrapper .dataTables_filter {
  display: flex !important;
  align-items: center !important;
  gap: 6px;
}

/* Default rule for all pages. */
select {
  background: #fff;
}

/* FIX [FDCM-3547]: modal grid's table header font & background color. */
.contractor-groups-log-modal.modal .modal-body .dataTable th {
  color: #1f7fbd !important;
  font-weight: 600 !important;
}
.contractor-groups-log-modal.modal .modal-body table > thead > tr > th {
  background: #edf6ff !important;
  border-color: #dbe9f6 !important;
  vertical-align: middle !important;
}

/* FIX [FDCM-3547]: save anchor link color set. */
.training-settings-page .save-btn a {
  color: #fff !important;
  background: var(--cds-interactive, #0f62fe) !important;
  border-color: var(--cds-interactive, #0f62fe) !important;
  text-align: center;
}

.training-settings-page .last-btn .save-btn:nth-child(2) a {
  color: #fff !important;
  padding: 5px 10px;
}

/* Departments (personnel/department.php). */
.department-page .Middle.bonus-category {
  margin-top: -5%;
}

.department-page .checktxt,
.department-page .department-grid-search-value {
  display: none;
}

.department-page .gap-chck-up .control.control--checkbox {
  left: 50% !important;
}

.department-page .dt-button-collection.dtb-b1 {
	left: -120px !important;
}

/* The grid fits its visible page into the card; DataTables must not create
   an internal horizontal or vertical scrolling viewport. */
.department-page .records.datasrchJSO,
.department-page #exampledepartment_wrapper,
.department-page #exampledepartment_wrapper .dt-table-scroll,
.department-page #exampledepartment_wrapper .dt-scroll-body,
.department-page #exampledepartment_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow: visible !important;
}

.department-page #exampledepartment {
  table-layout: fixed;
  width: 100% !important;
}

.department-page #exampledepartment th,
.department-page #exampledepartment td {
  overflow-wrap: anywhere;
  white-space: normal;
}

.department-page #exampledepartment input[type="text"] {
  box-sizing: border-box;
  min-width: 0;
  width: 100%;
}

/* Length, search, and export controls share the grid's top toolbar. */
.department-page #exampledepartment_wrapper .department-grid-toolbar {
  align-items: center;
  display: flex;
  gap: 14px;
  margin: 0 0 14px;
}

.department-page #exampledepartment_wrapper .department-grid-length,
.department-page #exampledepartment_wrapper .department-grid-search,
.department-page #exampledepartment_wrapper .department-grid-export {
  display: flex;
  align-items: center;
}

.department-page #exampledepartment_wrapper .department-grid-search {
  margin-right: 16px;
}

.department-page #exampledepartment_wrapper .department-grid-search input {
  width: 200px !important;
}

.department-page #exampledepartment_wrapper .department-grid-export {
  margin-left: auto;
  position: relative;
}

.department-page #exampledepartment_wrapper .dt-buttons {
  margin: 0 !important;
}

.department-page .records {
  overflow-x: hidden;
}

/* Keep the collection directly beneath Export, matching the DevOps menu. */
.department-page #exampledepartment_wrapper .dt-button-collection,
.department-page #exampledepartment_wrapper .dt-button-background + .dt-button-collection {
  border: 1px solid #999 !important;
  border-radius: 4px !important;
  box-shadow: 0 2px 6px rgb(0 0 0 / 25%) !important;
  min-width: 140px;
  padding: 8px !important;
  z-index: 1000 !important;
}

.department-page #exampledepartment_wrapper .dt-button-collection .dt-button {
  background: #f5f5f5 !important;
  border: 1px solid #aaa !important;
  border-radius: 2px !important;
  box-shadow: none !important;
  color: #333 !important;
  display: block !important;
  margin: 0 !important;
  text-align: center;
  width: 100%;
}

/* TimeSheet History (personnel/timesheet-history.php). */
.personnel-timesheet-history-page .Middle.payrl.bonus-category .col-md-6 {
  margin: 0 auto;
}

/* New Hire Entry (personnel/personnel/new-hire-entry.php). */
.personnel-new-hire-entry-page .self_qs label {
  text-transform: uppercase;
  padding: 50px 0 11px;
  float: left;
  font-size: 26px;
  font-weight: 300;
  margin: 0;
  width: 100%;
}

/* New Contractor (personnel/personnel/new-contractor.php). */
.personnel-new-contractor-page .self_qs label {
  text-transform: uppercase;
  padding: 50px 0 11px;
  float: left;
  font-size: 26px;
  font-weight: 300;
  margin: 0;
  width: 100%;
}

/* New Contractor Company (personnel/new-contractor-company.php). */
.personnel-new-contractor-company-page .self_qs label {
  text-transform: uppercase;
  padding: 50px 0 11px;
  float: left;
  font-size: 26px;
  font-weight: 300;
  margin: 0;
  width: 100%;
}

/* Personnel Summary (personnel/summary.php). The page's ".label" fields
   clash with the Bootstrap 3 ".label" badge restored above (75% size, white,
   bold, centred, all !important). Cover every summary card's labels - the
   Employment Info / Contact Info rows sit in ".info-grid", not ".profile-card",
   so they were still white-on-white - and keep the page's 600 weight for the
   Office Assignments labels, as on ats. */
.personnel-summary-page .data-row .label {
  color: #64748b !important;
  font-size: 14px !important;
  font-weight: 500 !important;
  text-align: left !important;
}

.personnel-summary-page .office-section .data-row .label {
  font-weight: 600 !important;
}

/* Interviewers (personnel/interviewer.php). */
.interviewer-page .Middle.cust-grp {
  margin-top: -5%;
}

.interviewer-page .edit_memb {
  text-align: center;
}

.interviewer-page .edit_memb > label {
  color: #1f7fbd;
  display: inline-block;
  font-size: 20px;
  font-weight: 400;
  margin: 0 0 16px;
  padding-bottom: 12px;
  border-bottom: 1px solid #0f62fe;
}

.interviewer-page .membors_off > form {
  align-items: center;
  display: flex;
  gap: 28px;
  justify-content: center;
  width: 100%;
}

.interviewer-page .membors_off > form > .office_box {
  float: none;
  flex: 0 1 320px;
  min-width: 0;
  padding: 0;
}

.interviewer-page .membors_off > form > .boxArea_in {
  flex: 0 0 auto;
}

.interviewer-page .button_bx {
  align-items: center;
  display: flex;
  flex-direction: column;
  gap: 12px;
  justify-content: center;
  padding: 0;
}

.interviewer-page .button_bx .small-add {
  margin: 0;
  min-width: 110px;
}

.interviewer-page .user-item {
  padding-bottom: 10px;
}

.interviewer-page .available-status {
  float: right;
  font-size: 12px;
}

.interviewer-page .checktxt {
  display: none;
}

.interviewer-page #user2-list {
  overflow-y: auto;
}

@media (max-width: 768px) {
  .interviewer-page .membors_off > form {
    flex-direction: column;
    gap: 20px;
  }

  .interviewer-page .membors_off > form > .office_box,
  .interviewer-page .membors_off > form > .boxArea_in {
    flex: 0 0 auto;
    max-width: 100%;
    width: 100%;
  }

  .interviewer-page .button_bx {
    flex-direction: row;
  }
}

/* Termination reasons (personnel/termination-reason.php). */
.termination-reason-page .Middle.bonus-category {
  margin-top: -5%;
}

.termination-reason-page .checktxt {
  display: none;
}

/* Fit the five-column grid to its card instead of exposing a horizontal rail. */
.termination-reason-page #example_wrapper,
.termination-reason-page #example_wrapper .dt-table-scroll,
.termination-reason-page #example_wrapper .dt-scroll,
.termination-reason-page #example_wrapper .dataTables_scroll {
  overflow-x: hidden !important;
}

.termination-reason-page #example {
  table-layout: fixed;
  width: 100% !important;
}

.termination-reason-page #example th,
.termination-reason-page #example td {
  overflow-wrap: anywhere;
  white-space: normal;
}

.termination-reason-page #example input[type="text"] {
  box-sizing: border-box;
  max-width: 100%;
}

/* Separate the search input from the pagination control. */
.termination-reason-page #example_wrapper .records .dt-search,
.termination-reason-page #example_wrapper .records .dataTables_filter,
.termination-reason-page #example_wrapper .records > div:has(.dt-search),
.termination-reason-page #example_wrapper .records > div:has(.dataTables_filter) {
  margin-right: 10px !important;
}

.termination-reason-page #example_wrapper .records div {
  display: inline;
}

.termination-reason-page .export_function button {
  margin-top: 0;
  padding-bottom: 7px;
  padding-top: 7px;
}

/* Contractor groups (personnel/contractor-groups-test.php). */
.contractor-groups-page .Middle {
  margin-top: -4%;
}

.contractor-groups-page .checktxt,
.contractor-groups-page .contractor-group-hidden-label {
  display: none;
}

.contractor-groups-page .user-item,
.contractor-groups-page .user-item2 {
  position: relative;
  width: 80%;
}

.contractor-groups-page .user-item {
  top: 18px;
}

.contractor-groups-page .sup-tab,
.contractor-groups-page #exampleContractorGroup_wrapper {
  height: auto !important;
  max-height: none !important;
  overflow: visible !important;
}

/* Keep the four-column grid within its card without horizontal or vertical rails. */
.contractor-groups-page #exampleContractorGroup_wrapper .dt-table-scroll,
.contractor-groups-page #exampleContractorGroup_wrapper .dt-scroll,
.contractor-groups-page #exampleContractorGroup_wrapper .dataTables_scroll,
.contractor-groups-page #exampleContractorGroup_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow: hidden !important;
}

.contractor-groups-page #exampleContractorGroup {
  min-width: 0 !important;
  table-layout: fixed !important;
  width: 100% !important;
}

.contractor-groups-page #exampleContractorGroup th,
.contractor-groups-page #exampleContractorGroup td {
  min-width: 0 !important;
  overflow-wrap: anywhere;
  white-space: normal;
}

/* The group name only needs a little over one third of the grid. */
.contractor-groups-page #exampleContractorGroup th:first-child,
.contractor-groups-page #exampleContractorGroup td:first-child,
.contractor-groups-page #exampleContractorGroup colgroup col:first-child {
  width: 36% !important;
}

.contractor-groups-page #exampleContractorGroup th:not(:first-child),
.contractor-groups-page #exampleContractorGroup td:not(:first-child),
.contractor-groups-page #exampleContractorGroup colgroup col:not(:first-child) {
  width: 21.33% !important;
}

/* Keep the DataTables controls together while separating search from paging. */
.contractor-groups-page #exampleContractorGroup_wrapper .records {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  justify-content: center;
}

.contractor-groups-page #exampleContractorGroup_wrapper .records > div {
  float: none !important;
  margin: 0 !important;
}

.contractor-groups-page #exampleContractorGroup_wrapper .records .dataTables_filter,
.contractor-groups-page #exampleContractorGroup_wrapper .records .dt-search {
  margin-right: 20px !important;
}

.contractor-groups-page .assets_tabil .control.control--radio {
  top: 0px !important;
}

.contractor-groups-page #myModal .taskinfoclose {
  position: absolute;
  right: 15px;
  top: 13px;
}

.contractor-groups-page .clsextrapadd {
  padding-top: 23px;
}

@media (max-width: 768px) {
  .contractor-groups-page #exampleContractorGroup th,
  .contractor-groups-page #exampleContractorGroup td {
    font-size: 12px;
    padding-left: 4px !important;
    padding-right: 4px !important;
  }

  .contractor-groups-page #exampleContractorGroup th:first-child,
  .contractor-groups-page #exampleContractorGroup td:first-child,
  .contractor-groups-page #exampleContractorGroup colgroup col:first-child {
    width: 34% !important;
  }

  .contractor-groups-page #exampleContractorGroup th:not(:first-child),
  .contractor-groups-page #exampleContractorGroup td:not(:first-child),
  .contractor-groups-page #exampleContractorGroup colgroup col:not(:first-child) {
    width: 22% !important;
  }
}

/* New hire field settings (personnel/new-hire-setting.php). */
.personnel-new-hire-entry-page .midStyle_section {
  align-items: flex-start;
  display: flex;
  flex-wrap: wrap;
  gap: 30px;
  /* FIX: carbon-theme.css's ".qc_mainPrat, .qc_mainPrat1111,
     .midStyle_section { background: var(--cds-layer-01); }" (#f4f4f4)
     paints ".midStyle_section" itself the same grey as the two
     ".qc_mainPrat" cards (Federal Tax/State Tax) it wraps - so even
     though the 30px flex "gap" above genuinely separates the two cards
     structurally, the gap gets filled with that same grey by the parent,
     making both cards read as one continuous block instead of two
     distinct ones. Confirmed live: neither card's own background needs
     touching, only the wrapping ".midStyle_section" needs to go
     transparent so the page's white background shows through the gap. */
  background: transparent !important;
}

.personnel-new-hire-entry-page .midStyle_section > .left_midSec,
.personnel-new-hire-entry-page .midStyle_section > .right_midSec {
  box-sizing: border-box;
  float: none;
  flex: 1 1 0;
  max-width: calc(50% - 15px);
  min-width: 0;
  padding: 0;
  width: auto;
}

.personnel-new-hire-entry-page .midStyle_section .self_qs,
.personnel-new-hire-entry-page .midStyle_section .qc_mainPrat {
  max-width: 100%;
  width: 100%;
}

.personnel-new-hire-entry-page .right_midSec .col-md-12.qc_mainPrat {
  padding-bottom: 20px;
}

.personnel-new-hire-entry-page #loading {
  display: none;
}

@media (max-width: 768px) {
  .personnel-new-hire-entry-page .midStyle_section {
    gap: 24px;
  }

  .personnel-new-hire-entry-page .midStyle_section > .left_midSec,
  .personnel-new-hire-entry-page .midStyle_section > .right_midSec {
    flex-basis: 100%;
    max-width: 100%;
    width: 100%;
  }
}

/* Labor category (personnel/labor-category.php). */
.labor-category-page .Middle.bonus-category {
  margin-top: -5%;
}

.labor-category-page .checktxt {
  display: none;
}

.labor-category-page #myModal .taskinfoclose {
  float: right;
}

/* Fit the three-column grid and show all five configured rows without rails. */
.labor-category-page #example_title_wrapper,
.labor-category-page .real-page-content .qc_mainPrat {
  height: auto !important;
  max-height: none !important;
  overflow: visible !important;
}

.labor-category-page #frm_dectype > .records {
  overflow: visible !important;
}

.labor-category-page #example_title_wrapper .dt-table-scroll,
.labor-category-page #example_title_wrapper .dt-scroll,
.labor-category-page #example_title_wrapper .dataTables_scroll,
.labor-category-page #example_title_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow: hidden !important;
}

.labor-category-page #example_title {
  min-width: 0 !important;
  table-layout: fixed !important;
  width: 100% !important;
}

.labor-category-page #example_title th,
.labor-category-page #example_title td {
  min-width: 0 !important;
  overflow-wrap: anywhere;
  white-space: normal;
}

.labor-category-page #example_title input[type="text"] {
  box-sizing: border-box;
  max-width: 196px;
  width: 100%;
}

.labor-category-page #example_title colgroup col:first-child {
  width: 50% !important;
}

.labor-category-page #example_title colgroup col:not(:first-child) {
  width: 25% !important;
}

/* Separate the search field from the pagination controls. */
.labor-category-page #example_title_wrapper .records {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  justify-content: center;
}

.labor-category-page #example_title_wrapper .records > div {
  float: none !important;
  margin: 0 !important;
}

.labor-category-page #example_title_wrapper .records .dataTables_filter,
.labor-category-page #example_title_wrapper .records .dt-search {
  margin-right: 20px !important;
  text-align: left !important;
}

.labor-category-page #example_title_wrapper .exportappend {
  margin-left: 10px;
}

.labor-category-page #example_title_wrapper .dataTables_length,
.labor-category-page #example_title_wrapper .dt-length {
  margin-right: 10px;
}

.labor-category-page .export_function button {
  margin-top: 0;
  padding-bottom: 7px;
  padding-top: 7px;
}

@media (max-width: 768px) {
  .labor-category-page #example_title th,
  .labor-category-page #example_title td {
    font-size: 12px;
    padding-left: 4px !important;
    padding-right: 4px !important;
  }

  .labor-category-page #example_title input[type="text"] {
    max-width: 100%;
  }
}

/* Badge information settings (personnel/badge-information-settings.php). */
.badge-information-settings-page .Middle.bonus-category {
  margin-top: -5%;
}

.badge-information-settings-page .checktxt {
  display: none;
}

.badge-information-settings-page #Show_Log .modal-dialog {
  width: 85%;
}

.badge-information-settings-page table {
  width: 100%;
}

.badge-information-settings-page .btn-group ul {
  max-height: 300px;
  overflow-x: hidden;
  overflow-y: scroll;
  position: absolute;
}

.badge-information-settings-page .btn-group {
  top: -4px;
}

.badge-information-settings-page .payrl .btn-group {
  top: 0 !important;
}

/* Let the ten-column grid grow to its five configured rows without a vertical rail. */
.badge-information-settings-page #tableBadgeSettings_wrapper,
.badge-information-settings-page .real-page-content .qc_mainPrat,
.badge-information-settings-page #frm_badge_at_once > .records {
  height: auto !important;
  max-height: none !important;
  overflow-y: visible !important;
}

.badge-information-settings-page #tableBadgeSettings_wrapper .dt-table-scroll,
.badge-information-settings-page #tableBadgeSettings_wrapper .dt-scroll,
.badge-information-settings-page #tableBadgeSettings_wrapper .dataTables_scroll,
.badge-information-settings-page #tableBadgeSettings_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

/* Center every control under its heading while retaining left-aligned text fields. */
.badge-information-settings-page #tableBadgeSettings th,
.badge-information-settings-page #tableBadgeSettings td {
  text-align: center !important;
  vertical-align: middle;
}

.badge-information-settings-page #tableBadgeSettings td:first-child {
  text-align: left !important;
}

.badge-information-settings-page #tableBadgeSettings td:not(:first-child) .control {
  display: inline-block;
  text-align: left;
}

/* Separate the search input from pagination. */
.badge-information-settings-page #tableBadgeSettings_wrapper .records {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  justify-content: center;
}

.badge-information-settings-page #tableBadgeSettings_wrapper .records > div {
  float: none !important;
  margin: 0 !important;
}

.badge-information-settings-page #tableBadgeSettings_wrapper .records .dataTables_filter,
.badge-information-settings-page #tableBadgeSettings_wrapper .records .dt-search {
  margin-right: 28px !important;
}

.badge-information-settings-page #LogModalTable_wrapper .records > div,
.badge-information-settings-page #tableBadgeSettings_wrapper .records > div {
  display: inline;
}

.badge-information-settings-page #LogModalTable_paginate,
.badge-information-settings-page #tableBadgeSettings_paginate {
  margin: 1% !important;
}

@media (max-width: 768px) {
  .badge-information-settings-page #tableBadgeSettings th,
  .badge-information-settings-page #tableBadgeSettings td {
    font-size: 12px;
    padding-left: 4px !important;
    padding-right: 4px !important;
  }

  .badge-information-settings-page #Show_Log .modal-dialog {
    width: calc(100% - 30px);
  }
}

/* Manage race (personnel/manage-race.php). */
.manage-race-page .checktxt { display: none; }

.manage-race-page #example_wrapper,
.manage-race-page #frm_dectype { overflow-x: visible !important; }

.manage-race-page #example_wrapper .dt-table-scroll,
.manage-race-page #example_wrapper .dt-scroll,
.manage-race-page #example_wrapper .dataTables_scroll {
  overflow-x: hidden !important;
}

.manage-race-page #example {
  min-width: 0 !important;
  table-layout: fixed !important;
  width: 100% !important;
}

.manage-race-page #example th,
.manage-race-page #example td {
  min-width: 0 !important;
  overflow-wrap: anywhere;
  white-space: normal;
}

/* Keep ADP Code compact while letting race names use the available space. */
.manage-race-page #example colgroup col:first-child { width: 46% !important; }
.manage-race-page #example colgroup col:nth-child(2) { width: 24% !important; }
.manage-race-page #example colgroup col:nth-child(3),
.manage-race-page #example colgroup col:nth-child(4) { width: 15% !important; }

.manage-race-page #example input { box-sizing: border-box; max-width: 100%; }

.manage-race-page #example_wrapper .records {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  justify-content: center;
}

.manage-race-page #example_wrapper .records > div {
  float: none !important;
  margin: 0 !important;
}

/* Leave room on both sides of pagination. */
.manage-race-page #example_wrapper .records .dt-paging,
.manage-race-page #example_wrapper .records .dataTables_paginate { margin: 0 20px !important; }

@media (max-width: 768px) {
  .manage-race-page #example th,
  .manage-race-page #example td {
    font-size: 12px;
    padding-left: 4px !important;
    padding-right: 4px !important;
  }
}

/* Manage gender (personnel/manage-gender.php). */
.manage-gender-page .checktxt { display: none; }

.manage-gender-page #example_wrapper,
.manage-gender-page #frm_dectype { overflow-x: visible !important; }

.manage-gender-page #example_wrapper .dt-table-scroll,
.manage-gender-page #example_wrapper .dt-scroll,
.manage-gender-page #example_wrapper .dataTables_scroll { overflow-x: hidden !important; }

.manage-gender-page #example {
  min-width: 0 !important;
  table-layout: fixed !important;
  width: 100% !important;
}

.manage-gender-page #example th,
.manage-gender-page #example td {
  min-width: 0 !important;
  overflow-wrap: anywhere;
  white-space: normal;
}

/* Keep ADP Code compact while preserving room for the gender name. */
.manage-gender-page #example colgroup col:first-child { width: 46% !important; }
.manage-gender-page #example colgroup col:nth-child(2) { width: 24% !important; }
.manage-gender-page #example colgroup col:nth-child(3),
.manage-gender-page #example colgroup col:nth-child(4) { width: 15% !important; }
.manage-gender-page #example input { box-sizing: border-box; max-width: 100%; }

.manage-gender-page #example_wrapper .records {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  justify-content: center;
}

.manage-gender-page #example_wrapper .records > div {
  float: none !important;
  margin: 0 !important;
}

.manage-gender-page #example_wrapper .records .dt-paging,
.manage-gender-page #example_wrapper .records .dataTables_paginate { margin: 0 20px !important; }

body:has(.manage-gender-page) .modal-backdrop { display: none; }
.manage-gender-page .modalwidth { width: 70%; }
.manage-gender-page .export_function button { margin-top: 0; padding: 7px 0; }

@media (max-width: 768px) {
  .manage-gender-page #example th,
  .manage-gender-page #example td {
    font-size: 12px;
    padding-left: 4px !important;
    padding-right: 4px !important;
  }

  .manage-gender-page .modalwidth { width: 95%; }
}

/* Recruiters (personnel/recruiters.php). */
.recruiters-page > .Middle { margin-top: -4%; }

/* FIX: this previously targeted ".recruiters-page > .Middle > .container"
   as three separate nested elements, but the actual markup combines all
   three classes (plus "has-menu-box") onto one single div -
   "<div class="container recruiters-page Middle has-menu-box">" - so that
   selector never matched anything and this page stayed capped at
   Bootstrap 5's default ".container" max-width (1320px at this viewport,
   confirmed live), instead of running full width like DevOps (whose
   equivalent container has no max-width at all - confirmed live:
   "max-width: none" there). Centering ("text-align: center" on
   ".heading_bold"/".last-btn.tw-three" etc.) was already correct and just
   looked left-aligned because it was centering *within* that
   narrower-than-the-page container.
   That single compound rule alone still wasn't enough, though (confirmed
   live) - the page nests a SECOND, plain "<div class="container Middle">"
   (no "recruiters-page"/"has-menu-box" classes of its own) directly
   inside the first one, and all the visible content (heading, the grey
   Members/Available-Members panel, Save/Cancel) actually lives inside
   THIS inner container - so it was still hitting the same 1320px cap
   independently, keeping everything visually narrow even once the outer
   wrapper itself went full width. Added as a descendant selector (rather
   than folding into one compound selector) since this inner element
   doesn't carry "recruiters-page" itself - only an ancestor does. */
.recruiters-page.container.Middle,
.recruiters-page .container.Middle {
  max-width: none !important;
  width: 100% !important;
}

.recruiters-page .heading_bold { text-align: center; }

.recruiters-page .qc_mainPrat.supv {
  box-sizing: border-box;
  max-width: none !important;
  width: 100% !important;
}

.recruiters-page .membors_off {
  display: flex;
  align-items: center;
  gap: 48px;
  justify-content: center;
  width: 100%;
}

.recruiters-page .membors_off > form > .office_box,
.recruiters-page .membors_off > .office_box {
  float: none;
  flex: 0 1 320px;
  margin: 0;
  min-width: 0;
  padding: 0;
}

.recruiters-page .membors_off > .boxArea_in {
  flex: 0 0 auto;
}

.recruiters-page .Box-UserW { max-width: 300px !important; }

.recruiters-page .button_bx {
  align-items: center;
  display: flex;
  flex-direction: column;
  gap: 12px;
  justify-content: center;
}

.recruiters-page .button_bx br { display: none; }
.recruiters-page .button_bx .small-add { margin: 0; min-width: 110px; }
.recruiters-page .checktxt { display: none; }
.recruiters-page .txt-center { text-align: center !important; }
.recruiters-page .multiselect-container { max-height: 200px !important; overflow-y: scroll !important; }
.recruiters-page .assets_tabil .control.control--radio { top: 10px !important; }
.recruiters-page #example5_wrapper .records div { display: inline; }
.recruiters-page .small-adding { margin-left: 50px; padding-left: 19px !important; width: 83px; }

@media (max-width: 768px) {
  .recruiters-page .membors_off { flex-direction: column; gap: 20px; }
  .recruiters-page .membors_off > form,
  .recruiters-page .membors_off > .office_box {
    flex: 0 0 auto;
    max-width: 100%;
    width: 100%;
  }
  .recruiters-page .button_bx { flex-direction: row; }
  .recruiters-page .user-item2 { width: 100% !important; }
}

/* Certifications (personnel/certification.php). */
.certification-page .Middle.bonus-category {
  margin-top: -5%;
}

.certification-page .cer-tab1 table {
  width: 100%;
}

.certification-page .cer-tab1 th:nth-child(2) {
  text-align: left;
}

.certification-page .cer-tab1 input[name="Renewal"] {
  float: left;
  width: 25%;
}

.certification-page .cer-tab1 select[name="Frequency"],
.certification-page #exampleTrainingCreti select[name^="Frequency-"] {
  margin-top: 0;
}

.certification-page .checktxt {
  opacity: 0;
}

.certification-page #exampleTrainingCreti input[name^="Renewal-"] {
  float: left;
  width: 30%;
}

.certification-page #exampleTrainingCreti select[name^="Frequency-"] {
  width: 65%;
}

.certification-page #exampleTrainingCreti_wrapper .records div {
  display: inline;
}

.certification-page #exampleTrainingCretiLog td {
  text-align: center !important;
}

.certification-page .export_function button {
  padding-top: 7px;
  padding-bottom: 7px;
  margin-top: 0;
}

/* Expand the first grid to fit all rows on the selected page. */
.certification-page #exampleTrainingCreti_wrapper .dt-scroll-body,
.certification-page #exampleTrainingCreti_wrapper .dataTables_scrollBody {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden !important;
}

/* Space pagination away from the search field and export button. */
.certification-page #exampleTrainingCreti_wrapper .dt-paging,
.certification-page #exampleTrainingCreti_wrapper .dataTables_paginate {
  margin-left: 15px !important;
  margin-right: 15px !important;
}

.certification-page .dt-table-scroll,
.certification-page .dt-container div:has(> table.dataTable) {
  overflow-y: hidden;
}

/* Leave room on both sides of pagination. */
.manage-marital-status-page #example_wrapper .records .dt-paging,
.manage-marital-status-page #example_wrapper .records .dataTables_paginate {
  margin: 0 20px !important;
}

.manage-marital-status-page #example_wrapper .dt-table-scroll {
  height: auto !important;
  max-height: none !important;
  overflow-y: hidden;
  overflow-x: hidden;
}

.custom-info-page #example5_wrapper .records .dt-paging {
  margin: 0 20px !important;
}

.custom-info-page #example5_wrapper .dt-table-scroll {
  height: auto !important;
  max-height: none !important;
  overflow-x: hidden !important;
  overflow-y: hidden !important;
}

.assign-group-permission-page .dt-search {
    margin-right: 10px;
}

/* Assign group permission: fit the grid without nested scrollbars. */
.assign-group-permission-page .Middle { margin-top: -4%; }

.assign-group-permission-page .sup-tab,
.assign-group-permission-page #exampleContractorGroup_wrapper,
.assign-group-permission-page .dt-table-scroll {
  height: auto !important;
  max-height: none !important;
  overflow: visible !important;
}

.assign-group-permission-page #exampleContractorGroup {
  width: 100% !important;
  min-width: 0 !important;
  table-layout: fixed !important;
}

.assign-group-permission-page #exampleContractorGroup th,
.assign-group-permission-page #exampleContractorGroup td {
  min-width: 0 !important;
  white-space: normal;
  overflow-wrap: anywhere;
}

.assign-group-permission-page #exampleContractorGroup tbody td {
  padding-top: 5px !important;
  padding-bottom: 5px !important;
}

.assign-group-permission-page #exampleContractorGroup th:first-child,
.assign-group-permission-page #exampleContractorGroup td:first-child,
.assign-group-permission-page #exampleContractorGroup col:first-child {
  width: 30% !important;
}

.assign-group-permission-page #exampleContractorGroup th:not(:first-child),
.assign-group-permission-page #exampleContractorGroup td:not(:first-child),
.assign-group-permission-page #exampleContractorGroup col:not(:first-child) {
  width: 17.5% !important;
}

.assign-group-permission-page #exampleContractorGroup .control {
  width: 20px;
  min-width: 0;
  padding-left: 0;
}

.assign-group-permission-page #exampleContractorGroup .control .checktxt { display: none; }
.assign-group-permission-page .assets_tabil .control.control--radio { top: 0 !important; }

.assign-group-permission-page #exampleContractorGroup_wrapper .records {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 8px;
}

.assign-group-permission-page .user-item,
.assign-group-permission-page .user-item2 {
  position: relative;
  width: 80%;
}
.assign-group-permission-page .user-item { top: 18px; }
.assign-group-permission-page .checktxt { opacity: 0; }
.assign-group-permission-page .group-centered-cell,
.assign-group-permission-page .main_model_footer { text-align: center; }
.assign-group-permission-page#logmodal .modal-dialog { width: 60%; }
.assign-group-permission-page#myModal .taskinfoclose {
  position: absolute;
  right: 15px;
  top: 13px;
}
.assign-group-permission-page .clsextrapadd { padding-top: 23px; }
.assign-group-permission-page .btn-group ul {
  position: absolute;
  max-height: 300px;
  overflow-y: auto;
  overflow-x: hidden;
  max-width: 300px;
}
.assign-group-permission-page .btn-group { top: -4px; }
.assign-group-permission-page .EmpTBoxR .multiselect { width: 300px; max-width: 100%; }
.assign-group-permission-page .payrl .btn-group { top: 0 !important; }

@media (max-width: 768px) {
  .assign-group-permission-page #exampleContractorGroup th,
  .assign-group-permission-page #exampleContractorGroup td {
    padding-left: 4px !important;
    padding-right: 4px !important;
    font-size: 12px;
  }
}

.manage-race-page .dt-length span,
.manage-gender-page .dt-length span,
.manage-marital-status-page .dt-length span,
.termination-reason-page .dt-length span,
.contractor-groups-page .dt-length span,
.assign-group-permission-page .dt-length span,
.custom-info-page .dt-length span,
.absence-reason-page .dt-length span,
.certification-page .dt-length span,
.badge-type-page .dt-length span {
  display: none;
}

.manage-race-page .records,
.manage-gender-page .records,
.manage-marital-status-page .records,
.termination-reason-page .records,
.contractor-groups-page .records,
.assign-group-permission-page .records,
.custom-info-page .records,
.absence-reason-page .records,
.certification-page .records,
.badge-type-page .records {
  text-align: center;
  margin: 20px 0px;
}

/* Fix for example wrapper records (search, pagination) overflow */
#example_wrapper .records {
  overflow-x: hidden;
}

/* ================================================================
"Export To" dropdown (personnel/field-training-input.php)
================================================================ */

/* FIX [FDCM-3547]: this page's "Export To" button is plain Bootstrap 3
   markup - "<button class="btn btn-secondary dropdown-toggle">Export To
   <span class="caret"></span></button>" - which combines with two other
   sitewide things to produce the reported look:
   1. Bootstrap 5's own ".btn-secondary" is a solid dark-grey button
      (confirmed live: rgb(108,117,125)), not the plain white/bordered
      button DevOps shows for this style of button elsewhere.
   2. Two carets: the ".caret" rule earlier in this file restores the
      Bootstrap-3-style triangle (needed sitewide since Bootstrap 5 no
      longer renders a bare "<span class='caret'>" at all) - but Bootstrap
      5 also draws its OWN caret via "::after" on any ".dropdown-toggle",
      so this button ends up with both at once. Same double-caret shape
      already fixed for position-title.php's filter dropdown elsewhere in
      this file (search for "already renders its own .caret element");
      suppressing the Bootstrap 5 pseudo-caret here the same way, since
      this page's caret is the restored ".caret" span, not the other way
      around.
   Also restyled the dropdown menu's items: they're bare "<a>" tags with
   no ".dropdown-item" class, so they inherited the sitewide link blue
   instead of Bootstrap's normal dark dropdown-item text - confirmed via
   reference screenshot showing dark "PDF"/"EXCEL" text, not blue links.
   ".field-training-export" is unique to this page (grep confirms), so
   scoped directly without a body-class/:has() guard. */
.field-training-export .dropdown-toggle.btn-secondary {
  background-color: #fff !important;
  color: #333 !important;
  border: 1px solid #ccc !important;
}

.field-training-export .dropdown-toggle::after {
  display: none !important;
  content: none !important;
}

.field-training-export .dropdown-menu a {
  color: #333 !important;
  display: block !important;
  padding: 4px 16px !important;
  text-decoration: none !important;
}

.field-training-export .dropdown-menu a:hover {
  background-color: #f0f0f0 !important;
}

.personnel-field-training-input-page #example_wrapper div.dt-search {
  margin-right: 16px;
}

.personnel-field-training-input-page #row1 .multiselect-native-select .multiselect-container.dropdown-menu.show {
  min-width: 320px !important;
}

.personnel-portal-personnel-acknowledgement-history-page .container:has(.work-type-s) {
  max-width: 100% !important;
}

.personnel-portal-personnel-acknowledgement-history-page #example_wrapper div.dt-table-scroll td.dt-empty {
  text-align: center !important;
}

.personnel-portal-personnel-acknowledgement-history-page #example_wrapper div.dt-paging {
  margin: 0 10px !important;
}

.personnel-portal-contractor-company-invoicing-approval-page #dtable_schedule_contractor_wrapper div.dt-info {
  text-align: center !important;
}

.personnel-portal-contractor-company-invoicing-approval-page #dtable_schedule_contractor_wrapper div.dt-paging {
  width: 100% !important;
}

.personnel-portal-contractor-company-invoicing-approval-page #dtable_schedule_contractor_wrapper div.dt-paging nav {
  margin: 0 auto !important;
}

.personnel-portal-timesheet-approval-loc-page #dismodal .modal-dialog {
  width: 40% !important;
}

.personnel-portal-timesheet-approval-loc-page #dismodal .modal-dialog .modal-body input[type="text"]#up_date {
  background-color: #fff !important;
}

/* the jQuery UI datepicker gets appended inside .payrl containers on some pages;
   the 200px min-width above is for grid link cells and blows up the calendar's
   table-layout:auto column widths (~200px x 7 days) if not reset here */
.personnel-portal-timesheet-approval-loc-page .modal-content table.ui-datepicker-calendar {
  width: 100%;
}

.personnel-portal-timesheet-approval-loc-page .payrl .ui-datepicker td a {
	min-width: auto;
	text-align: right !important;
}

.personnel-portal-timesheet-approval-loc-page .modal-content .modal-body .last-btn .save-btn:nth-child(2) a {
  height: auto !important;
}

.personnel-portal-work-order-billing-history-page #example_wrapper .records .dt-length span {
  display: none;
}

.personnel-portal-work-order-billing-history-page #example_wrapper .records .dt-search {
  margin-right: 16px;
}

.personnel-portal-work-order-billing-history-page #example_wrapper div.dt-table-scroll td.dt-empty {
  text-align: center !important;
}

.personnel-portal-cdb-personnel-page #example_new_wrapper #example_new_filter.dt-search {
  margin-top: 0 !important;
}

.personnel-portal-supply-request-page #addsupply .modal-dialog {
  max-width: 675px !important;
}

.personnel-portal-personnel-deduction-page .dt-container .dt-paging {
  margin-left: 16px !important;
}

.personnel-portal-contractor-tech-status-page #dtable_contractor_tech_status_wrapper .dt-search {
  margin-right: 16px;
}

.personnel-portal-timesheet-history-indivisual-page div#example_wrapper .records {
  margin-top: 10px;
}

.personnel-portal-timesheet-history-indivisual-page #example_wrapper .records div.d-md-flex {
  margin-top: 2px;
}

.personnel-portal-timesheet-history-indivisual-page #example_wrapper .records div.dt-paging {
  margin: 0 10px !important;
}

.hr-settings-hr-support-settings-page #example_wrapper .dt-table-scroll {
    overflow-x: hidden !important;
}

.hr-settings-hr-support-settings-page #example_wrapper .dt-search {
  margin-right: 16px;
}

.hr-settings-support-ticket-form-config-page #support_form_config_modal table#example tbody td {
  text-align: center !important;
}

.asset-info-settings-page .dt-container:has(#example3) .dt-paging, 
.asset-info-settings-page .dt-container:has(#example4) .dt-paging, 
.asset-info-settings-page .dt-container:has(#example5) .dt-paging, 
.asset-info-settings-page .dt-container:has(#example6) .dt-paging {
  display: inline-block !important;
  width: auto !important;
}

.asset-info-settings-page .dt-table-scroll {
  overflow-x: hidden !important;
  overflow-y: hidden !important;
}

.asset-info-settings-page .works_gap {
  margin-top: 20px;
}

.asset-info-settings-page .works_gap .col-md-6.PerBorL:nth-child(3),
.asset-info-settings-page .works_gap .col-md-6.PerBorL:nth-child(4) {
  margin-top: 20px;
}

.payroll-que-local-page .records div.dt-search {
  margin-right: 16px;
}

.payroll-que-local-page .records div.dt-search input {
  margin-top: 0px;
}

.payroll-que-local-page #example tbody td:nth-child(3) {
  text-align: center !important;
}

.payroll-que-local-page #example {
  margin: 0px !important;
}

.payroll-que-local-page #example_wrapper .dt-table-scroll {
  overflow-y: hidden !important;
}

.payroll-que-local-page #example tbody td:nth-child(1) {
  display: block;
  margin-right: 10px;
}

.payroll-documents-page .faq-cat-content .card h4.card-title img {
  width: 5%;
  float: left;
}

.payroll-documents-page .faq-cat-content .card h4.card-title div.text-acc {
  width: 85%;
  float: left;
}

.payroll-documents-page .faq-cat-content .card h4.card-title span.mrt {
  margin-top: 0px;
}

.payroll-documents-page .faq-cat-content .card h4.card-title div.text-acc h5,
.payroll-documents-page .faq-cat-content .card h4.card-title div.text-acc h6 {
  font-size: 14px;
}

.payroll-documents-page .card-body #example_wrapper #example tbody td {
  text-align: center !important;
}

/* FIX: carbon-theme.css's ".qc_mainPrat { background-color: var(--cds-layer-01)
   !important }" ("Gray 10 content layers") paints every .qc_mainPrat panel
   #f4f4f4 sitewide. ats.i-t-g.net's reference instead has .qc_mainPrat's own
   pre-migration #e6e6e6 background/#222 text - but NOT uniformly: verified
   live (getComputedStyle) against every .qc_mainPrat on ats's rendering of
   this exact page and found 3 distinct cases, not 1:
     1) the individual content cards (payscale filter form, "Add Vehicle Comp
        Scale", the import-log/duplicate-scheduler tables, etc.) are #e6e6e6.
     2) the one large OUTER ".qc_mainPrat" that wraps the whole lower section
        (containing ".big-table.payrl.pay-acc") stays WHITE (its own inline
        style="background:#fff", which carbon-theme.css's !important had
        been overriding same as the others) - this is what creates the
        visible white "gap" between the individual gray cards inside it.
     3) the empty ".qc_mainPrat.payscale-table" spacer div is fully
        TRANSPARENT, not gray.
   A single blanket #e6e6e6 override (an earlier version of this fix) made
   every .qc_mainPrat gray including cases 2 and 3, erasing the white gaps
   ats shows between cards - hence the 3 rules below instead of 1. Scoped to
   this page's own auto-generated body class (see include/header.php's
   $fuse_page_body_class) since .qc_mainPrat is reused ~4000 times sitewide. */
.payroll-payscales-local-v2-page .qc_mainPrat {
  background-color: #e6e6e6 !important;
  color: #222 !important;
}
.payroll-payscales-local-v2-page .qc_mainPrat:has(.big-table.payrl.pay-acc) {
  background-color: #fff !important;
}
.payroll-payscales-local-v2-page .qc_mainPrat.payscale-table {
  background-color: transparent !important;
}
/* Explicit header background for every DataTable on this page, matching
   the card's #e6e6e6 - belt-and-suspenders alongside the .qc_mainPrat rule
   above, which already makes this the inherited value since thead/th have
   no background of their own; written explicitly per direct request. */
.payroll-payscales-local-v2-page table.dataTable thead th,
.payroll-payscales-local-v2-page table.dataTable thead td {
  background-color: #e6e6e6 !important;
}
/* FIX: a sitewide Bootstrap5 ".table" rule gives every thead/tbody/tfoot
   cell a "border-top: 1px solid #fff" (a grid-line separator meant to show
   between rows of different shades) - on the very first (header) row
   there's nothing above it to separate from, so it just renders as a
   stray white hairline above the header. ats has no such border. Scoped
   to just the header row since body rows still want their separator. */
.payroll-payscales-local-v2-page table.dataTable thead th,
.payroll-payscales-local-v2-page table.dataTable thead td {
  border-top: 0 !important;
}
/* FIX: DataTables 3's Bootstrap5 ".table-striped" skin darkens ODD rows
   with a black-tinted inset box-shadow at a fixed 0.05 opacity
   (--dt-row_background-stripe defaults to "0, 0, 0") - both the direction
   (odd should be the LIGHT row, per ats) and the intensity (0.05 opacity
   over #e6e6e6 is barely a 5-level shade difference) were wrong. ats's
   reference (older DataTables 1.x "odd"/"even" row classes) instead sets
   flat colors: odd rows #f9f9f9, even rows transparent (showing the card's
   #e6e6e6 through) - a ~19-level difference, clearly visible. Replacing
   the box-shadow approach with the same flat colors matches ats exactly
   rather than just approximating the tint direction. */
.payroll-payscales-local-v2-page table.dataTable.table-striped > tbody > tr:nth-of-type(odd) > * {
  box-shadow: none !important;
  background-color: #f9f9f9 !important;
}
.payroll-payscales-local-v2-page table.dataTable.table-striped > tbody > tr:nth-of-type(even) > * {
  box-shadow: none !important;
  background-color: transparent !important;
}
/* FIX: the "Duplicate Payscale Rates from:" row's last <td> only holds a
   hidden (style="display:none") loading spinner <img id="run_loader">,
   but table-layout:auto still reserved ~70px for that cell (browsers can
   size an auto-layout column from a hidden replaced element's width/height
   attributes even though it paints nothing) - on top of the oversized
   Select2 hidden-accessible select fixed above, this pushed the row 17px
   past the viewport, clipping the leading "D" of the first cell's label
   and adding a horizontal scrollbar. Collapsing this cell to zero width
   removes that extra reserved space. */
.payroll-payscales-local-v2-page td:has(> #run_loader) {
  width: 0 !important;
  padding: 0 !important;
}
.payroll-payscales-local-v2-page .dt-search {
  margin-right: 10px;
}
.payroll-payscales-local-v2-page .dt-search input#dt-search-0,
.payroll-payscales-local-v2-page .dt-search input#dt-search-1,
.payroll-payscales-local-v2-page .dt-search input#dt-search-2 {
  margin-top: 5px;
}
.payroll-schedule-personnel-payroll-summary-page #myModal {
  width: 50%;
  margin-left: 25%;
}
.payroll-schedule-personnel-payroll-summary-page #dtable_schedule_contractor_wrapper .records {
  margin-top: 10px;
}
.payroll-schedule-personnel-payroll-summary-page #dtable_schedule_contractor_wrapper .records .dt-search {
  margin-right: 16px;
}
.payroll-schedule-payscales-local-v2-page #myModal {
  width: 50%;
  margin-left: 25%;
}
.payroll-schedule-payscales-local-v2-page #dtable_schedule_contractor_wrapper .records {
  margin-top: 10px;
}
.payroll-schedule-payscales-local-v2-page #dtable_schedule_contractor_wrapper .dt-search,
.payroll-schedule-payscales-local-v2-page #example3_wrapper .dt-search {
  margin-right: 16px;
}
.payroll-schedule-payscales-local-v2-page #exampleImport_wrapper .dt-length {
  justify-content: center;
}
.payroll-schedule-payscales-local-v2-page .real-page-content .records .dt-search {
  text-align: left;
}
.payroll-schedule-payscales-local-v2-page .real-page-content .records #exampleImport_wrapper input {
  width: auto !important;
}
.payroll-update-cron-with-emp-ids-page #viewlog_modal .modal-dialog {
  width: 50%;
  margin-left: 25%;
}
.payroll-commit-globalSp-page .container .center-part a {
  color: #FFF !important;
}
.payroll-commit-globalSp-page #example_wrapper .dt-table-scroll {
  overflow-x: hidden;
  overflow-y: hidden;
}
.payroll-close-local-new-process-NN-page #sel_wo_cnt_div .single-line ul li a,
.payroll-close-local-new-process-NN-page #sel_wo_cnt_div .big-hei-btn a {
  color: #FFF !important;
}
.payroll-close-local-new-process-NN-page #main_table_wrapper .dt-table-scroll {
  overflow-x: hidden;
  overflow-y: hidden;
}
.payroll-personnel-cron-stoted-vs-live-schedule-daly-RR-SP-gl-page .monthly_section.RecPattSection {
  width: 345px;
}
.payroll-personnel-cron-stoted-vs-live-schedule-daly-RR-SP-gl-page .monthly_section.RecPattSection .custom-control {
  margin-bottom: 10px;
}
.payroll-personnel-cron-stoted-vs-live-schedule-daly-RR-SP-gl-page #myModal .modal-dialog {
  width: 50%;
  margin-left: 25%;
}
.payroll-personnel-cron-stoted-vs-live-schedule-daly-RR-SP-gl-page #dtable_schedule_contractor_wrapper .records {
  margin-top: 10px;
}
.payroll-personnel-cron-stoted-vs-live-schedule-daly-RR-SP-gl-page #dtable_schedule_contractor_wrapper .dt-search {
  margin-right: 16px;
}
.payroll-get-emp-list-page #chk_ofc_form .multiselect-container.dropdown-menu.show {
  min-width: 300px !important;
}
.payroll-personnel-cron-unconfirmed-time-page .monthly_section.RecPattSection {
  width: 345px;
}
.payroll-personnel-cron-unconfirmed-time-page .monthly_section.RecPattSection .custom-control {
  margin-bottom: 10px;
}
.payroll-personnel-cron-unconfirmed-time-page #myModal {
  width: 50%;
  margin-left: 25%;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-buttons .buttons-collection {
  min-width: 116px;
  position: relative;
  top: 45px;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-buttons .buttons-collection:after {
  content: "";
  display: inline-block;
  margin-left: 8px;
  vertical-align: middle;
  border-top: 4px dashed;
  border-right: 4px solid transparent;
  border-left: 4px solid transparent;
}
/* FDCM-3547: js-upgrade-fix.css hides this caret sitewide
  (".dt-container .dt-buttons .buttons-collection::after") so every
  migrated page's collection buttons match -- but ats.i-t-g.net's
  "Export To" still shows one, so restore it just here. */
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-buttons .buttons-collection::after {
  display: inline-block !important;
}
.payroll-misc-pay-import-page .dt-button-collection {
  min-width: 116px;
}
.payroll-misc-pay-import-page .dt-button-collection .dt-button {
  display: block;
  margin: 0 !important;
  text-align: left;
  width: 100%;
}
/* FDCM-3547: match ats.i-t-g.net's "Export To" popup. The sitewide
  rule ".dt-container .dt-buttons .buttons-html5, .buttons-collection"
  (js-upgrade-fix.css) is meant for the top-level trigger buttons, but
  it matches on class alone -- since each popup item is a <li
  class="dt-button buttons-excel buttons-html5"> descended from that
  same ".dt-container .dt-buttons", it incidentally gets swept up too,
  already giving the <li> the flat gray/bordered button look (and,
  via the ".btn-group ... buttons-html5" variant, a 4.1px
  "margin-left" meant to gap horizontally-adjacent trigger buttons --
  harmless there, but it knocks every popup row after the first out
  of alignment here). The <li>'s child is a Bootstrap ".dropdown-item"
  anchor (old stack rendered these as plain ".dt-button" anchors,
  already covered above), which has no styling of its own, so it
  falls through to carbon-theme.css's sitewide "a:not(...)"
  link-color rule and renders link-blue instead of black. */
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-button-collection {
  padding: 8px 8px 4px !important;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-button-collection .dt-button {
  margin-left: 0 !important;
  margin-bottom: 4px !important;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-button-collection .dt-button:last-child {
  margin-bottom: 0 !important;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-button-collection .dt-button:hover,
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-button-collection .dt-button:focus-within {
  background: #dcdcdc !important;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper .dt-button-collection .dropdown-item {
  display: block;
  color: #000 !important;
  text-decoration: none;
  background: transparent !important;
  border: 0 !important;
  padding: 0 !important;
  text-align: center;
}
.payroll-misc-pay-import-page #miscPayImport_wrapper table.dataTable td,
.payroll-misc-pay-import-page #miscPayImport_wrapper table.dataTable th {
  text-align: center;
}
.payroll-misc-pay-import-page #miscPayImport th:nth-child(2) div.dt-column-header,
.payroll-misc-pay-import-page #miscPayImport td:nth-child(2),
.payroll-misc-pay-import-page #miscPayImport th:nth-child(3) div.dt-column-header,
.payroll-misc-pay-import-page #miscPayImport td:nth-child(3) {
  min-width: 75px !important;
  width: 90px;
}
.payroll-misc-pay-import-page div#miscPayImport_info {
  margin-top: 16px;
  text-align: center;
}
.payroll-misc-pay-import-page div#miscPayImport_paginate {
  justify-content: center;
  width: 100% !important;
}
.payroll-commit-globalSp-background-page .center-part a {
  color: #FFF !important;
}
.payroll-commit-globalSp-background-page #example_wrapper .dt-table-scroll {
  overflow-x: hidden;
  overflow-y: hidden;
}
.payroll-commit-globalSp-background-page #example_wrapper .dt-search {
  margin-right: 16px;
}
.expense-settings-expense-categories-page #expenseCategories_wrapper .dt-search {
  margin-right: 16px !important;
}
/* expense-categories.php Log modal: wrap long Old/New Settings text so the table fits with no horizontal scroll */
.expense-settings-expense-categories-page #stat_modal .modal-body { overflow-x: hidden; }
.expense-settings-expense-categories-page #stat_modal #expenseCatLog,
.expense-settings-expense-categories-page #stat_modal #expenseCatLog_wrapper { width: 100% !important; }
.expense-settings-expense-categories-page #stat_modal #expenseCatLog { table-layout: fixed; }
.expense-settings-expense-categories-page #stat_modal #expenseCatLog th,
.expense-settings-expense-categories-page #stat_modal #expenseCatLog td {
  white-space: normal !important;
  word-wrap: break-word;
  overflow-wrap: anywhere;
  text-align: center;
}
.expense-settings-expense-categories-page #stat_modal #expenseCatLog_wrapper .records .dt-search {
  margin-right: 16px !important;
}
.expense-settings-recuring-percentage-expenses-page #example6_wrapper .dt-table-scroll {
  overflow-y: hidden;
  overflow-x: hidden;
}
.expense-settings-recuring-percentage-expenses-page #example6_wrapper .records .dt-search {
  margin-right: 16px !important;
}
.expense-settings-recuring-percentage-expenses-page #example6_wrapper .records .dt-paging {
  margin-right: 16px !important;
}
.work-order-pages-work-orders-invoicing-v2-page .nav>li {
  position: relative;
  display: block;
}
.work-order-pages-work-orders-invoicing-v2-page .nav-pills>li {
  float: left;
}
.work-order-pages-work-orders-invoicing-v2-page .real-page-content .nav-wrapper .nav-pills>li>a {
  font-weight: 700;
  color: #000;
  border: 1px solid #000;
  border-bottom-left-radius: 0;
  border-bottom-right-radius: 0;
  background-color: #eee;
}
.work-order-pages-work-orders-invoicing-v2-page .nav>li>a {
  position: relative;
  display: block;
  padding: 10px 15px;
}
.work-order-pages-work-orders-invoicing-v2-page .nav>li {
  position: relative;
  display: block;
}
.work-order-pages-work-orders-invoicing-v2-page .nav-pills>li>a {
  border-radius: 4px;
}
.work-order-pages-work-orders-invoicing-v2-page #unbilled_table_data_wrapper div.dt-buttons,
.work-order-pages-work-orders-invoicing-v2-page #exampleImport1_wrapper div.dt-buttons {
  margin-top: -3px !important;
}

.supply-pages-sell-supplies-page #k_example_wrapper .btn-group>.btn,
.supply-pages-sell-supplies-page #k_example2_wrapper .btn-group>.btn {
  margin-right: 5px;
}
.personnel-timesheet-correction-prior-weekN-page #example_wrapper .dt-search {
  margin-right: 16px !important;
}

/* Classic construction settings pages do not receive .itg-construction. */
body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) .crew-view {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: center;
  gap: 16px;
  width: 100%;
}

body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) .crew-view-radios,
body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) .crew-view-radios #frm_enable_sort {
  display: flex;
  flex-wrap: nowrap;
  align-items: center;
  gap: 16px;
  margin: 0;
}

body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) .crew-view .control.control--radio {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 0;
  margin: 0;
  white-space: nowrap;
}

body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) .crew-view .control.control--radio .control__indicator {
  position: relative !important;
  top: auto !important;
  left: auto !important;
  order: -1;
  flex: 0 0 20px;
  margin: 0;
}

body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) #example_wrapper .dt-table-scroll {
  overflow-x: hidden !important;
  overflow-y: hidden !important;
}

body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) #example_wrapper .dt-search {
  margin-right: 16px !important;
}

body:is(.construction-project-status-settings-page, .construction-payment-terms-settings-page,
  .construction-project-type-page, .construction-co-ordinators-page,
  .construction-invoice-status-settings-page, .construction-billing-status-page) #example_wrapper .dt-paging {
  margin-right: 16px !important;
}

#onb_form_log_table_wrapper .dt-length label,
#onb_form_log_table_wrapper .dt-search label,
#onb_form_setting_schedule_task_table_wrapper .dt-length label,
#onb_form_setting_schedule_task_table_wrapper .dt-search label {
  display: none;
}

#onb_form_log_table_wrapper .dt-search input,
#onb_form_setting_schedule_task_table_wrapper .dt-search input {
  margin-top: 0 !important;
}
/*  Members | Add/Remove | Available Contractors three-across.
    Members' col-md-4 is inside <form>, the other two are the form's
    siblings. */
@media (min-width: 768px) {
  .personnel-contractor-groups-test-page .supv .membors_off {
    display: flex;
    align-items: center;
  }
  .personnel-contractor-groups-test-page .supv .membors_off > form,
  .personnel-contractor-groups-test-page .supv .membors_off > .office_box {
    flex: 0 0 33.333333%;
    width: 33.333333%;
    max-width: 33.333333%;
    min-width: 0;
  }
  /* flow-root so it wraps its floated .box1 and keeps its 25px margin,
      otherwise Members sits ~12px lower than Available Contractors. */
  .personnel-contractor-groups-test-page .supv .membors_off > form > .office_box {
    display: flow-root;
    float: none;
    width: 100%;
    max-width: none;
  }
}

.personnel-contractor-groups-test-page #ui-datepicker-div.ui-datepicker {
  z-index: 99999 !important;
}

.personnel-position-title-page ul.multiselect-container.dropdown-menu {
  min-width: 250px !important;
}

/* Edit Group Members: Members | Add/Remove | Available Members three-across.
   Members' col-md-4 sits inside <form id="form2">, the other two are the form's
   siblings; ".office_grp1.membors_off > form { display: flow-root }" above makes
   the form a full-width row, dropping the other two below it. Flex the row
   instead (same fix as contractor-groups). flow-root on the inner box wraps its
   floated .box1 so its 25px margin counts, keeping Members level with Available. */
@media (min-width: 768px) {
  .personnel-supervisor-groups-page .membors_off {
    display: flex;
    align-items: center;
  }

  .personnel-supervisor-groups-page .membors_off > form,
  .personnel-supervisor-groups-page .membors_off > .office_box {
    flex: 0 0 33.333333%;
    width: 33.333333%;
    max-width: 33.333333%;
    min-width: 0;
  }

  .personnel-supervisor-groups-page .membors_off > form > .office_box {
    display: flow-root;
    float: none;
    width: 100%;
    max-width: none;
  }

  .personnel-supervisor-groups-page .self_qs.col-md-12.col-sm-12.col-12.edit_memb {
    margin-top: 25px;
  }

  .personnel-supervisor-groups-page .self_qs.col-md-12.col-sm-12.col-12.edit_memb label {
    text-align: center;
    width: 100%;
  }
}

/* FDCM-3547: this page nests Bootstrap columns in plain divs, not .row.
   Bootstrap 3 floated every column so they sat side by side; Bootstrap 5
   columns only do that inside a flex .row, so here each stacked full width:
   "Outstanding Issues" dropped under the title, the Inventory Check List /
   Status Log / Crew Log panel fell below the Termination box, and every
   label sat above its field. Give those parents .row's flex layout.
   Labels stay top-aligned with their fields, like the floated original. */
@media (min-width: 768px) {
  .personnel-personnel-status-page .col-md-9.offset-sm-3,
  .personnel-personnel-status-page #ajaxResp > .col-md-12,
  .personnel-personnel-status-page #ajaxResp .pad-big,
  .personnel-personnel-status-page #ajaxResp .entry {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
  }

  /* was float-end (pull-right): keep it at the right of the title row */
  .personnel-personnel-status-page .col-md-9.offset-sm-3 > .col-md-4.float-end {
    margin-left: auto;
  }
}

.personnel-personnel-status-page .calendar.ii[readonly] {
  background-color: #eee !important;
}

.personnel-personnel-status-page input.form-control.form-control-sm {
  margin-top: 5px !important;
}

.personnel-personnel-status-page #stat_modal button.close,
.personnel-personnel-status-page #crew_modal button.close {
  opacity: 1 !important;
}

.personnel-deduction-page .container.payrl,
.personnel-deduction-page .container.payrl .container {
  max-width: 95% !important;
}

.personnel-deduction-page #change_ofc .modal-dialog,
.personnel-deduction-page #Deduc_file_log .modal-dialog,
.personnel-deduction-page #erp_global_dialog_modal .modal-dialog {
  width: 35% !important;
}

.personnel-deduction-page #Deduc_log .modal-dialog #d_log_wrapper .justify-content-between,
.personnel-deduction-page #Deduc_file_log .modal-dialog #d_file_log_wrapper .justify-content-between {
  justify-content: center !important;
}

.personnel-deduction-page #cur_deduc_table_wrapper .dt-search,
.personnel-deduction-page #employee_table2_wrapper .dt-search,
.personnel-deduction-page #employee_table3_wrapper .dt-search,
.personnel-deduction-page #example_deduction_histry_wrapper .dt-search,
.personnel-deduction-page #Deduc_file_log .modal-dialog #d_file_log_wrapper .dt-search,
.personnel-deduction-page #Deduc_log .modal-dialog #d_log_wrapper .dt-search {
  margin-right: 16px;
}

.personnel-deduction-page #change_ofc .form-chng-ofc .form-group .col-sm-9 {
  margin-top: 15px;
}

.personnel-deduction-page #change_ofc .select2-container {
  z-index: 99999;
}

.personnel-deduction-page #change_ofc.modal .last-btn .save-btn:nth-child(2) a {
  padding: 5px 25px;
  background-color: #e6e6e6 !important;
  border-radius: 4px !important;
  color: #212121 !important;
  border: 1px solid #ccc !important;
}

.personnel-deduction-page #change_ofc.modal .last-btn .save-btn:nth-child(2) a:hover {
  color: #212121 !important;
  background-color: #e6e6e6 !important;
  border: 1px solid #999 !important;
}

.personnel-deduction-page #employee_table2_wrapper td:nth-child(2) select {
  margin-top: 0px;
}

.personnel-deduction-page #employee_table3_wrapper select.drop-change,
.personnel-deduction-page #employee_table3_wrapper select.drop-filter,
.personnel-deduction-page #employee_table3_wrapper select.drop-subfilter {
  margin-top: 1px;
}

.personnel-deduction-page .select2-container {
  z-index: 99999;
}

.personnel-deduction-page .modal-dialog .dt-table-scroll table tr td {
    text-align: center;
}

.personnel-contractor-retainage-page #dataTables-retainagewithid_wrapper .dt-table-scroll {
  overflow-y: hidden;
}

.personnel-contractor-retainage-page input.form-control.form-control-sm {
  margin-top: 5px !important;
}

.personnel-contractor-retainage-page #dataTables-retainagewithid_wrapper .justify-content-between,
.personnel-contractor-retainage-page #dataTables-retainagepaid_wrapper .justify-content-between {
  justify-content: center !important;
}

.personnel-tech-area-page #p_log_wrapper table.dataTable td.dt-type-date {
  text-align: center !important;
}

.personnel-tech-area-page #p_log_wrapper .dt-search {
  margin-right: 16px;
}

/* The single bottom cell carries Bootstrap's .me-auto (margin-right: auto !important),
   which pins it left; auto margins on both sides centre it. */
.personnel-contractor-retainage-page #dataTables-retainagewithid_wrapper .dt-layout-start.me-auto,
.personnel-contractor-retainage-page #dataTables-retainagepaid_wrapper .dt-layout-start.me-auto {
  margin-left: auto !important;
  margin-right: auto !important;
}

/* FDCM-3547: each ".entry" row (Production Bonus Eligible, Pay Period,
   PTO Accrual, ... Annual Bonus) puts its label and field columns
   (col-md-4 / col-md-8 / col-md-1) in a plain div, not a .row. Bootstrap 3
   floated them side by side; Bootstrap 5 columns only do that inside a
   flex .row, so every label sat above its field and "Bank Information"
   dropped into the form. Give those rows .row's flex layout (not the
   hidden ".entry.hide" row, which display:flex would reveal). */
@media (min-width: 768px) {
  .personnel-paysetup-hr-page .qc_mainPrat > .entry:not(.hide),
  .personnel-pay-setup-page .qc_mainPrat > .entry:not(.hide),
  .personnel-pay-setup-page .gen.mb20:not(.hide),
  #normal_accural_modal .gen.mb20:not(.hide),
  #change_accural_modal .gen.mb20:not(.hide) {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
  }
}

/* FDCM-3547: Prior Pay History's nine min-width columns total ~1014px; the
   BS5 card is 24px narrower than ATS's BS3 one, so both the legacy
   "div.records" wrapper (overflow-x:auto) and DT3's .dt-table-scroll drew a
   horizontal scrollbar for ~8px. The table still fits inside the card. */
.personnel-paysetup-hr-page .records:has(> #example3_wrapper),
.personnel-paysetup-hr-page #example3_wrapper .dt-table-scroll {
  overflow-x: visible;
}

.personnel-information-page .SButsbox a:last-child {
  color: #000 !important;
}

.personnel-information-page .self_qs label {
  margin: 0px;
  padding: 50px 0 11px;
  font-size: 26px;
  text-transform: uppercase;
  float: left;
  width: 100%;
}

.personnel-import-users-page .modal-dialog #example_wrapper tbody tr td,
.personnel-import-users-page .modal-dialog table#example tbody tr td {
  text-align: center !important;
}

/* FDCM-3547: the upgraded bootstrap-multiselect wraps the select in
   span.multiselect-native-select { position: relative }, which makes it the
   containing block of the absolutely positioned .btn-group above. That puts
   the button and its menu inside .table-responsive's overflow box, so the
   -233px offset cut off the button's left edge and the options list was
   clipped to just the search row. Static restores the ATS behaviour where
   the dropdown escapes the scroll box. */
.personnel-training-page td > .multiselect-native-select {
  position: static;
}

/* FDCM-3547: below 1366px the generic ".btn-group:has(> .multiselect.dropdown-toggle)
   { width: 100% !important }" rule applies. With the span above now static, that
   100% resolves against a far page container instead of the table cell, so at
   1280px the Certifications button stretched across the whole row and covered
   the Cert Date / Expiration / Upload Doc fields. Keep the plugin's 435px
   buttonWidth, matching ATS at every width. */
.personnel-training-page td > .multiselect-native-select > .btn-group:has(> .multiselect.dropdown-toggle) {
  width: 435px !important;
}

/* FDCM-3547: BS5 uses .show instead of BS3 .open, so the 240px menu height
   rule above no longer applied to the certification list. */
.personnel-training-page td .multiselect-container.dropdown-menu.show {
  height: 240px;
  overflow-y: scroll;
}

/* FDCM-3547: the form's inner .container (inside .gen) is still capped at
   BS5's 1320px, indenting the Training Review / Certifications rows; ATS
   spans the full page width. */
.container.payrl.traning-n .Middle.badge-type .gen > .container {
  max-width: none !important;
}

.construction-construction-project-summary-page #tblWorkOrderInSummaryPage_wrapper .records,
.construction-construction-project-summary-page #ProjectNotes_Table_wrapper .records {
  margin-top: 10px;
}

.construction-construction-project-summary-page #tblWorkOrderInSummaryPage_wrapper .dt-search,
.construction-construction-project-summary-page #ProjectNotes_Table_wrapper .dt-search {
  margin-right: 16px;
}

.construction-construction-project-summary-page #tblWorkOrderInSummaryPage_wrapper .dt-paging {
  margin-left: 16px !important;
}

/* FDCM-3547: personnel-portal/work-order-billing-history.php - the heading
   ".container" only holds a floated ".Middle" (style-new.css), and Bootstrap 5's
   ".container" has no clearfix (BS3's did), so it collapses to 0px height. The
   following ".big-table" has overflow-x:auto (a new formatting context), so below
   the 1600px breakpoint it squeezed into the ~75px left beside the float and the
   name / week checkbox / DataTable rendered as a thin column at the right edge.
   Clearing the float drops it below the heading as on ats.
   header.php now moves the page content into "#fuse-page-scroll", so ".big-table"
   is no longer a direct child of <body>; the second selector covers that wrapper. */
.personnel-portal-work-order-billing-history-page > .big-table,
.personnel-portal-work-order-billing-history-page > #fuse-page-scroll > .big-table {
  clear: both;
}

/* FDCM-3547: personnel-portal/personnel-acknowledgement.php - BS5 flex-grid
   leftovers after the body restore (layout now matches ats):
   - style-new.css ".qc_pic { height: 100% }" was inert under BS3 floats (auto-
     height parent) but the BS5 flex column is stretched to the row, so the
     Self QC picture box grew to the full column height;
   - BS3 .img-responsive was display:block, BS5 .img-fluid is inline, leaving a
     baseline gap under each picture;
   - Fleet Assignment wraps its col-md-5 / col-md-5 / col-md-2 in a <form>
     inside .row, so only the form is a flex item and the columns stacked;
     make the form the flex row instead;
   - CPE Assignment / Asset Repair / Asset Lost / CPE Return sections sit in
     forms that are direct .row children, which BS5 ".row > *" pads by 12px
     each side, making those cards 24px narrower than the others. */
.personnel-portal-personnel-acknowledgement-page .qc_pic {
  height: auto;
}

.personnel-portal-personnel-acknowledgement-page .qc_pic > img.img-fluid {
  display: block;
}

.personnel-portal-personnel-acknowledgement-page .self-div > .row > form {
  display: flex;
  flex-wrap: wrap;
  width: 100%;
  padding-left: 0;
  padding-right: 0;
}

.personnel-portal-personnel-acknowledgement-page .gen > .row > form {
  padding-left: 0;
  padding-right: 0;
}

/* FDCM-3547: BS5 moved column gutters from
   ".col-*" to ".row > *", so these
   row-less columns lost BS3's 15px side
   padding - the folder list ran straight
   into the preview panel and the search row
   lost its left inset. Restore it as on ATS.
   (The keyword input's inline
   "right: 25px" from commit 4d1ca33a496 was
   removed too: it slid the input left over
   the Folder/File select; not in master.) */
.personnel-portal-itg-document-resource-page .Middle > .col-sm-12,
.personnel-portal-itg-document-resource-page .itg-folder-container,
.personnel-portal-itg-document-resource-page #itg-preview-section {
  padding-left: 15px;
  padding-right: 15px;
}

/* FDCM-3547: keep the search box at its
   col-sm-5 width (41.67%) like ATS instead of
   growing to 50%, so the search icon and
   Reset sit where they do on ATS. */
.personnel-portal-itg-document-resource-page .doc-resource-search-row > .col-sm-5 {
  flex: 0 0 41.6667% !important;
  max-width: 41.6667%;
}

/* FDCM-3547: BS5 ".input-group" joins its children (margin-left:-1px, very
   high-specificity :not() chain), so the search button was glued to the input
   and Reset sat top-aligned in the 41px-tall flex row. ATS shows an ~11px gap
   before the button and Reset vertically centred on it. */
.personnel-portal-itg-document-resource-page .doc-resource-search-row > .col-sm-5 > .input-group-btn:not(.reset-btn) {
  margin-left: 11px !important;
}

.personnel-portal-itg-document-resource-page .doc-resource-search-row > .col-sm-5 > .reset-btn {
  margin-left: 0 !important;
  display: flex;
  align-items: center;
  height: 35px;
}

/* FDCM-3547: the saved signature (#exisiting_signature) and initials
   (#exisiting_signature_ini) images are position:absolute; left:50%, sized
   to their own column. BS3 gave every .col-md-* position:relative, so each
   centred inside its own column; BS5 columns are static, so both resolved
   against .container and the adopted initials landed on top of the
   signature box. Restore the column containing block (as on ATS). */
.personnel-portal-digi-psignature-page .container > .row > [class*="col-md-"] {
  position: relative;
}

/* FDCM-3547: the terms row starts flush against the fixed header's bottom edge
   (body padding-top = header height), and .terms_button / .terms-accept-text are
   nudged up with negative "top" offsets, so "I Accept" and View Terms slid under
   the blue module menu. Give the row some clearance below the menu. */
.personnel-portal-digi-psignature-page .terms-accept-row {
  margin-top: 25px;
}

/* FDCM-3547: js-upgrade-fix.css hides every DataTables wrapper (opacity:0)
   until header.php marks it .itg-dt-ready after its first draw. get_data()
   destroys and rebuilds this server-side grid on every Filter / date arrow /
   status change, so the whole grid - including its processing indicator -
   was invisible for the entire AJAX request. Keep it visible so the
   "Processing..." indicator shows while loading, as on ATS. */
.personnel-portal-contractor-company-invoicing-approval-page #dtable_schedule_contractor_wrapper {
  opacity: 1;
}

/* FIX: report/project-work-order-report.php's Status multiselect is
   initialised with "buttonWidth: '116px'". The sitewide
   ".multiselect-container.dropdown-menu" rule above forces the menu to
   "width: 100%" of that 116px button with "overflow-x: hidden", so the
   option labels ("Pending Setup", "Ready for Work", "Bid Proposal") and
   the search box were clipped. On ATS (Bootstrap 3) the menu kept its own
   160px min-width and grew to fit its content past the narrow button.
   Restore that: let the menu size to its content, never narrower than the
   button. Scoped to #filter_WorkStatus + #dtable_schedule_contractor
   together - each ID alone is reused on dozens of other pages
   (order-management, project-work-order, contractor invoicing, ...). */
body:has(#dtable_schedule_contractor):has(#filter_WorkStatus) .multiselect-container.dropdown-menu {
  width: auto !important;
  min-width: 160px !important;
  white-space: nowrap;
}

body.construction-expenses-page .heading_bold {
  justify-self: center;
  text-align: center !important;
}

/* FDCM-3547: construction/expenses.php - centre the #form3 filter block as one
   ~580px column: Expense type full width, Start/End and Filter/Reset as
   side-by-side pairs. Layout only; theme colours/borders are untouched. */
body.construction-expenses-page #form3 > .row {
  display: flex;
  flex-direction: column;
  align-items: stretch;
  max-width: 580px;
  margin: 0 auto 24px;
  gap: 12px;
}
body.construction-expenses-page #form3 > .row > .col-sm-3,
body.construction-expenses-page #form3 > .row > .form-group {
  flex: 0 0 auto;
  width: 100%;
  max-width: 100%;
  margin: 0;
  padding: 0;
}
body.construction-expenses-page #form3 > .row .btn-group,
body.construction-expenses-page #form3 > .row .multiselect {
  width: 100%;
}
body.construction-expenses-page #form3 > .row > .form-group table {
  width: 100%;
  border-collapse: separate;
  border-spacing: 0;
}
body.construction-expenses-page #form3 > .row > .form-group td {
  width: 50%;
  padding: 0;
  vertical-align: top;
}
body.construction-expenses-page #form3 > .row > .form-group td + td {
  padding-left: 10px;
}
body.construction-expenses-page #form3 > .row > .form-group td > input {
  width: 100%;
  max-width: 100%;
}

body.construction-expenses-page .qc_mainPrat:has(#expense_types) {
  overflow-x: clip;
  overflow-y: visible;
  position: relative;
  z-index: 20;
}
body.construction-expenses-page #exp-type .multiselect-container {
  z-index: 1050;
}

/* FDCM-3547: clipped DataTables search box (sitewide).
   que-local.css ".form-control { margin-top: -5px }" pulls the DataTables 3 search
   input 5px above its row; inside an overflow:auto wrapper its top gets clipped
   (e.g. onb/contractor_recruiting.php Recruits Listing). 5px centres it on the
   "Show" select, matching the page-level fixes above; pages without que-local.css
   go from 1px to 5px.
   - :where() keeps the specificity at (0,1,1) with no !important, so every
     page-specific search-input rule still wins.
   - Grids inside modals (e.g. notice modals) are left alone.
   - Excluded pages already look right with the -5px (their fixes move the search
     container instead of the input); add a :not(.<page-class>) to exclude another. */
:where(body:not(.personnel-portal-cdb-personnel-page)
            :not(.document-store-contract-management-page)
            :not(.payroll-payscales-local-v2-page))
  .dt-search input:where(:not(.modal *)) {
  margin-top: 5px;
  margin-right: 10px;
}

/* FDCM-3547: the same -5px clip for grids inside modals, which the rule above
   skips (e.g. contractor_recruiting.php "View Log" #searchlog_modal: its grid's
   overflow:auto .records row cut off the top 5px). 1px is what modal grids get on
   pages without que-local.css (style-new.css .form-control), so only que-local
   pages change. (0,1,1), no !important: modal-specific rules still win (the notice
   modals' own rule sets the same 1px). */
:where(.modal) .dt-search input {
  margin-top: 1px;
}

/* FDCM-3547: Go / Reset buttons injected into the search box sat at different
   heights. Pages carry bare ".btn-primary { margin-bottom: 5px }" rules (e.g.
   contractor_recruiting.php:8451) that hit the Go button (btn-primary) but not
   Reset (btn-secondary); with align-items:center the extra margin lifted Go ~3px.
   Some pages also set inline vertical margins on these buttons. Zero the vertical
   margins so both centre on the same line (as several page-level fixes already do
   with "margin: 0 !important"); horizontal spacing is left as each page set it. */
.dt-search .btn {
  margin-top: 0 !important;
  margin-bottom: 0 !important;
}

/* FDCM-3547: onb/recruting_live.php Recruits grid -- blank area on first load.
   The sitewide rule above hides every DataTables wrapper (opacity:0) until
   header.php marks it .itg-dt-ready after its first draw, so the processing
   indicator was invisible during the first request (ATS shows "Processing...").
   Until the first draw: keep the rest of the grid hidden, but show the processing
   indicator. A child can override visibility (unlike opacity), so only the
   indicator appears. Once .itg-dt-ready is added, this stops matching. */
.onb-recruting-live-page #exampleImport_wrapper:not(.itg-dt-ready) {
  opacity: 1;
  visibility: hidden;
}

.onb-recruting-live-page #exampleImport_wrapper:not(.itg-dt-ready) .dt-processing {
  visibility: visible;
}

/* FDCM-3547: cpe-pages/new-inventory-reconcile.php -- the pager sat flush against the
   "Export To" select on both grids (Reconciliation #example, Que For Reconcile #example1).
   !important: style-new.css zeroes .dt-paging margins with !important. */
.cpe-pages-new-inventory-reconcile-page #example_wrapper .dt-paging,
.cpe-pages-new-inventory-reconcile-page #example1_wrapper .dt-paging {
  margin-right: 12px !important;
}

/* FIX [FDCM-3547]: personnel-portal/timesheet-unconfirmed.php - "Enter Correct
   Time or Remove Time Entry Mistake" modals (#dismodal = Add Dispute Entry,
   #cwomodal = Dispute checkbox). Their label/field rows are
   "<div class='gen mb20'>" holding bare ".col-sm-3"/".col-sm-9" divs with no
   ".row" wrapper. Bootstrap 3 floated those columns side by side; Bootstrap 5
   doesn't, so every label and field stacked on its own line (Select office,
   Date, Clock In / Clock Out, mileage, comment, meal breaks).

   Float (not flex) on purpose: show_modal() toggles "#disputofc" with an
   inline "display:block", which would override a "display:flex" row rule.
   A clearfix ::after makes each row contain its floated columns. Don't use
   "overflow:hidden" for this: que-local.css gives ".form-control" a
   "margin-top:-5px", so the inputs stick 5px above the row and it clipped
   their top border. ":has(> col)"
   skips the AJAX-filled rows (#commentlists, #project_login_details). Label
   columns (the ones without a .form-control) get 7px top padding so their text
   lines up with the 38px inputs. Below 768px the columns stack, as BS3's
   col-sm-* did. Scoped to this page's body class: ".gen mb20" and these modal
   IDs are reused by ~20 other timesheet pages that haven't been verified. */
@media (min-width: 768px) {
  .personnel-portal-timesheet-unconfirmed-page :is(#dismodal, #cwomodal) .gen.mb20:has(> [class*="col-sm-"])::after {
    content: "";
    display: table;
    clear: both;
  }
  .personnel-portal-timesheet-unconfirmed-page :is(#dismodal, #cwomodal) .gen.mb20 > [class*="col-sm-"] {
    float: left;
    box-sizing: border-box;
    padding-right: 15px;
  }
  .personnel-portal-timesheet-unconfirmed-page :is(#dismodal, #cwomodal) .gen.mb20 > [class*="col-sm-"]:not(:has(.form-control)) {
    padding-top: 7px;
  }
}

/* FIX [FDCM-3547]: personnel-portal/employee-summary.php -- everything
   stacked in one narrow left column.
   The page lays out its grid with Bootstrap 3 style .col-sm-* divs placed
   directly inside .gen / .qc_mainPrat / .gen.mtb10, with no .row wrapper:
   - photo (.col-sm-4) beside the field list (.col-sm-8)
   - each field row's label (.col-sm-5) beside its input (.col-sm-7)
   - PRIMARY POC label (.col-sm-4) / input (.col-sm-5) / Update+Log (.col-sm-3)
   - the main panel (.col-sm-8.offset-sm-2), with the "show tech log" and
     "2FA Settings" buttons flowing to its right
   Bootstrap 5 dropped the default float:left on .col-*, and gutter padding
   only applies to `.row > *`, so each column got its width but sat on its own
   line against the left edge. The fix restores BS3's float and 15px column
   padding. .gen (float:left; width:100%) and .qc_mainPrat (inline-block) already
   contain the floats.
   Scoped to the page's auto-generated body class, because .gen, .qc_mainPrat
   and .lh are reused on dozens of unrelated pages. The 576px breakpoint
   matches where BS5's .col-sm-* widths start, so phones still stack.
   The sitewide ".gen.mtb10 { display:flex; flex-wrap:wrap }" rule (search
   "QC Categories Config") also matched this page's main-panel wrapper and
   forced its .col-sm-8 to 75%. That plus the 16.67% offset left too little
   room, so "show tech log"/"2FA Settings" wrapped to the bottom-left. The flex
   row also ignored the <br> between them. Turning that wrapper back into a
   plain block (same as the :has(#ActionType) fix) lets the panel float again,
   and the buttons sit stacked to its right as on DevOps. */
.personnel-portal-employee-summary-page .Middle > .gen.mtb10 {
  display: block !important;
}
@media (min-width: 576px) {
  .personnel-portal-employee-summary-page .Middle .gen > [class*="col-sm-"],
  .personnel-portal-employee-summary-page .Middle .qc_mainPrat > [class*="col-sm-"] {
    float: left;
    padding-left: 15px;
    padding-right: 15px;
  }
  .personnel-portal-employee-summary-page .Middle .gen > .no-pad {
    padding-left: 0;
    padding-right: 0;
  }
}

/* FDCM-3547: textareas in modal DataTables grids sat above their row.
   que-local.css ".form-control { margin-top: -5px }" also hits .form-control
   textareas. style-new.css protects table-cell inputs from it
   ("td input:not([type=radio]) { margin-top: 1px !important }") but has no
   textarea equivalent, so e.g. contractor_recruiting.php View Log
   (#searchlog_modal) "Comment" textarea sat 3px above the row's inputs and
   overlapped the header/row border. Same 1px as the inputs; only inside a
   DataTable within a modal. :where() keeps the specificity at (0,1,2), so
   page-specific textarea rules still win. */
:where(.modal) :where(.dt-container, .dataTables_wrapper) td textarea.form-control {
  margin-top: 1px;
}

/* FDCM-3547: inventory-settings/vendor-info.php Vendor List -- row checkbox
   overlapped the Vendor ID box. style-new.css ".assets_tabil td { padding: 0 }"
   applies because the table has no Bootstrap .table class; on ATS, DataTables 1's
   own stylesheet gave these cells 8px 10px, which DataTables 3 doesn't. Without it,
   the Vendor ID input starts at the cell edge, under the checkbox (which
   ".assets_tabil .control.control--checkbox { left: 36% }" pushes right). Restore
   the ATS cell padding: the box ends 3px before Vendor ID, centred in the row. */
.inventory-settings-vendor-info-page #exampleVendor tbody td {
  padding: 8px 10px;
}

/* FIX [FDCM-3547]: personnel-portal/employee-summary.php -- everything
   stacked in one narrow left column.
   The page lays out its grid with Bootstrap 3 style .col-sm-* divs placed
   directly inside .gen / .qc_mainPrat / .gen.mtb10, with no .row wrapper:
   - photo (.col-sm-4) beside the field list (.col-sm-8)
   - each field row's label (.col-sm-5) beside its input (.col-sm-7)
   - PRIMARY POC label (.col-sm-4) / input (.col-sm-5) / Update+Log (.col-sm-3)
   - the main panel (.col-sm-8.offset-sm-2), with the "show tech log" and
     "2FA Settings" buttons flowing to its right
   Bootstrap 5 dropped the default float:left on .col-*, and gutter padding
   only applies to `.row > *`, so each column got its width but sat on its own
   line against the left edge. The fix restores BS3's float and 15px column
   padding. .gen (float:left; width:100%) and .qc_mainPrat (inline-block) already
   contain the floats.
   Scoped to the page's auto-generated body class, because .gen, .qc_mainPrat
   and .lh are reused on dozens of unrelated pages. The 576px breakpoint
   matches where BS5's .col-sm-* widths start, so phones still stack.
   The sitewide ".gen.mtb10 { display:flex; flex-wrap:wrap }" rule (search
   "QC Categories Config") also matched this page's main-panel wrapper and
   forced its .col-sm-8 to 75%. That plus the 16.67% offset left too little
   room, so "show tech log"/"2FA Settings" wrapped to the bottom-left. The flex
   row also ignored the <br> between them. Turning that wrapper back into a
   plain block (same as the :has(#ActionType) fix) lets the panel float again,
   and the buttons sit stacked to its right as on DevOps. */
.personnel-portal-employee-summary-page .Middle > .gen.mtb10 {
  display: block !important;
}
@media (min-width: 576px) {
  .personnel-portal-employee-summary-page .Middle .gen > [class*="col-sm-"],
  .personnel-portal-employee-summary-page .Middle .qc_mainPrat > [class*="col-sm-"] {
    float: left;
    padding-left: 15px;
    padding-right: 15px;
  }
  .personnel-portal-employee-summary-page .Middle .gen > .no-pad {
    padding-left: 0;
    padding-right: 0;
  }
}

/* FDCM-3547: cpe-pages/correct-cpe-location.php "CPE Location Que" -- centre the cells
   under their centred headers, except Count (column 2, a textbox). !important: the
   unscoped "#example tbody td { text-align: left !important }" above (written for a
   checkbox grid) also reaches this page's #example. */
.cpe-pages-correct-cpe-location-page #example tbody td:not(:nth-child(2)) {
  text-align: center !important;
}

/* FDCM-3547: CPE que grids (return-cpe.php, cpe-checkin.php, return-cpe-import.php
   "Check in Que"; correct-cpe-type.php "CPE Type Queue") -- centre the plain-text
   cells (Count, Serial, Status ...) and the inline delete icon under their centred
   headers, as on correct-cpe-location.php. The dropdowns and the Count textbox are
   display:block form-controls, so text-align does not move them. correct-cpe-type
   needs !important to beat the unscoped "#example tbody td { text-align: left
   !important }" above. */
.cpe-pages-return-cpe-page #example5 tbody td,
.cpe-pages-cpe-checkin-page #example5 tbody td,
.cpe-pages-return-cpe-import-page #example5 tbody td {
  text-align: center;
}
.cpe-pages-correct-cpe-type-page #example tbody td {
  text-align: center !important;
}

/* FDCM-3547: cpe-pages/lost-cpe-import.php. BS5 has no ".input-group-btn" rule, so
   the upload block sat at the left of the flex ".input-group"; centre it (same fix
   as .import-users-page above). */
.cpe-pages-lost-cpe-import-page .bottom_div .input-group .input-group-btn {
  margin: 0 auto;
}

/* style-new.css lifts every "div.dt-buttons" by -36px (sized for the DT1 toolbar);
   on lost-cpe-import that pushed Excel/PDF Export above the grid, where they were
   clipped. */
.cpe-pages-lost-cpe-import-page #exampleImport_wrapper div.dt-buttons {
  margin-top: 0 !important;
}

/* Centre "Showing x to y of z entries" and the pager under the import log grid. */
.cpe-pages-lost-cpe-import-page #exampleImport_wrapper div.dt-info,
.cpe-pages-lost-cpe-import-page #exampleImport_wrapper div.dt-paging {
  display: flex !important;
  justify-content: center;
  width: 100% !important;
  float: none !important;
}

/* The "View" details modal grid (#example, loaded from
   ajax/lost-cpe-import-details.php) was left-aligned by the unscoped
   "#example tbody td { text-align: left !important }" above. */
.cpe-pages-lost-cpe-import-page #details_modal #example tbody td {
  text-align: center !important;
}

/* FDCM-3547: grid loader for serial scans on the CPE que pages (cpeGridLoader() in
   return-cpe.php, cpe-checkin.php, return-cpe-import.php and correct-cpe-type.php).
   It reuses footer.php's .erp-export-spinner, recoloured for a light overlay. */
.cpe-pages-return-cpe-page #example5_wrapper,
.cpe-pages-cpe-checkin-page #example5_wrapper,
.cpe-pages-return-cpe-import-page #example5_wrapper,
.cpe-pages-correct-cpe-type-page #example_wrapper {
  position: relative;
}
.cpe-grid-loader {
  position: absolute;
  inset: 0;
  z-index: 5;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 10px;
  min-height: 120px;
  background: rgba(255, 255, 255, 0.88);
  color: #2196f3;
  font-size: 14px;
}
.cpe-grid-loader .erp-export-spinner {
  width: 40px;
  height: 40px;
  border-color: rgba(33, 150, 243, 0.25);
  border-top-color: #2196f3;
}

/* ---- office/work-area.php (FDCM-3547) ---- */
/* FDCM-3547: payroll.css `.control--checkbox { left: 30% }` plus the hidden checkbox
   <input> stretching to the cell width pushed past the cell edge, so the Manage
   grid's .dt-table-scroll showed horizontal and vertical scrollbars. */
.office-work-area-page #example5 tbody .control--checkbox {
  display: inline-block;
  left: auto;
  margin: 0;
  padding-left: 0;
  width: 20px;
  height: 20px;
  vertical-align: middle;
}
.office-work-area-page #example5 tbody .control--checkbox input {
  left: 0;
  top: 0;
  width: 20px;
  height: 20px;
}
.office-work-area-page #example5 tbody .control--checkbox .control__indicator {
  top: 0;
}
/* FDCM-3547: space between the Search box and the pager in the modal grids. */
.office-work-area-page #logtable_wrapper .dt-search,
.office-work-area-page #example5_wrapper .dt-search {
  margin-right: 12px !important;
}
/* FDCM-3547: BS5 .container has no clearfix, so it collapsed around the floated
   .Middle and its 70px margin-bottom (space under Save/Cancel) was lost. */
.office-work-area-page .container:has(> .Middle.bonus-category) {
  display: flow-root;
}
/* FDCM-3547: sitewide `#example tbody td { text-align: left !important }` left-aligned
   the "view log" links under the centred Log header. */
.office-work-area-page #example tbody td:last-child {
  text-align: center !important;
}

/* ---- office/work-area.php (FDCM-3547) ---- */
/* FDCM-3547: payroll.css `.control--checkbox { left: 30% }` plus the hidden checkbox
   <input> stretching to the cell width pushed past the cell edge, so the Manage
   grid's .dt-table-scroll showed horizontal and vertical scrollbars. */
.office-work-area-page #example5 tbody .control--checkbox {
  display: inline-block;
  left: auto;
  margin: 0;
  padding-left: 0;
  width: 20px;
  height: 20px;
  vertical-align: middle;
}
.office-work-area-page #example5 tbody .control--checkbox input {
  left: 0;
  top: 0;
  width: 20px;
  height: 20px;
}
.office-work-area-page #example5 tbody .control--checkbox .control__indicator {
  top: 0;
}
/* FDCM-3547: space between the Search box and the pager in the modal grids. */
.office-work-area-page #logtable_wrapper .dt-search,
.office-work-area-page #example5_wrapper .dt-search {
  margin-right: 12px !important;
}
/* FDCM-3547: BS5 .container has no clearfix, so it collapsed around the floated
   .Middle and its 70px margin-bottom (space under Save/Cancel) was lost. */
.office-work-area-page .container:has(> .Middle.bonus-category) {
  display: flow-root;
}
/* FDCM-3547: sitewide `#example tbody td { text-align: left !important }` left-aligned
   the "view log" links under the centred Log header. */
.office-work-area-page #example tbody td:last-child {
  text-align: center !important;
}

/* Keep this four-column grid within its card instead of scrolling sideways. */
.inventory-settings-email-notification-page .assets_tabil.email-notification-grid,
.inventory-settings-email-notification-page .email-notification-grid .dt-table-scroll {
  overflow-x: visible !important;
  overflow-y: visible !important;
}
.inventory-settings-email-notification-page .email-notification-grid #example {
  width: 100% !important;
  min-width: 0 !important;
  table-layout: fixed;
}
.inventory-settings-email-notification-page .email-notification-grid #example th,
.inventory-settings-email-notification-page .email-notification-grid #example td {
  min-width: 0;
  white-space: normal !important;
  overflow-wrap: anywhere;
}
.inventory-settings-email-notification-page .email-notification-grid #example input.form-control {
  width: 100% !important;
  min-width: 0 !important;
  max-width: 100%;
  box-sizing: border-box;
}
.inventory-settings-email-notification-page .email-notification-grid #example td.pos-cen {
  text-align: center !important;
}
.inventory-settings-email-notification-page .email-notification-grid #example .control {
  display: inline-block;
  left: auto !important;
  top: 0 !important;
  width: 20px;
  height: 20px;
  padding: 0;
  margin: 0;
  vertical-align: middle;
}
.inventory-settings-email-notification-page .email-notification-grid #example .control__indicator {
  left: 0; top: 0;
}
.inventory-settings-email-notification-page .email-notification-grid #example .checktxt {
  display: none;
}
.inventory-settings-email-notification-page .email-notification-grid #example_wrapper .records {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: center;
  gap: 0.75rem;
}

.onb-recruting-live-page #responseDiv .col-md-6 .form-group div.btn-group {
  width: 215px !important;
}
.onb-recruting-live-page #responseDiv .col-md-6 .form-group .btn-group .multiselect-container.dropdown-menu {
  overflow-x: visible !important;
}
/* FIX: report/kpi-report.php - Recurrence Pattern block.
   report-common.css sets ".report-form label { display:block }", and BS5 has no
   .custom-control/.custom-radio styles, so every radio sat on its own line above its
   label. BS5 also floats <legend> at 1.5rem, and the col-md-3/col-md-9 wrappers have no
   .row, so they lose their gutters. Scoped to the page body class because
   .report-form/.custom-radio are shared with other report pages. */
.report-kpi-report-page .report-form fieldset {
  margin: 0 12px;
  padding: 0 10px 10px !important;
  border: 1px solid #c8c8c8 !important;
  border-top: 0 !important;
}
.report-kpi-report-page .report-form fieldset > legend {
  float: none;
  width: auto;
  font-size: 20px;
  font-weight: 300;
  line-height: 1.4;
  margin: 0 -11px 15px;
  padding: 0;
}
.report-kpi-report-page .report-form fieldset > .col-md-3,
.report-kpi-report-page .report-form fieldset > .col-md-9 {
  width: 100%;
  padding: 0 5px;
}
.report-kpi-report-page .report-form fieldset > .col-md-3 {
  margin-bottom: 10px;
}
.report-kpi-report-page .report-form .custom-radio {
  display: flex;
  align-items: center;
  gap: 4px;
  margin-bottom: 6px;
}
.report-kpi-report-page .report-form .custom-radio > label,
.report-kpi-report-page .report-form .form-check-inline > label {
  display: inline-block;
  margin-bottom: 0;
}
.report-kpi-report-page .report-form .custom-radio > input[type=radio] {
  margin: 0;
}
.report-kpi-report-page .report-form .form-check-inline {
  display: block;
  padding-left: 0;
}
.report-kpi-report-page .report-form .form-check-inline .form-check-input {
  float: none;
  margin: 0 3px 0 0;
}
