/* ==========================================================================
   Modern Refresh — visual overlay on top of the Angle/Bootstrap 3 theme.
   Loaded last in SimplyMasterNew.Master so it wins on normal specificity.
   No markup/JS changes required; delete the <link> to revert instantly.
   ========================================================================== */

:root {
    --mr-accent: #4f46e5;
    --mr-accent-dark: #4338ca;
    --mr-accent-soft: #eef2ff;
    --mr-bg: #f4f6f9;
    --mr-surface: #ffffff;
    --mr-text: #2b2f38;
    --mr-text-muted: #6b7280;
    --mr-border: #e5e7eb;
    --mr-radius: 8px;
    --mr-radius-sm: 6px;
    --mr-shadow: 0 2px 10px rgba(17, 24, 39, 0.06);
    --mr-shadow-lg: 0 8px 24px rgba(17, 24, 39, 0.10);
    --mr-sidebar-bg: #1f2430;
    --mr-sidebar-text: #b7bdcc;
    --mr-sidebar-active: #2c3345;
    --mr-font: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
}

/* ---- Base / typography ---- */
html, body {
    background-color: var(--mr-bg) !important;
    color: var(--mr-text);
    font-family: var(--mr-font);
}

body, .form-control, .btn, .dropdown-menu, .modal-content, table {
    font-family: var(--mr-font);
}

/* ---- Popup pages loaded inside an iframe within a parent modal ----
   (FindSurveyMultipleEmployee.aspx, GetMultipleEmail.aspx — marked with
   class="popup-embed" on <body>.) Without this, the standard grey page
   background above shows up as a redundant middle layer: white (parent
   modal) -> grey (this page's own body) -> white (its .card) — a
   pointless triple-nested box look, since the parent modal already
   provides the "page" framing. Blends this page's body into the parent
   instead. */
html:has(body.popup-embed) {
    background-color: var(--mr-surface) !important;
}
.popup-embed {
    background-color: var(--mr-surface) !important;
    /* FindSurveyMultipleEmployee.aspx sets style="width:95%" inline on
       <body> — since html (100% wide) stayed the grey page background,
       that leftover 5% strip on the right showed through as a distinct
       grey column once body itself went white. !important beats the
       inline style here since inline styles only win over non-important
       stylesheet rules. auto (not 100%) deliberately — 100% plus a
       vertical scrollbar's own gutter width is a classic way to push
       content a few px past the viewport and trigger an unwanted
       horizontal scrollbar, which is exactly what showed up. */
    width: auto !important;
}
.popup-embed .wrapper > .card {
    box-shadow: none;
    border: none;
}
h1, h2, h3, h4, h5, h6 {
    font-family: var(--mr-font);
    font-weight: 600;
    color: var(--mr-text);
}

a {
    color: var(--mr-accent);
}
a:hover, a:focus {
    color: var(--mr-accent-dark);
}

/* ---- Top navbar ---- */
.topnavbar-wrapper,
.topnavbar {
    background-color: var(--mr-surface) !important;
    background-image: none !important;
    box-shadow: var(--mr-shadow);
    border-bottom: 1px solid var(--mr-border);
}
.topnavbar .navbar-nav > li > a {
    color: var(--mr-text) !important;
}
.topnavbar .navbar-nav > li > a:hover,
.topnavbar .navbar-nav > li > a:focus,
.topnavbar .navbar-nav > .open > a {
    background-color: var(--mr-accent-soft) !important;
    color: var(--mr-accent-dark) !important;
    border-radius: var(--mr-radius-sm);
}
.topnavbar .badge.bg-red {
    background-color: var(--mr-accent) !important;
}

/* ---- Sidebar ---- */
.wrapper > .aside,
.aside-inner,
.sidebar {
    background-color: var(--mr-sidebar-bg) !important;
    background-image: none !important;
}
.sidebar > .nav > li > a,
.sidebar li > a {
    color: var(--mr-sidebar-text) !important;
    border-radius: var(--mr-radius-sm);
}
.sidebar > .nav > li > a:hover,
.sidebar > .nav > li > a:focus,
.sidebar > .nav > li.active > a,
.sidebar > .nav > li.active > .nav-item {
    background-color: var(--mr-sidebar-active) !important;
    color: #fff !important;
    box-shadow: inset 3px 0 0 var(--mr-accent);
}
/* .sidebar-subnav (the inline expanded submenu shown for the active
   section — NOT the floating hover-preview flyout, .nav-floating, which
   stays as its own white popup like the rest of the dropdowns) still had
   layout.css's original white background (#fff) while the .sidebar li > a
   rule above was already forcing its text to the dark-theme light-grey
   color — white bg + light-grey text read as washed-out/illegible. */
.sidebar-subnav:not(.nav-floating) {
    background-color: #171b24 !important;
}
.sidebar-subnav:not(.nav-floating) > li > a:hover,
.sidebar-subnav:not(.nav-floating) > li > a:focus,
.sidebar-subnav:not(.nav-floating) > li.active > a {
    background-color: var(--mr-sidebar-active) !important;
    color: #fff !important;
    border-radius: var(--mr-radius-sm);
}
.sidebar-subnav:not(.nav-floating) > li.active > a:after {
    border-color: var(--mr-accent) !important;
    background-color: var(--mr-accent) !important;
}
.sidebar > .nav > .nav-heading {
    color: #7b8299 !important;
}

/* ---- Buttons ---- */
.btn {
    border-radius: var(--mr-radius-sm);
    box-shadow: none !important;
    border-width: 1px;
    padding: 8px 18px;
    font-weight: 600;
    letter-spacing: .01em;
    transition: transform .12s ease, box-shadow .12s ease, background-color .12s ease;
}
.btn:hover {
    transform: translateY(-1px);
    box-shadow: var(--mr-shadow) !important;
}
.btn:active {
    transform: translateY(0);
}
.btn-primary,
.btn-primary:active,
.btn-primary:focus {
    background-color: var(--mr-accent) !important;
    border-color: var(--mr-accent) !important;
}
.btn-primary:hover {
    background-color: var(--mr-accent-dark) !important;
    border-color: var(--mr-accent-dark) !important;
}
.btn-info, .btn-info:active, .btn-info:focus {
    background-color: #0ea5e9 !important;
    border-color: #0ea5e9 !important;
}
.btn-danger, .btn-danger:active, .btn-danger:focus {
    background-color: #d64545 !important;
    border-color: #d64545 !important;
}
.btn-success, .btn-success:active, .btn-success:focus {
    background-color: #1f9d55 !important;
    border-color: #1f9d55 !important;
}
.btn-warning, .btn-warning:active, .btn-warning:focus {
    background-color: #f59e0b !important;
    border-color: #f59e0b !important;
}
.btn-default {
    background-color: var(--mr-surface) !important;
    border-color: var(--mr-border) !important;
    color: var(--mr-text) !important;
}

/* The template's own bg-* utility classes are used as button colors
   sitewide (e.g. CssClass="btn bg-black waves-effect") far more often than
   Bootstrap's btn-primary/btn-danger/etc above, so they need their own
   softened palette rather than the original raw #000/#F44336/#4CAF50. */
/* bg-black is used sitewide for primary/submit-style actions (Search,
   Save, etc.) — plain black doesn't read as "primary action", so it gets
   the same indigo accent used for primary actions elsewhere instead. */
.btn.bg-black {
    background-color: var(--mr-accent) !important;
    border-color: var(--mr-accent) !important;
}
.btn.bg-black:hover {
    background-color: var(--mr-accent-dark) !important;
}
.btn.bg-red {
    background-color: #d64545 !important;
    border-color: #d64545 !important;
}
.btn.bg-red:hover {
    background-color: #bd3a3a !important;
}
.btn.bg-green {
    background-color: #1f9d55 !important;
    border-color: #1f9d55 !important;
}
.btn.bg-green:hover {
    background-color: #188245 !important;
}
/* bg-blue deliberately does NOT reuse --mr-accent — that indigo is meant
   to stay vivid for links/focus rings/the current-page pill, so a generic
   "blue" utility button gets its own separate, deeper shade instead of
   competing with it. */
.btn.bg-blue {
    background-color: #2f6fb0 !important;
    border-color: #2f6fb0 !important;
}
.btn.bg-blue:hover {
    background-color: #275c93 !important;
}
.btn.bg-cyan {
    background-color: #0d84ba !important;
    border-color: #0d84ba !important;
}
.btn.bg-cyan:hover {
    background-color: #0b6c97 !important;
}

/* ---- Forms ---- */
.form-control {
    border: 1px solid var(--mr-border);
    border-radius: var(--mr-radius-sm);
    box-shadow: none;
    background-color: var(--mr-surface);
}
.form-control:focus {
    border-color: var(--mr-accent);
    box-shadow: 0 0 0 3px var(--mr-accent-soft);
}

/* ---- Tables / GridView output ----
   GridView renders header cells as plain <th> with NO <thead> wrapper, so
   they fall into the browser's implicit <tbody> alongside data rows. The
   legacy `.table th { background:#4CAF50 }` at style.css:14883 is an
   unscoped rule that matches regardless, and its `color:#eee !important`
   means an !important is required here too to reliably win. */
.table th {
    background-color: var(--mr-accent-soft) !important;
    color: var(--mr-accent-dark) !important;
    font-weight: 700 !important;
    font-size: 13px;
    text-transform: uppercase;
    letter-spacing: .03em;
    padding: 12px;
    border-bottom: 2px solid var(--mr-accent);
    /* <th> centers by native browser default, <td> left-aligns by
       default — neither Bootstrap nor this file ever explicitly set
       either, so headers and data drifted out of alignment with each
       other despite no CSS actually saying "center". */
    text-align: left;
}
/* Sticky header attempt reverted — position:sticky on bare <th> cells (no
   real <thead>, since GridView never emits one) broke row order on at
   least one page (header rendered below the first data row instead of
   above it). Not safe to apply generically across every GridView's
   markup without a more targeted, per-page/JS-driven approach. */
/* Sortable GridView columns (AllowSorting + SortExpression) render their
   header text as an <a>; style.css:14891 sets that to white (`.table th a`),
   which is invisible against our light header background. */
.table th a {
    color: var(--mr-accent-dark) !important;
    font-weight: 700 !important;
    text-decoration: none;
}
.table > tbody > tr > td,
.table td {
    border-top: 1px solid var(--mr-border) !important;
    padding: 12px;
    vertical-align: middle;
    color: var(--mr-text);
    font-size: 13px;
}
/* GridView's default pager: a class-less <table> nested inside the last
   row's <td>, other pages as <a href="javascript:__doPostBack(...)">,
   current page as plain unlinked text in its own <td>. Reset what the
   generic ".table td" rule above put on these nested cells first, since it
   matches them too (descendant selector), then pill-style them.

   Deliberately :has()-free (two prior attempts using it, incl. :not(:has())
   and a plain positive :has(a), both collapsed cells to a rendering
   glitch in this browser). Every pager <td> gets the identical pill box
   unconditionally — no conditional selector needed — and only the text
   color distinguishes current page (bold accent) from clickable pages
   (muted, darkens on hover). */
.table td table {
    border-collapse: separate !important;
    border-spacing: 6px 0;
    margin: 4px auto 0;
}
/* Every cell defaults to the filled "current page" look. Cells that DO
   have an <a> (i.e. every page except the current one) get their own
   opaque pill on top, sized with a negative margin equal to the td's own
   padding so it fully overlays/hides the accent fill underneath — the
   presence of the <a> itself is what distinguishes them, no :has()
   needed. */
.table td table td {
    border-top: none !important;
    padding: 6px 12px !important;
    min-width: 30px;
    border-radius: var(--mr-radius-sm);
    text-align: center;
    font-weight: 700;
    font-size: 13px;
}
/* .table tbody tr:nth-child(even) td (zebra stripe) turned out to have the
   SAME specificity as an equal-specificity attempt here, and it sits later
   in this file, so it kept winning the !important tie on source order.
   Going one type-selector higher (adding tbody) so this unambiguously
   outranks it regardless of where either rule sits in the file. */
.table.table-bordered tbody td table td {
    background-color: var(--mr-accent) !important;
    color: #fff !important;
    cursor: default;
    -webkit-user-select: none;
    user-select: none;
}
/* Current-page number renders as <span>N</span> (confirmed via inspector),
   not bare text. style.css:14904 has `.table tr:hover td span {
   background-color: #F1F1F1 }` — targets the SPAN directly, so on hover it
   painted its own light-grey background over the td's indigo fill,
   leaving white text invisible against it. Override with `inherit` so it
   picks up whatever the td's actual background is instead of a hardcoded
   color, plus force color through the same way. */
.table.table-bordered tbody td table td span {
    background-color: inherit !important;
    color: inherit !important;
    cursor: default;
    user-select: none;
}
.table td table td a {
    display: inline-block;
    margin: -6px -12px;
    padding: 6px 12px;
    min-width: 30px;
    border-radius: var(--mr-radius-sm);
    background-color: var(--mr-surface);
    border: 1px solid #c7ccd6;
    box-shadow: var(--mr-shadow);
    color: var(--mr-text-muted);
    text-decoration: none;
    font-weight: 600;
}
.table td table td a:hover {
    background-color: var(--mr-accent-soft);
    color: var(--mr-accent-dark);
    border-color: var(--mr-accent);
}
/* Bootstrap's table-bordered boxes every cell; keep only horizontal rules */
.table-bordered th,
.table-bordered td {
    border-left: none !important;
    border-right: none !important;
}
.table-bordered {
    border: none !important;
}
.table tbody tr:nth-child(even) td {
    background-color: #f3f4f8 !important;
}
.table tbody tr:hover td,
.table-hover > tbody > tr:hover {
    background-color: var(--mr-accent-soft) !important;
}
/* Note: deliberately NOT adding border-radius/overflow:hidden on
   .table-responsive — Bootstrap relies on that element's overflow-x:auto
   for horizontal scrolling on narrow screens, and overflow is a shorthand
   that would silently kill it. */
.table-responsive .table {
    margin-bottom: 0;
    border: 1px solid var(--mr-border);
}
/* GridView results tables commonly sit directly after a Search/Reset
   button row with zero gap in the markup (e.g. PopUps/
   FindSurveyMultipleEmployee.aspx) — give the results table breathing
   room from whatever precedes it. */
.table-responsive {
    margin-top: 20px;
}

/* ---- Cards / panels ---- */
.panel,
.card {
    background-color: var(--mr-surface);
    border: 1px solid var(--mr-border);
    border-radius: var(--mr-radius);
    box-shadow: var(--mr-shadow);
}
.panel-heading {
    border-radius: var(--mr-radius) var(--mr-radius) 0 0 !important;
    background-color: var(--mr-surface);
    border-bottom: 1px solid var(--mr-border);
}
.card > .card-header,
.card .form-horizontal > .card-header {
    padding: 20px 24px;
}
/* .form-horizontal (unlike .body) is consistently present as the direct
   child of .card across every page convention seen so far — some pages
   nest an extra .body div inside it (.card > .form-horizontal > .body),
   others put form-groups directly inside .form-horizontal with no .body
   at all (e.g. PopUps/FindSurveyMultipleEmployee.aspx). Padding lived on
   .body only, so pages without it had zero card padding — inputs sat
   flush against the card's own edge. Moved here so it applies either
   way; .body's own padding zeroed out to avoid doubling it when both
   exist. */
.card .form-horizontal {
    padding: 20px 24px;
}
.card .body {
    padding: 0;
}
.card .card-header {
    box-shadow: none;
    overflow: hidden; /* clearfix: .card-header wraps a floated .form-group */
}
/* Popup "Add"-style action rows (FindSurveyMultipleEmployee.aspx,
   GetMultipleEmail.aspx) offset the button via an empty col-lg-4 +
   col-lg-6 content column — centers within that 6-col box, not the full
   row, so a single button reads as off-center; also had zero bottom
   margin, sitting flush against the card's own bottom edge. [id$=...]
   matches by ID suffix since ASP.NET prefixes server IDs at runtime. */
[id$="divAddBtn"] {
    text-align: center;
    margin-bottom: 24px;
}
[id$="divAddBtn"] > div {
    float: none;
    display: inline-block;
    width: auto;
}
/* .card-header's actual boundary is inconsistent across pages (sometimes
   just the "I Want to" toggle, sometimes the whole form+table), so anchor
   the divider to the toggle row itself via its RadioButtonList (id="rdbList"
   everywhere) rather than trusting .card-header's border position. Falls
   back to no divider (not a broken one) in browsers without :has(). */
.card .body .form-group:has(.rbl-Iwant) {
    padding-bottom: 16px;
    margin-bottom: 20px;
    border-bottom: 1px solid var(--mr-border);
    overflow: hidden;
}
/* layout.css:129 sets .content-wrapper { padding: 1px } — the theme
   expected pages to wrap content in .container/.container-fluid to get
   real gutters, but these pages just use .row > .col-md-12 directly, so
   there was effectively no left/right margin between the card and the
   sidebar/viewport edge. Real padding here is what makes the card's
   border/shadow/radius actually visible against the page background. */
.content-wrapper {
    background-color: var(--mr-bg);
    padding: 20px 24px !important;
}
.page-header {
    border: none;
    margin: 4px 0 20px;
    padding: 0;
}
.page-header h4 {
    font-weight: 700;
    font-size: 20px;
    margin: 0;
}

/* ---- Radios / checkboxes ----
   assets/css/style.css imports assets/css/materialize.css (see @import at
   its line 2), which hides the real <input> off-screen (left:-9999px) and
   draws the visible dot/box on the adjacent <label>'s ::before/::after —
   hardcoded to Materialize's red (#f44336) at materialize.css:93-101 and
   :231-239. Styling the <input> itself (e.g. accent-color, appearance:none)
   has no visible effect since the input is invisible; these selectors
   must match Materialize's own label-based ones to win. */
[type="radio"]:checked + label:after,
[type="radio"].with-gap:checked + label:after {
    background-color: var(--mr-accent) !important;
}
[type="radio"]:checked + label:before,
[type="radio"]:checked + label:after,
[type="radio"].with-gap:checked + label:before,
[type="radio"].with-gap:checked + label:after {
    border-color: var(--mr-accent) !important;
}
[type="checkbox"]:checked + label:before {
    border-right-color: var(--mr-accent) !important;
    border-bottom-color: var(--mr-accent) !important;
}
[type="checkbox"].filled-in:checked + label:after {
    background-color: var(--mr-accent) !important;
    border-color: var(--mr-accent) !important;
}
.rbl-Iwant td {
    padding-right: 20px;
}
.control-label {
    color: var(--mr-text);
    padding-top: 7px;
}
/* Descenders (g, y, p) were getting clipped on some plain <label> text —
   Bootstrap's default line-height ran tight against our font stack. */
label {
    line-height: 1.5;
}

/* ---- Dropdowns / modals ---- */
.dropdown-menu {
    border: 1px solid var(--mr-border);
    border-radius: var(--mr-radius);
    box-shadow: var(--mr-shadow-lg);
}
.modal-content {
    border: none;
    border-radius: var(--mr-radius);
    box-shadow: var(--mr-shadow-lg);
}
.modal-header.bg-red {
    background-color: var(--mr-accent) !important;
}
/* Generic, unclassed .modal-header (Bootstrap's bare default — no bg-*
   class) reads as a blank white bar on a white body ("all white board").
   Colored by default now, matching the .card-header treatment elsewhere,
   EXCEPT the two confirmation-dialog types (.modal-col-green/-red) which
   were deliberately redesigned earlier to keep a white header + a
   colored top accent bar instead — excluded below. */
.modal-header {
    background-color: var(--mr-accent);
    border-bottom: none;
    border-radius: var(--mr-radius) var(--mr-radius) 0 0;
    padding: 16px 20px;
}
/* Not every modal-header wraps its title in <h4 class="modal-title"> —
   some (e.g. UC_Celebration.ascx's #myModallg) put the label directly
   inside .modal-header with no wrapper at all, which the .modal-title
   selector alone missed, leaving it at some other muted default color.
   Turned out that default IS a real, specific rule — style.css:7461
   `.modal .modal-content .modal-header { color: #707780; }` — three
   classes of specificity, beating my plain `.modal-header`. Matching
   that specificity plus !important here since we've been burned by
   close specificity calls before. */
.modal .modal-content .modal-header,
.modal .modal-content .modal-header .modal-title,
.modal .modal-content .modal-header .modal-title * {
    color: #fff !important;
}
.modal-col-green .modal-header,
.modal-col-red .modal-header {
    background-color: transparent;
    border-radius: 0;
    padding: 15px;
}
.modal .modal-content.modal-col-green .modal-header,
.modal .modal-content.modal-col-green .modal-header .modal-title,
.modal .modal-content.modal-col-green .modal-header .modal-title *,
.modal .modal-content.modal-col-red .modal-header,
.modal .modal-content.modal-col-red .modal-header .modal-title,
.modal .modal-content.modal-col-red .modal-header .modal-title * {
    color: var(--mr-text) !important;
}
/* Bootstrap's default .close is dark grey — invisible on the now-colored
   default header, so white-by-default here, with the two white-header
   confirmation-dialog types flipped back to dark. */
.modal-header .close {
    color: #fff;
    opacity: 0.85;
    text-shadow: none;
    font-size: 24px;
    font-weight: 400;
    margin-top: -4px;
}
.modal-header .close:hover {
    color: #fff;
    opacity: 1;
}
.modal-col-green .modal-header .close,
.modal-col-red .modal-header .close {
    color: var(--mr-text-muted);
    opacity: 0.6;
}
.modal-col-green .modal-header .close:hover,
.modal-col-red .modal-header .close:hover {
    color: var(--mr-text);
    opacity: 1;
}

/* ---- Badges / alerts ---- */
.badge.bg-red {
    background-color: var(--mr-accent) !important;
}
.alert {
    border-radius: var(--mr-radius-sm);
    border: 1px solid transparent;
}

/* ---- Loader ---- */
.sk-wave .sk-rect.bg-red {
    background-color: var(--mr-accent) !important;
}

/* ---- Scrollbar (WebKit) ---- */
::-webkit-scrollbar {
    width: 8px;
    height: 8px;
}
::-webkit-scrollbar-thumb {
    background-color: #c7cbd4;
    border-radius: 8px;
}
::-webkit-scrollbar-track {
    background: transparent;
}


/* ---- Card headers (dashboard widgets, popups, etc.) ----
   .card-header is paired with all sorts of bg-* colors sitewide (bg-black,
   bg-red, bg-grey, bg-white, bg-blue, bg-light-blue, bg-green — 53+ uses
   across the app). The class itself conveniently splits by context: every
   dashboard widget (Leadership, Celebration, Notice Board, Attendance,
   Picture Gallery) specifically uses bg-black, which reads well as the
   dark sidebar navy. Popup/detail cards (e.g. the birthday-wish list) use
   the other variants (bg-red etc.) — those get the indigo accent instead,
   since navy read as too somber/basically-black at that size there. */
.card-header.bg-black {
    background-color: var(--mr-sidebar-bg) !important;
    border-radius: var(--mr-radius) var(--mr-radius) 0 0 !important;
    padding: 14px 20px !important;
}
/* Compact: these variants are used for repeated per-item cards (e.g. one
   per person in the birthday-wish list), so a much slimmer bar keeps a
   long list scannable instead of every entry costing a full-size header.
   Backed off from the indigo fill to plain white/light + dark text — now
   that the surrounding .modal-header already carries the brand color,
   coloring every single repeated entry too was redundant and, over a
   long list, visually heavy. */
.card-header.bg-red,
.card-header.bg-grey,
.card-header.bg-white,
.card-header.bg-blue,
.card-header.bg-light-blue,
.card-header.bg-green {
    background-color: var(--mr-bg) !important;
    border-bottom: 1px solid var(--mr-border);
    border-radius: var(--mr-radius) var(--mr-radius) 0 0 !important;
    padding: 8px 16px !important;
}
.card-header.bg-red h2,
.card-header.bg-grey h2,
.card-header.bg-white h2,
.card-header.bg-blue h2,
.card-header.bg-light-blue h2,
.card-header.bg-green h2,
.card-header.bg-red h4,
.card-header.bg-grey h4,
.card-header.bg-white h4,
.card-header.bg-blue h4,
.card-header.bg-light-blue h4,
.card-header.bg-green h4 {
    color: var(--mr-text) !important;
    font-size: 14px;
    font-weight: 700;
    margin: 0;
}
.card-header.bg-black h2,
.card-header.bg-black h4 {
    color: #fff !important;
    font-size: 16px;
    font-weight: 700;
    margin: 0;
}
.card-header.bg-black .pull-right,
.card-header.bg-black .pull-right * {
    color: rgba(255, 255, 255, 0.75) !important;
    font-weight: 400;
    font-size: 13px;
}
/* These are now a light background (see above), not dark, so their date/
   pull-right text needs to stay dark-muted instead of white. */
.card-header.bg-red .pull-right,
.card-header.bg-grey .pull-right,
.card-header.bg-white .pull-right,
.card-header.bg-blue .pull-right,
.card-header.bg-light-blue .pull-right,
.card-header.bg-green .pull-right,
.card-header.bg-red .pull-right *,
.card-header.bg-grey .pull-right *,
.card-header.bg-white .pull-right *,
.card-header.bg-blue .pull-right *,
.card-header.bg-light-blue .pull-right *,
.card-header.bg-green .pull-right * {
    color: var(--mr-text-muted) !important;
    font-weight: 600;
    font-size: 13px;
}
/* small/name labels commonly used inside these headers (e.g. the
   birthday-wishes card: name + "small.pull-right" date) */
.card-header.bg-black small {
    color: rgba(255, 255, 255, 0.75) !important;
}
.card-header.bg-red small,
.card-header.bg-grey small,
.card-header.bg-white small,
.card-header.bg-blue small,
.card-header.bg-light-blue small,
.card-header.bg-green small {
    color: var(--mr-text-muted) !important;
}
/* Repeated "Happy Birthday"/etc description text per entry — the outer
   modal title + this compact header already give enough context; the
   date alone is what's actually useful when scanning a long list. Hidden
   rather than removed, since a jQuery handler
   (EmployeeCelebrationWishDetails.aspx:79) still reads its .text() value
   when the wishes are submitted. */
[id$="gvlblwishedEmpDescription"] {
    display: none;
}

/* ---- Celebration widget stat rows ----
   UC_Celebration.ascx hardcodes full-bleed saturated rows via
   bg-deep-orange/bg-red/bg-lime (each paired with a shared ".overflow"
   class, which is what scopes these rules — avoids touching bg-red
   elsewhere, e.g. badges/buttons, which are deliberately left alone).
   Replaced with white tiles + a colored icon badge and left accent bar. */
.card .bg-deep-orange.overflow,
.card .bg-red.overflow,
.card .bg-lime.overflow {
    background-color: var(--mr-surface) !important;
    border: 1px solid var(--mr-border) !important;
    border-radius: var(--mr-radius-sm);
    padding: 10px 8px !important;
}
.card .bg-deep-orange.overflow {
    border-left: 4px solid #f97316 !important;
}
.card .bg-red.overflow {
    border-left: 4px solid var(--mr-accent) !important;
}
.card .bg-lime.overflow {
    border-left: 4px solid #d97706 !important;
}
.card .bg-deep-orange.overflow .avatar,
.card .bg-red.overflow .avatar,
.card .bg-lime.overflow .avatar {
    border-radius: 50%;
    padding: 6px;
    display: inline-block;
}
.card .bg-deep-orange.overflow .avatar {
    background-color: #fff7ed;
}
.card .bg-red.overflow .avatar {
    background-color: var(--mr-accent-soft);
}
.card .bg-lime.overflow .avatar {
    background-color: #fffbeb;
}
.card .bg-deep-orange.overflow *,
.card .bg-red.overflow *,
.card .bg-lime.overflow * {
    color: var(--mr-text) !important;
}
.card .bg-deep-orange.overflow .font-40,
.card .bg-red.overflow .font-40,
.card .bg-lime.overflow .font-40 {
    font-weight: 700;
}
.card .bg-deep-orange.overflow .font-18,
.card .bg-red.overflow .font-18,
.card .bg-lime.overflow .font-18 {
    color: var(--mr-text-muted) !important;
    font-size: 13px;
    font-weight: 600;
}
.card .bg-deep-orange.overflow a,
.card .bg-red.overflow a,
.card .bg-lime.overflow a {
    color: var(--mr-accent) !important;
    text-decoration: none;
    font-weight: 600;
}

/* ---- Confirmation dialogs (#notmyModal pattern: "No record found.",
   validation results, etc.) ----
   .modal-col-green / .modal-col-red (style.css:7702, :7513) fill the
   ENTIRE modal-content with a raw, solid #4CAF50 / a matching red,
   including the footer — used ~2,850 times across the app (the standard
   success/error dialog), so worth doing properly rather than leaving as
   a full-bleed saturated box. Switched to a white dialog with a colored
   top accent bar + colored title/icon instead. */
.modal-content.modal-col-green,
.modal-content.modal-col-red {
    background-color: var(--mr-surface) !important;
    border-top: 5px solid var(--mr-accent);
}
.modal-content.modal-col-green {
    border-top-color: #1f9d55;
}
.modal-content.modal-col-red {
    border-top-color: #d64545;
}
.modal-col-green .modal-body,
.modal-col-red .modal-body {
    color: var(--mr-text) !important;
}
.modal-col-green .modal-title,
.modal-col-red .modal-title {
    color: var(--mr-text) !important;
    font-weight: 700;
}
.modal-col-green .modal-title .glyphicon {
    color: #1f9d55;
}
.modal-col-red .modal-title .glyphicon {
    color: #d64545;
}
.modal-col-green .modal-title .glyphicon,
.modal-col-red .modal-title .glyphicon {
    margin-right: 8px;
    font-size: 18px;
}
.modal-col-green .modal-footer,
.modal-col-red .modal-footer {
    background-color: var(--mr-surface) !important;
    border-top: 1px solid var(--mr-border);
}
.modal-col-green .modal-footer .btn-link,
.modal-col-red .modal-footer .btn-link {
    color: var(--mr-text) !important;
}
/* The "Ok" dismiss button (.btn.btn-default) reads as an inert grey box
   on the now-white dialog — give it the dialog's own accent color so it
   reads as the clear next action instead of a neutral secondary button. */
.modal-col-green .modal-footer .btn {
    background-color: #1f9d55 !important;
    border-color: #1f9d55 !important;
    color: #fff !important;
}
.modal-col-green .modal-footer .btn:hover {
    background-color: #188245 !important;
    border-color: #188245 !important;
}
.modal-col-red .modal-footer .btn {
    background-color: #d64545 !important;
    border-color: #d64545 !important;
    color: #fff !important;
}
.modal-col-red .modal-footer .btn:hover {
    background-color: #bd3a3a !important;
    border-color: #bd3a3a !important;
}

/* ---- Validation error text ----
   ASP.NET validators (RequiredFieldValidator etc.) render as a bare
   <span>, colored via inline style="color:red"/ForeColor="Red" directly
   in ~156 pages' markup — no existing CSS rule at all previously. CSS
   !important genuinely overrides inline (non-!important) styles, so this
   works without touching any of those files. */
.mandatoryflag {
    color: #d64545 !important;
    font-weight: 600;
    font-size: 12px;
}

/* ---- Topnavbar dropdown icon badges ----
   The small colored circles behind each menu icon in the master page's
   Poll/Survey, Query Management, Notifications, and Profile dropdowns
   (icon-circle + bg-red/bg-blue/bg-cyan/bg-green — style.css:1786 gives
   the circle shape, the bg-* class gives the raw saturated color). Scoped
   to .icon-circle specifically so the plain .bg-red/.bg-blue utility
   classes used elsewhere (badges, dashboard tiles, etc.) are untouched. */
.icon-circle.bg-red {
    background-color: #d64545 !important;
}
.icon-circle.bg-blue {
    background-color: var(--mr-accent) !important;
}
.icon-circle.bg-cyan {
    background-color: #0d84ba !important;
}
.icon-circle.bg-green {
    background-color: #1f9d55 !important;
}

/* ---- Global employee-search autocomplete (topnavbar, every page) ----
   jQuery UI's default "Smoothness" theme (jquery-ui.css) is a dated blue
   gradient skin — light-blue gradient background image, bold blue hover
   text, orange active text. Scoped to .ui-autocomplete specifically so
   other jQuery UI widgets elsewhere (datepicker, slider, etc., which use
   the same generic .ui-state-hover/.ui-state-active classes) aren't
   affected by this. */
.ui-autocomplete {
    border: 1px solid var(--mr-border) !important;
    border-radius: var(--mr-radius-sm);
    box-shadow: var(--mr-shadow-lg);
    background: var(--mr-surface) !important;
    padding: 4px 0;
}
.ui-autocomplete .ui-menu-item a {
    color: var(--mr-text) !important;
    padding: 8px 14px;
}
.ui-autocomplete .ui-state-hover,
.ui-autocomplete .ui-state-focus,
.ui-autocomplete .ui-state-active {
    background: var(--mr-accent-soft) !important;
    border: none !important;
    color: var(--mr-accent-dark) !important;
    font-weight: 600;
}
.ui-autocomplete .ui-state-hover a,
.ui-autocomplete .ui-state-focus a,
.ui-autocomplete .ui-state-active a {
    color: var(--mr-accent-dark) !important;
}

/* ---- File upload inputs (92 pages use asp:FileUpload) ----
   Renders as a bare native <input type="file"> with zero CSS previously —
   the OS's raw "Choose File" button sitting next to our now-styled
   inputs/buttons. ::file-selector-button is the standard pseudo-element;
   ::-webkit-file-upload-button is the older Chrome/Edge/Safari-specific
   equivalent, included since this app runs on a range of browser ages.
   Ceiling here is genuinely lower than other controls — a fully custom
   "no file chosen" replacement needs JS/markup, not attempted here. */
input[type="file"] {
    border: 1px solid var(--mr-border);
    border-radius: var(--mr-radius-sm);
    background-color: var(--mr-surface);
    padding: 0;
    font-family: var(--mr-font);
    color: var(--mr-text-muted);
    overflow: hidden; /* clips the button below to this box's own rounded
                          corners instead of the button having its own
                          radius and poking past the input's edge */
}
input[type="file"]::file-selector-button,
input[type="file"]::-webkit-file-upload-button {
    border: none;
    border-radius: 0;
    background-color: var(--mr-accent);
    color: #fff;
    font-family: var(--mr-font);
    font-weight: 600;
    font-size: 13px;
    padding: 9px 16px;
    margin: 0 12px 0 0;
    cursor: pointer;
    transition: background-color .12s ease;
}
input[type="file"]::file-selector-button:hover,
input[type="file"]::-webkit-file-upload-button:hover {
    background-color: var(--mr-accent-dark);
}

/* ---- .form-group clearfix ----
   Plain Bootstrap .form-group (outside .form-horizontal, where Bootstrap
   already adds this itself) has no clearfix by default — just
   margin-bottom. Several pages (e.g. CommonDashBoard.aspx) use
   .form-group as a makeshift row wrapper around floated col-lg-* columns
   with uneven heights (e.g. Notice Board vs. Attendance calendar), which
   without clearing lets a taller sibling displace the next row's
   columns — the "distorted dashboard" symptom. Matches what Bootstrap's
   own .row/.form-horizontal .form-group already do, so it's a no-op
   wherever a .form-group has nothing to clear. */
.form-group:before,
.form-group:after {
    content: " ";
    display: table;
}
.form-group:after {
    clear: both;
}
