/*!
 * bs3.css - Bootstrap 3 -> 4 compatibility shim (Collaterals app)
 * --------------------------------------------------------------------------
 * Load this AFTER assets/bootstrap/4.6.2/css/bootstrap.min.css.
 * It re-implements the Bootstrap 3 classes that BS4 renamed or dropped but
 * that the app's existing markup still relies on, so pages can run on BS4
 * without an immediate full markup rewrite.
 *
 * The col-xs-* GRID shim is intentionally NOT here - it lives in
 * bs3-grid.css, which must load BEFORE bootstrap.min.css (BS3's
 * grid cascade is source-order sensitive). Everything in THIS file is either
 * additive (selectors BS4 doesn't define) or an intentional override of BS4,
 * so it must load AFTER bootstrap.min.css.
 *
 * RETIRE these rules incrementally as markup is migrated to native BS4
 * (pull-* -> float-*, panel -> card, well/thumbnail removed,
 *  btn-default -> btn-secondary, label -> badge, glyphicon -> font-awesome).
 *
 * Glyphicon icon fonts are provided separately by glyphicons.css in this
 * same compat/ folder (with its fonts/ subfolder).
 */

/* ===========================================================================
   Float / centering helpers (BS3 pull-*; BS4 uses float-left / float-right)
   =========================================================================== */
.pull-right   { float: right !important; }
.pull-left    { float: left !important; }
.center-block { display: block; margin-right: auto; margin-left: auto; }

/* BS3 marked visible faded elements with .in; BS4 renamed it to .show, leaving
   legacy markup/JS that applies "fade in" (e.g. the GSE data-collection tab
   panes rendered as 'fade in active') stuck at opacity:0 with no errors. Same
   specificity (0,2,0) as BS4's .fade:not(.show); wins by load order. */
.fade.in { opacity: 1; }

/* ===========================================================================
   Nested rows. BS3 .row was float/block based, so a .row nested directly inside
   another .row (legacy markup that skips the intervening column) stacked as
   full-width blocks. BS4 .row is display:flex;flex-wrap:wrap, so those child rows
   become flex ITEMS and line up horizontally instead of stacking (e.g. the
   Message Rules "Add New Rule" steps). Force a row that is a direct child of a
   row back to full width so it wraps onto its own line and stacks like BS3.
   Valid .col > .row nesting is unaffected.
   =========================================================================== */
.row > .row { -ms-flex: 0 0 100%; flex: 0 0 100%; max-width: 100%; }

/* ===========================================================================
   Base typography. BS4 Reboot sets body line-height to 1.5; BS3 used 1.42857143.
   The app inherits this, so under BS4 every text block (and anything inheriting,
   like the page footer) runs ~5% looser than QA and accumulates down long pages.
   Restore BS3's value app-wide. Elements with their own explicit line-height
   (.btn, .dropdown-menu, form controls) are unaffected and keep their rules.
   BS4 Reboot also changed the body text color to #212529; BS3 used #333. Restore it
   so inherited text (table headers, body copy, etc.) matches QA's shade. */
/* BS4 Reboot leaves the body font at the browser's 16px, so every page's text grew after the
   migration - inflating labels and em-based spacing and wrapping floated elements sooner.
   The pre-migration app rendered at 13px, NOT BS3's 14px default: verified against UAT,
   whose computed body font-size is 13px with line-height 18.5714px (13px x this rule's
   1.42857143 ratio - the Beyond theme era base). Restore the measured value. */
body { font-size: 13px; line-height: 1.42857143; color: #333; }

/* BS4 Reboot set b/strong to font-weight:bolder (relative - it resolves to 400 under
   light text, so <strong> stops looking bold); BS3 used bold (700, absolute). Restore
   BS3's absolute bold. */
b, strong { font-weight: bold; }

/* BS4 Reboot bumped several block margins vs BS3 (audited 2026-06-24 against QA):
   p / ul / ol bottom margin 1rem (16px) -> 10px, hr margin 1rem -> 20px, dd bottom
   .5rem -> 0. (Heading margins deferred - they also need the .modal-title / box /
   panel-title resets restored, or container headings gain an unwanted top margin.) */
p      { margin-bottom: 10px; }
ul, ol { margin-bottom: 10px; }
hr     { margin-top: 20px; margin-bottom: 20px; }
dd     { margin-bottom: 0; }

/* BS4 Reboot adds `a:not([href]):not([tabindex]) { color: inherit }` (BS3 had no such
   rule) at higher specificity than the skin's `a { color: #dd4b39 }`. So anchors WITHOUT
   an href - common for JS-driven links like the Search Results "Order No" cells - ignore
   the app's link red and inherit the text color. Restore the link color for hrefless
   anchors to match BS3/QA. (#dd4b39 mirrors Style.min.css's `a` color.) */
a:not([href]):not([tabindex]) { color: #dd4b39; }
/* ...except chrome that sits on a dark background: .widget-buttons action links are
   hrefless and were inheriting the widget header's white (BS4's original behavior).
   Revert those to inherit so they stay white instead of taking the content-link red.
   Higher specificity than the rule above. */
.widget-buttons a:not([href]):not([tabindex]) { color: inherit; }

/* BS3 set `a.list-group-item { color: #555 }`; BS4 dropped it, so the GseDataCollection
   step-nav links fall back to the skin's `a` link-red (#dd4b39). A plain `a.list-group-item`
   override ties the skin's anchor rule on specificity and loses on load order, so scope it to
   the verttab nav with higher specificity + !important. The active item keeps its own white.
   Covers both spellings: .list-group (GseDataCollection) and .listGroup (inspection-form tabs,
   whose icon is a .faHomeIcon that inherits this color rather than the skin's link-red). */
div.verttab-tab-menu div.list-group > a:not(.active),
div.verttab-tab-menu div.listGroup > a:not(.active) { color: #555 !important; }

/* BS3 list-group items were padding: 10px 15px; BS4 grew them to .75rem 1.25rem (12px 20px),
   costing 10px of horizontal text space per item. In narrow rails (the inspection form's
   col-lg-1 verttab, GseDataCollection's step nav) labels wrap sooner than the BS3/UAT build.
   Restore the BS3 padding. */
.list-group-item { padding: 10px 15px; }

/* BS3 set the ROOT font to 10px, so Style.css's `.faHomeIcon:before { font-size: 3rem }`
   rendered a 30px icon; BS4 leaves the root at the browser's 16px, inflating the icon to
   48px and the whole tab with it. Pin the BS3-rendered size. (Style.css's only real rem
   rule - fixed here rather than there to spare the Style.css/Style.min.css twin update.) */
div.verttab-tab-menu .faHomeIcon:before { font-size: 30px; }

/* BS4 Reboot changed heading margins (h4: BS3's 10px top/bottom -> 0 top, .5rem bottom).
   The global h4 restore is deferred (see the block-margins note above), but the ValueNet
   wizard rails (AppraisalReview, VendorReview, AppraisalReviewCompletion, GseDataCollection)
   draw their tab icon as an <h4 class="glyphicon">, so every tab lost 12px of height vs the
   BS3/UAT render (measured 66-67px vs BS3's ~78px). Restore BS3's h4 margins inside the
   verttab rail only; the inspection form's rail uses a div.faHomeIcon and is unaffected. */
div.verttab-tab-menu div.list-group > a h4,
div.verttab-tab-menu div.listGroup > a h4 { margin: 10px 0; }

/* At the lg tier (>=1200 in this recompile) the inspection form's col-lg-1 rail is ~8.3% of
   the row - about 60px of text space - so labels like "Neighborhood" and "Interior Addendum"
   can never fit on one line. Let THAT rail size to its widest label and give the remainder to
   the content pane, capped at the md-tier share (16.67%) so long labels cannot steal form
   space. min-width: 0 on the pane keeps wide grids inside it from blowing the flex row out.
   SCOPED to #inspectionFormContainer on purpose: an earlier class-global version of this rule
   made every verttab rail hug its labels, visibly shrinking rails with short labels
   (AppraisalReview, VendorReview) below their BS3 column width. Other rails keep their
   col-lg-* percentages. */
@media (min-width: 1200px) {
    #inspectionFormContainer > div.verttab-tab-menu { flex: 0 0 auto; width: auto; min-width: 110px; max-width: 16.66667%; }
    #inspectionFormContainer > div.verttab-tab-menu + div.verttab-tab { flex: 1 1 0%; width: auto; max-width: none; min-width: 0; }
}

/* Error modal (#divErrorBody, shared across all masters): roomier than BS4's default
   1rem .modal-body padding. App preference, not a compat fix. #id beats .modal-body. */
#divErrorBody { padding: 1.5rem; }

/* BS3 .pull-right floats a nav item right, but BS4's .nav-tabs is a flex container where the
   float is ignored. Use an auto left-margin to push a .pull-right tab to the right instead. */
.nav-tabs > li.pull-right, .nav-tabs > .pull-right { margin-left: auto; }

/* Tab count badges carry a blue fill from the skin; force the number white for contrast
   (BS4's bare .badge sets no color, so it was inheriting the dark tab-link text). */
.nav-tabs .badge { color: #fff !important; }
/* Sidebar treeview link color (#8aa4af, specificity 0,2,1) beats BS4's .badge {color:#fff} (0,1,0);
   bump to 0,2,2 to restore white badge text in the left-nav menu. */
.skin-blue .treeview-menu > li > a .badge { color: #fff; }

/* Comp-selector grid (DataTables scrollX+scrollY) clones the <thead> into the scroll body for
   column sizing; addSubjectData shows .pmSubjDataRow across the whole wrapper, so that clone
   renders too — an empty green copy whose border-b1 reads as a doubled line under the real
   subject row. Hide the clone (the real subject row lives in the scroll head). */
.dataTables_scrollBody .pmSubjDataRow { display: none !important; }

/* Comp grid header: under BS4 the sort-header cells collapse to line-height 1 (13px), too
   short for the sort glyph DataTables pins at bottom:8px (it clips) and making the header row
   read short. QA/BS3 had ~18.57px (13px x 1.42857). Restore the BS3 ratio on the header cells. */
#cswidgetholder table.dataTable thead th { line-height: 1.42857143 !important; }

/* border-collapse:separate tables (DataTables, and plain ones at the browser default) keep
   BS4's default border-spacing:2px, so .table-bordered cells show a 2px gap that reads as thick
   vertical separators vs QA. Zero it for every bordered table (comp grid, additional-comps, etc.). */
.table-bordered { border-spacing: 0; }

/* Comp Filter tab: its col-lg-3/5/4 columns sit directly in .container-fluid with no .row.
   BS3 floated cols laid out side-by-side without a row; BS4 cols are flex items needing a flex
   parent, so without one they stack vertically. Make the container itself the flex row.
   (Deliberately not adding a .row in markup: a .row's negative gutters would pull the content
   in vs QA, which has no row here — this keeps QA's spacing.) */
#csFilterWrapper > .container-fluid { display: flex; flex-wrap: wrap; align-items: flex-start; }

/* Review Comparables (step 3): the verttab columns (col-lg-1 tabs + col-lg-11 grid) sit in a
   col-lg-12 with no .row, so BS4 stacks them and the Market Sales Analysis grid wraps below the
   tabs. Make the wrapper the flex row (CSS, not a .row, to keep QA's gutters). */
#reviewComparableHolder > .row > .col-lg-12 { display: flex; flex-wrap: wrap; align-items: flex-start; }

/* BS3 contextual table-row classes (.success/.info/.warning/.danger) tinted the row; BS4
   renamed them to .table-success etc. and no longer styles the bare class. Re-add them
   (the comp-selector subject row is <tr class="success"> in the table header). */
.table tr.success > td, .table tr.success > th { background-color: #dff0d8; }
.table tr.info    > td, .table tr.info    > th { background-color: #d9edf7; }
.table tr.warning > td, .table tr.warning > th { background-color: #fcf8e3; }
.table tr.danger  > td, .table tr.danger  > th { background-color: #f2dede; }
.table-hover tbody tr.success:hover > td, .table-hover tbody tr.success:hover > th { background-color: #d0e9c6; }

/* Beyond colors .success text green (#53a93f) on the <tr>, but BS4/DataTables set the subject
   row's <th> color directly so the cells stop inheriting it. Re-assert it on the cells — this
   also tints their border-b1 green so it blends into the fill instead of a dark double line. */
.table tr.success > th, .table tr.success > td { color: #53a93f !important; }

/* GseDataCollection vertical-tab nav (#gseDcVertTabHolder = col-lg-1 col-md-2 col-sm-3 col-xs-3).
   BS4's lower grid breakpoints make it pick a narrower column than BS3 at 768-1199px
   (col-lg-1's 8.3% starts at >=992 in BS4 vs >=1200 in BS3; col-md-2 at >=768 vs >=992),
   so the nav is cramped vs QA. Re-assert BS3's widths over those two ranges. */
@media (min-width: 992px) and (max-width: 1199.98px) {
  #gseDcVertTabHolder { -ms-flex: 0 0 16.666667%; flex: 0 0 16.666667%; max-width: 16.666667%; }
  #gseInspectionContent { -ms-flex: 0 0 83.333333%; flex: 0 0 83.333333%; max-width: 83.333333%; }
}
@media (min-width: 768px) and (max-width: 991.98px) {
  #gseDcVertTabHolder { -ms-flex: 0 0 25%; flex: 0 0 25%; max-width: 25%; }
  #gseInspectionContent { -ms-flex: 0 0 75%; flex: 0 0 75%; max-width: 75%; }
}

/* ===========================================================================
   Visibility (BS4 dropped .hidden and the entire responsive show/hide set)
   BS3 breakpoints: xs < 768, sm 768-991, md 992-1199, lg >= 1200
   =========================================================================== */
.hidden { display: none !important; }

/* BS4 Reboot made the HTML `hidden` attribute `[hidden]{display:none!important}`
   (BS3 used plain `[hidden]{display:none}`). The app's pattern is to mark
   elements `hidden="hidden"` and REVEAL them with an inline display (set
   directly or via jQuery .show(), which writes inline display:block). BS4's
   !important now beats that inline style, so revealed elements stay hidden -
   e.g. the InternalUsers `main-sidebar` (`hidden="hidden" style="display:block"`)
   disappears. Re-assert the inline intent with higher specificity. Elements
   left at inline display:none (e.g. the VendorUsers sidebar) correctly stay
   hidden. */
[hidden][style*="display: block"]        { display: block !important; }
[hidden][style*="display: inline-block"] { display: inline-block !important; }
[hidden][style*="display: flex"]         { display: flex !important; }

@media (max-width: 767.98px)                          { .hidden-xs { display: none !important; } }
@media (min-width: 768px) and (max-width: 991.98px)   { .hidden-sm { display: none !important; } }
@media (min-width: 992px) and (max-width: 1199.98px)  { .hidden-md { display: none !important; } }
@media (min-width: 1200px)                            { .hidden-lg { display: none !important; } }

.visible-xs, .visible-sm, .visible-md, .visible-lg,
.visible-xs-block, .visible-xs-inline, .visible-xs-inline-block,
.visible-sm-block, .visible-sm-inline, .visible-sm-inline-block,
.visible-md-block, .visible-md-inline, .visible-md-inline-block,
.visible-lg-block, .visible-lg-inline, .visible-lg-inline-block { display: none !important; }

@media (max-width: 767.98px) {
  .visible-xs              { display: block !important; }
  .visible-xs-block        { display: block !important; }
  .visible-xs-inline       { display: inline !important; }
  .visible-xs-inline-block { display: inline-block !important; }
}
@media (min-width: 768px) and (max-width: 991.98px) {
  .visible-sm              { display: block !important; }
  .visible-sm-block        { display: block !important; }
  .visible-sm-inline       { display: inline !important; }
  .visible-sm-inline-block { display: inline-block !important; }
}
@media (min-width: 992px) and (max-width: 1199.98px) {
  .visible-md              { display: block !important; }
  .visible-md-block        { display: block !important; }
  .visible-md-inline       { display: inline !important; }
  .visible-md-inline-block { display: inline-block !important; }
}
@media (min-width: 1200px) {
  .visible-lg              { display: block !important; }
  .visible-lg-block        { display: block !important; }
  .visible-lg-inline       { display: inline !important; }
  .visible-lg-inline-block { display: inline-block !important; }
}

/* ===========================================================================
   AdminLTE top navbar - restore BS3 float layout.
   beyond.min.css (AdminLTE) lays the .main-header navbar out with floats and
   relies on BS3's navbar defaults. BS4 turns .navbar / .nav / .navbar-nav into
   flex containers (vertical items, justify-content: space-between), which
   throws the menu to the left and stacks the items. BS3 also padded the navbar
   links: base .nav>li>a was 10px 15px and .navbar-nav>li>a (>=768px) bumped the
   vertical to 15px -> effectively padding:15px (gone in BS4, which styles
   .nav-link instead). Re-scope to .main-header to restore the BS3 float layout
   + that 15px link padding. (BS4's auto dropdown caret is suppressed globally
   below.)
   =========================================================================== */
.main-header .navbar { display: block; padding: 0; }
.main-header .navbar-custom-menu { float: right; }
.main-header .navbar-nav { display: block; margin: 0; }
.main-header .navbar-nav > li { float: left; }
.main-header .navbar-nav > li > a { padding: 15px; }

/* AdminLTE LEFT SIDEBAR menu carries class "nav sidebar-menu". BS4's
   .nav { display: flex } turns that vertical menu into a horizontal flex row,
   so the items squish/overflow the ~230px sidebar and it renders blank. Force
   the block layout AdminLTE expects. (First surfaced on Layout.Master, which
   has a sidebar; OrderLayout.Master's order workspace has none.) */
.main-sidebar .sidebar-menu { display: block; }

/* AdminLTE user-menu dropdown spaces its items with double <br>s. BS3's floated
   col-xs-* collapsed most of that; the BS4 (flex) grid lets each <br> add a full
   line, so the menu opens up with big gaps. Drop the <br> spacers and give the
   rows a margin instead, sized to match PROD's item spacing (~20px gap). */
.user-menu .user-body br { display: none; }
.user-menu .user-body .col-xs-12 { margin-bottom: 20px; }

/* ===========================================================================
   Panels (BS4 replaced these with .card)
   =========================================================================== */
.panel {
  margin-bottom: 20px;
  background-color: #fff;
  border: 1px solid transparent;
  border-radius: 4px;
  box-shadow: 0 1px 1px rgba(0, 0, 0, .05);
}
.panel-body { padding: 15px; }
.panel-heading {
  padding: 10px 15px;
  border-bottom: 1px solid transparent;
  border-top-left-radius: 3px;
  border-top-right-radius: 3px;
}
.panel-title {
  margin-top: 0;
  margin-bottom: 0;
  font-size: 16px;
  color: inherit;
}
.panel-footer {
  padding: 10px 15px;
  background-color: #f5f5f5;
  border-top: 1px solid #ddd;
  border-bottom-right-radius: 3px;
  border-bottom-left-radius: 3px;
}
.panel-group { margin-bottom: 20px; }
.panel-default { border-color: #ddd; }
.panel-default > .panel-heading { color: #333; background-color: #f5f5f5; border-color: #ddd; }
.panel-primary { border-color: #337ab7; }
.panel-primary > .panel-heading { color: #fff; background-color: #337ab7; border-color: #337ab7; }
.panel-info { border-color: #bce8f1; }
.panel-info > .panel-heading { color: #31708f; background-color: #d9edf7; border-color: #bce8f1; }
.panel-success { border-color: #d6e9c6; }
.panel-success > .panel-heading { color: #3c763d; background-color: #dff0d8; border-color: #d6e9c6; }
.panel-warning { border-color: #faebcc; }
.panel-warning > .panel-heading { color: #8a6d3b; background-color: #fcf8e3; border-color: #faebcc; }
.panel-danger { border-color: #ebccd1; }
.panel-danger > .panel-heading { color: #a94442; background-color: #f2dede; border-color: #ebccd1; }

/* ===========================================================================
   Wells (removed in BS4)
   =========================================================================== */
.well {
  min-height: 20px;
  padding: 19px;
  margin-bottom: 20px;
  background-color: #f5f5f5;
  border: 1px solid #e3e3e3;
  border-radius: 4px;
  box-shadow: inset 0 1px 1px rgba(0, 0, 0, .05);
}
.well-sm { padding: 9px; border-radius: 3px; }
.well-lg { padding: 24px; border-radius: 6px; }

/* ===========================================================================
   Thumbnails (removed in BS4)
   =========================================================================== */
.thumbnail {
  display: block;
  padding: 4px;
  margin-bottom: 20px;
  line-height: 1.42857143;
  background-color: #fff;
  border: 1px solid #ddd;
  border-radius: 4px;
}
.thumbnail > img { display: block; max-width: 100%; height: auto; margin-right: auto; margin-left: auto; }

/* ===========================================================================
   btn-default (BS4 has no default variant; approximate the BS3 white/grey btn)
   =========================================================================== */
.btn-default { color: #333; background-color: #fff; border-color: #ccc; }
.btn-default:hover, .btn-default:focus, .btn-default:active, .btn-default.active {
  color: #333;
  background-color: #e6e6e6;
  border-color: #adadad;
}

/* ===========================================================================
   Button sizing. BS4 .btn is 1rem (16px) / line-height 1.5; BS3 was 14px /
   1.42857. The app's BS3 markup expects BS3 metrics, so every button renders
   slightly larger & taller under BS4 (first caught on the user-menu "Sign
   out"). Restore BS3 sizing for the base + lg/sm/xs variants. Base padding
   (.375rem .75rem = 6px 12px) and radius (.25rem = 4px) already match BS3.
   =========================================================================== */
.btn {
  font-size: 14px;
  line-height: 1.42857143;
  white-space: nowrap; /* BS3 had this; BS4 dropped it, so a button in a narrow column wraps (e.g. "Go To Cascades" in a col-lg-2) */
}
.btn-lg,
.btn-group-lg > .btn {
  padding: 10px 16px;
  font-size: 18px;
  line-height: 1.3333333;
  border-radius: 6px;
}
.btn-sm,
.btn-group-sm > .btn {
  padding: 5px 10px;
  font-size: 12px;
  line-height: 1.5;
  border-radius: 3px;
}
.btn-xs,
.btn-group-xs > .btn {
  padding: 1px 5px;
  font-size: 12px;
  line-height: 1.5;
  border-radius: 3px;
}

/* ===========================================================================
   Images
   =========================================================================== */
.img-responsive { display: block; max-width: 100%; height: auto; }
.img-circle     { border-radius: 50%; }
.img-rounded    { border-radius: 6px; }

/* ===========================================================================
   Forms
   =========================================================================== */
.help-block    { display: block; margin-top: 5px; margin-bottom: 10px; color: #737373; }
.control-label { font-weight: 700; }

/* BS4 .form-group margin-bottom is 1rem (16px); BS3 used 15px. The extra 1px per
   field accumulates down long forms and pushes the in-flow footer ~7px lower than
   QA (caught on the Order Search form). Restore BS3's 15px. */
.form-group { margin-bottom: 15px; }

/* BS4 Reboot bumped <label> margin-bottom to .5rem (8px); BS3 used 5px. The app
   puts bare <label>s in data widgets / table cells (e.g. Transaction Details),
   where the extra 3px inflates every row's height. Restore BS3's 5px. */
label { margin-bottom: 5px; }

/* BS4's flex .input-group has flex-wrap:wrap, so in narrow contexts (e.g. the appraisal
   grid's Date-of-Sale cells) the calendar addon drops onto its own line below the input.
   BS3's table-based input-group never wrapped; keep input + addon on one line. */
.input-group { -ms-flex-wrap: nowrap; flex-wrap: nowrap; }

/* BS4 sizes .form-control via calc(1.5em + .75rem + 2px) on a 16px / 1.5 base (~38px); QA/BS3
   used a flat 34px at 14px / 1.42857 line-height. Restore the BS3 sizing so form fields match QA
   app-wide (this also centers the file input's Choose File button). textarea + multi-row selects
   keep height:auto so they still grow with content. */
.form-control { height: 34px; font-size: 14px; line-height: 1.42857143; }
textarea.form-control,
select[multiple].form-control,
select[size].form-control { height: auto; }

/* The DataCollection / AppraisalReview forms use BS4-alpha custom-control markup
   (.custom-control-indicator / .custom-control-description) that BS4.6.2 no longer styles, so no
   indicator is ever drawn -- while BS4's .custom-control-input still hides the native input
   (opacity:0; position:absolute), leaving the radio/checkbox invisible. BS3 had no .custom-control-*
   rules, so the native control simply showed (what QA renders). Neutralize BS4's hiding + indent so
   the native input is visible inline again. (Nothing uses the BS4-stable .custom-control-label
   syntax, so this is safe app-wide.) */
.custom-control { display: inline-block; padding-left: 0; min-height: 0; }
.custom-control-input { position: static; width: auto; height: auto; margin-right: 0.25rem; opacity: 1; }

/* BS4 makes .form-inline a flex container. On the appraisal/review forms it wraps a full-width
   .row (input at width:90% + a help icon); as a flex item that .row collapses to the input's
   content width, "cutting short" fields like Lot Size / Year Built / Half Baths / Amenities.
   BS3's .form-inline was a block (the inline-block .form-control rule still keeps the input and
   its icon on one line), so restore that. */
.form-inline { display: block; }

/* BS4 (>=768px) also makes each .form-inline .form-group a flex row and each .form-inline label a
   centered flex box. The groups became block-level and stacked, and labels sat beside their control
   even where the page asks for display:block (e.g. the note Email modal: Custom Recipients dropped
   below Existing Recipients, labels moved to the left). BS3 laid the groups out inline-block side by
   side and left labels at their inline-block default with a 5px bottom margin; restore both. */
@media (min-width: 768px) {
  .form-inline .form-group { display: inline-block; vertical-align: middle; }
  .form-inline label { display: inline-block; margin-bottom: 5px; }
}

/* BS3 floated grid columns at each breakpoint, so cols sat side-by-side even when nested in another
   col instead of a .row (e.g. AppraisalReview "Comparables"). BS4's flex grid only lays columns out
   inside a .row, so loose cols stack. Restore BS3's full per-breakpoint float grid verbatim -- CSS
   ignores float on flex items, so cols inside a .row are untouched; only loose cols float, exactly
   as BS3 did (and below each breakpoint they go full-width and stack). */
.col-xs-1, .col-xs-2, .col-xs-3, .col-xs-4, .col-xs-5, .col-xs-6, .col-xs-7, .col-xs-8, .col-xs-9, .col-xs-10, .col-xs-11, .col-xs-12 { float: left; }
@media (min-width: 768px) {
  .col-sm-1, .col-sm-2, .col-sm-3, .col-sm-4, .col-sm-5, .col-sm-6, .col-sm-7, .col-sm-8, .col-sm-9, .col-sm-10, .col-sm-11, .col-sm-12 { float: left; }
}
@media (min-width: 992px) {
  .col-md-1, .col-md-2, .col-md-3, .col-md-4, .col-md-5, .col-md-6, .col-md-7, .col-md-8, .col-md-9, .col-md-10, .col-md-11, .col-md-12 { float: left; }
}
@media (min-width: 1200px) {
  .col-lg-1, .col-lg-2, .col-lg-3, .col-lg-4, .col-lg-5, .col-lg-6, .col-lg-7, .col-lg-8, .col-lg-9, .col-lg-10, .col-lg-11, .col-lg-12 { float: left; }
}

/* input-group-addon (BS4 uses input-group-text inside prepend/append wrappers).
   Styled to work as a flex child of BS4's flex .input-group. */
.input-group-addon {
  display: -ms-flexbox;
  display: flex;
  -ms-flex-align: center;
  align-items: center;
  padding: .375rem .75rem;
  margin-bottom: 0;
  font-size: 1rem;
  font-weight: 400;
  line-height: 1.5;
  color: #495057;
  text-align: center;
  white-space: nowrap;
  background-color: #e9ecef;
  border: 1px solid #ced4da;
  border-radius: .25rem;
}
.input-group > .input-group-addon:first-child { border-top-right-radius: 0; border-bottom-right-radius: 0; }
.input-group > .input-group-addon:last-child  { border-top-left-radius: 0; border-bottom-left-radius: 0; }
.input-group > .input-group-addon:first-child + .form-control { border-top-left-radius: 0; border-bottom-left-radius: 0; }

/* BS3-era markup often sets an inline width:100% on the .form-control inside an
   .input-group (harmless under BS3's table layout). Under BS4's flex .input-group that
   inline width forces the control onto its own row, wrapping it below the addon (e.g.
   the Analytics filter's date-range field). Re-assert BS4's flex sizing so the control
   stays inline with the addon; !important is required to beat the inline width. */
.input-group > .form-control {
  -ms-flex: 1 1 auto;
  flex: 1 1 auto;
  width: 1% !important;
}

/* ===========================================================================
   Tables - BS4 bumped default cell padding to .75rem (12px); BS3 was 8px, so
   every table got roomier. Restore BS3 density. The child-combinator selector
   (specificity 0,1,3) cleanly outranks BS4's .table td/.table th (0,1,1). The
   .table-condensed rule that follows (BS3's old -sm, also 0,1,3) overrides this
   one by source order for condensed tables, exactly like BS3.
   =========================================================================== */

/* BS3's bundled normalize reset table cell padding/spacing globally, which
   neutralized the legacy cellpadding/cellspacing attributes that ASP.NET
   server controls still render (e.g. CheckBoxList CellPadding="10" on the
   Vendor Performance Tiers state modal). BS4's reboot dropped the reset,
   reviving those attributes and inflating cells. Restore normalize; being
   element-level (0,0,1) every class-scoped rule (.table, DataTables) still
   wins, so only non-classed tables are affected - the same set BS3 zeroed. */
table { border-spacing: 0; }
td,
th { padding: 0; }
.table > thead > tr > th,
.table > tbody > tr > th,
.table > tfoot > tr > th,
.table > thead > tr > td,
.table > tbody > tr > td,
.table > tfoot > tr > td { padding: 8px; }

.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; }

/* IssueTracking Actions dropdown lives inside a cell of a `.table-responsive`
   table. `.table-responsive` is overflow-x:auto, and a non-visible overflow on
   one axis forces the other to auto too, so the container clips the open
   dropdown menu (which drops below its row past the table's edge) - it renders
   "inside" the table box, cut off. BS4's Popper also pins the menu to that
   scroll container. Let this table's container not clip; it's a full-width
   desktop admin table that fits, so losing horizontal auto-scroll is a non-issue. */
#issuesContainer .table-responsive { overflow: visible; }

/* ===========================================================================
   DataTables (Bootstrap-3 integration, dataTables.bootstrap.js 1.10.12) - the
   wrapper gets class "dataTables_wrapper form-inline". BS4 redefined
   .form-inline as display:flex, which turns the wrapper's child .row divs into
   flex items that shrink to content instead of filling 100% - starving the
   col-xs-6 length/filter columns of width (e.g. the notes filter dropdown
   landed left instead of right-aligned). BS3's .form-inline was a plain block;
   restore that so the rows span full width and the col-xs-6 50/50 split works.
   =========================================================================== */
.dataTables_wrapper.form-inline { display: block; }

/* BS4 (>=768px) also turns .form-inline label into a centered flex box
   (display:flex; justify-content:center; margin-bottom:0). Header captions
   wrapped in <label> (e.g. Message Center's <th><label>) became full-width
   flex containers with centered content; BS3 had no .form-inline label rule.
   Restore the BS3 label default - inline-block hands alignment back to the
   th's text-align, and 5px re-asserts the BS3 margin BS4 zeroed here. */
.dataTables_wrapper.form-inline label {
  display: inline-block;
  margin-bottom: 5px;
}

/* ===========================================================================
   Labels (BS4 renamed to .badge)
   =========================================================================== */
.label {
  display: inline;
  padding: .2em .6em .3em;
  font-size: 75%;
  font-weight: 700;
  line-height: 1;
  color: #fff;
  text-align: center;
  white-space: nowrap;
  vertical-align: baseline;
  border-radius: .25em;
}
.label-default { background-color: #777; }
.label-primary { background-color: #337ab7; }
.label-success { background-color: #5cb85c; }
.label-info    { background-color: #5bc0de; }
.label-warning { background-color: #f0ad4e; }
.label-danger  { background-color: #d9534f; }

/* ===========================================================================
   Caret - BS3 used an explicit <span class="caret">; BS4 dropped it and instead
   auto-generates a ::after caret on EVERY .dropdown-toggle. This is a BS3 app -
   it adds <span class="caret"> where it wants one - so re-style .caret AND
   globally suppress BS4's auto caret to kill stray/duplicate carets (the
   transaction-widget grid toggle, navbar menus, etc.).
   =========================================================================== */
.caret {
  display: inline-block;
  width: 0;
  height: 0;
  margin-left: 2px;
  vertical-align: middle;
  border-top: 4px dashed;
  border-right: 4px solid transparent;
  border-left: 4px solid transparent;
}
.dropdown-toggle::after { display: none; }

/* ===========================================================================
   Dropdown menus - BS3 styled .dropdown-menu > li > a; BS4 styles .dropdown-item
   instead, so BS3 dropdown markup (the "Additional Actions" menus, user menu,
   etc.) loses its item styling - notably white-space:nowrap, so long items wrap
   onto two lines and the menu won't widen to fit. Restore the BS3 item rules.
   =========================================================================== */
/* BS3 showed an open menu via `.open > .dropdown-menu`; BS4 dropped that rule and
   shows menus via `.dropdown-menu.show` instead. BS3-era plugins that still toggle
   `.open` themselves (bootstrap-multiselect in ucFilter, fuelux, bootstrap-
   timepicker) rely on the old rule, so their menus won't display under BS4 without
   it. Re-add it; BS4's own `.show` path is untouched. */
.open > .dropdown-menu { display: block; }

/* BS4 sets .dropdown-menu font-size to 1rem (16px); BS3 used 14px. The larger
   text wraps long items (the user menu's "Last Login: ... EDT" line) and makes
   the menu taller/looser. Restore 14px. */
.dropdown-menu { font-size: 14px; }
.dropdown-menu > li > a {
  display: block;
  padding: 3px 20px;
  clear: both;
  font-weight: 400;
  line-height: 1.42857143;
  color: #333;
  white-space: nowrap;
}
.dropdown-menu > li > a:hover,
.dropdown-menu > li > a:focus {
  color: #262626;
  text-decoration: none;
  background-color: #f5f5f5;
}
/* BS4 Reboot's a:not([href]):not([class]) { color: inherit } darkens the
   onclick-only items (no href), while the real <a href> links keep Style.css's
   .dropdown-menu>li>a{color:#777} - a two-tone menu. Re-apply #777 to the
   no-href items (specificity 0,2,2 beats the Reboot rule's 0,2,1) so every item
   matches, the way BS3/QA rendered them (no href distinction). */
.dropdown-menu > li > a:not([href]) { color: #777; }
.dropdown-menu > .divider {
  height: 1px;
  margin: 9px 0;
  overflow: hidden;
  background-color: #e5e5e5;
}
.dropdown-header {
  display: block;
  padding: 3px 20px;
  font-size: 12px;
  line-height: 1.42857143;
  color: #777;
  white-space: nowrap;
}

/* ===========================================================================
   Modal header - restore BS3 layout.
   BS3 markup puts the close button BEFORE the title and floats it right.
   BS4 makes .modal-header a flex row (justify-content: space-between), which
   would flip that order. Force block layout so .close floats to the right
   and the title stays on the left.
   =========================================================================== */
.modal-header { display: block; }

/* The app puts width utilities (e.g. width-97p) on .modal-dialog for wide modals; BS3 had no
   modal-dialog max-width so they honored it. BS4's .modal-dialog { max-width: 500px } caps them,
   shrinking the modal (e.g. step 5's Edit Property Inspection). Let the width utility win. */
.modal-dialog[class*="width-"] { max-width: none; }

/* BS3's default modal width was 600px (@ >=768px) with NO max-width; BS4 instead caps
   .modal-dialog at 500px, visibly shrinking every modal that relies on the default
   (e.g. the vendor dashboards' Out of Office settings). Restore the BS3 behavior:
   fixed 600px default, and max-width:none rather than a 600px cap because a max-width
   would override the inline width: styles several modals carry (900px on
   GseDataCollection, 100%/97%/60% on OrderStatus/WorkQueues/AppraisalReview) - inline
   width beats stylesheet width, but nothing beats a max-width cap. The :not() guards
   keep explicitly sized modals (.modal-sm/-lg/-xl, width utilities) out of this rule -
   without them its higher specificity would override those sizes. */
@media (min-width: 768px) {
    .modal-dialog:not(.modal-sm):not(.modal-lg):not(.modal-xl):not([class*="width-"]) {
        width: 600px;
        max-width: none;
    }
}

/* Modal footers that lay content out through an inner wrapper - a grid .row
   (VendorAssignment, IssueTracking, GWUserGuides, AIReadyPDFPreview), a
   space-between flex div (the tagImageEditor / vnInspEditorModal footer and its
   inline copies), or the ICA agreement asp:Panels: BS4's flex .modal-footer
   shrinks wrappers to content width and flex-ends them, collapsing the intended
   left/right split. Span the footer instead - BS4.6's footer is flex-wrap:wrap,
   so 100%-basis wrappers stack like the BS3 blocks they were written for; grids
   get their 50/50 col split back and floats inside them work again. */
.modal-footer > .row,
.modal-footer > div[style*="space-between"],
.modal-footer > #divICAAcceptDecline,
.modal-footer > #divConfirmDecline { flex: 1 1 100%; }

/* Modal footers with left-floated Cancel buttons: BS4 makes .modal-footer a flex row
   (justify-content:flex-end) and floats don't apply to flex items, so the Cancel bunches on the
   right next to Save/OK. Push it left with a flex auto-margin. Covers the three idioms in use:
   the .pull-left class (Add Document etc.), the .float-l utility (AppraisalReview1004D photo
   modal), and inline style="float: left" (the UAD modal family - Basement Details etc.). */
.modal-footer .pull-left,
.modal-footer .float-l,
.modal-footer [style*="float: left"],
.modal-footer [style*="float:left"] { margin-right: auto; }

/* Add Note / Add Document (and similar) modals put Cancel + Save in two col-lg-6 columns; below
   the lg breakpoint those stack and Save drops under Cancel. Keep the *button* columns at 50% at
   any width so the pair stays side by side — scoped via :has() to columns holding a .pull-left /
   .pull-right button, so adjacent form columns (file input, type) still stack responsively.
   Scoped to .modal: on page-level rows (e.g. Vendor Performance Tiers' Save row, an empty
   col-lg-6 + a button col-lg-6) the pinned 50% column wraps to its own line below lg and
   strands the right-floated button at mid-page. */
.modal .col-lg-6:has(> .btn.pull-left),
.modal .col-lg-6:has(> .btn.pull-right) { flex: 0 0 50%; max-width: 50%; }

/* Image-editor (tagImageEditor) tool toggles: the custom JS marks the active tool .btn-primary.
   BS3's data-toggle="buttons" plugin also added .active, giving it BS3's .btn.active inset
   "pressed" shadow; BS4 dropped that plugin, so the active tool gets no .active and loses the
   shadow. Re-add the pressed shadow on the active (.btn-primary) tool to match QA. */
#tagImageEditorActionBtnsArea label.btn-primary { box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); }
/* BS4 restyles .close for its flex header (padding:1rem + margin:-1rem -1rem -1rem auto),
   which bloats the X to ~49x58px and pushes the header to 63px tall. QA's close is the
   bare 26px icon - no padding, just a -2px top nudge. Reset to match. */
.modal-header .close { margin: -2px 0 0; padding: 0; }

/* BS4 sets pointer-events:none on BOTH .modal and .modal-dialog, restoring
   pointer-events:auto ONLY on .modal-content (so clicks in the empty area
   around the dialog fall through to dismiss). Modals whose content is NOT
   wrapped in .modal-content - e.g. ucAddUser's "Edit User" uses
   .modal-dialog > .widget - inherit pointer-events:none, so the ENTIRE modal
   (tabs, inputs, Save/Cancel) is unclickable. Restore auto on the dialog so the
   content works regardless of its wrapper. */
.modal-dialog { pointer-events: auto; }

/* Modal widths. BS3's default was 600px; modals with wider content (the Help modal's
   700px .list-3-column) expanded to fit, and the app's intentionally-wide modals set
   their own width (.width-100p, inline width). BS4 clamps every .modal-dialog to
   500px. An earlier fix here dropped the cap entirely (max-width:none) - but that made
   NARROW modals (e.g. the "Error!" alert) stretch full-width, since an auto-width
   dialog with no cap fills the viewport. So restore BS3's 600px default and lift the
   cap only where a modal actually needs to be wider. */
.modal-dialog { max-width: 600px; }
.modal-sm     { max-width: 300px; }
.modal-lg     { max-width: 900px; }
#helpModal .modal-dialog      { max-width: 600px; }            /* match QA: same 600px cap as the default (was max-width:none, which let short help content stretch full-width) */
.modal-dialog.width-100p      { max-width: 100% !important; } /* full-width modals (admin Edit User) */
.modal-dialog[style*="width"] { max-width: none !important; } /* inline-width modals (ucProfile 75%) */

/* ===========================================================================
   Navs - BS3 base link rule. BS3 had .nav>li>a { position:relative; display:
   block; padding:10px 15px }. BS4 dropped it (it styles .nav-link instead), so
   legacy <li><a> nav markup loses display:block - and an INLINE <a> with
   vertical padding mis-positions: the navbar links rendered ~13px too high,
   sitting ABOVE the navbar instead of inside it (aTop -13 vs navTop 0).
   position:relative also re-enables the absolute-positioned .label badge
   (Style.css: .main-header .navbar .nav>li>a>.label{position:absolute}).
   The .main-header navbar rule above still overrides padding to 15px.
   =========================================================================== */
.nav > li > a { position: relative; display: block; padding: 10px 15px; }

/* ===========================================================================
   Nav tabs / pills with legacy BS3 <li><a> markup
   (BS4 styles .nav-link instead of li > a)
   =========================================================================== */
.nav-tabs { border-bottom: 1px solid #ddd; }
.nav-tabs > li, .nav-pills > li { display: inline-block; }
.nav-tabs > li > a, .nav-pills > li > a { display: block; padding: 10px 15px; text-decoration: none; }
.nav-tabs > li > a {
  margin-right: 2px;
  line-height: 1.42857143;
  border: 1px solid transparent;
  border-radius: 4px 4px 0 0;
}
.nav-tabs > li.active > a,
.nav-tabs > li.active > a:hover,
.nav-tabs > li.active > a:focus {
  color: #555;
  cursor: default;
  background-color: #fff;
  border: 1px solid #ddd;
  border-bottom-color: transparent;
}
.nav-pills > li > a { border-radius: 4px; }
.nav-pills > li.active > a,
.nav-pills > li.active > a:hover,
.nav-pills > li.active > a:focus { color: #fff; background-color: #337ab7; }
/* Disabled tabs/pills: BS3 set cursor:not-allowed via .nav > li.disabled > a; BS4
   moved disabled styling to .nav-link.disabled, which the app's <li class="disabled">
   markup doesn't use, so restore the not-allowed cursor here. */
.nav-tabs > li.disabled > a,
.nav-pills > li.disabled > a { cursor: not-allowed; }

/* ===========================================================================
   Pagination - BS3 styled .pagination > li > a as bordered page buttons; BS4
   replaced that with .page-item/.page-link, so BS3 pager markup (DataTables'
   Bootstrap-3 integration renders <ul class="pagination"><li><a>) loses all
   button styling and shows as plain "Previous1234Next" text. Restore BS3.
   =========================================================================== */
.pagination { display: inline-block; padding-left: 0; margin: 20px 0; border-radius: 4px; }
.pagination > li { display: inline; }
.pagination > li > a,
.pagination > li > span {
  position: relative;
  float: left;
  padding: 6px 12px;
  margin-left: -1px;
  line-height: 1.42857143;
  color: #337ab7;
  text-decoration: none;
  background-color: #fff;
  border: 1px solid #ddd;
}
.pagination > li:first-child > a,
.pagination > li:first-child > span { margin-left: 0; border-top-left-radius: 4px; border-bottom-left-radius: 4px; }
.pagination > li:last-child > a,
.pagination > li:last-child > span { border-top-right-radius: 4px; border-bottom-right-radius: 4px; }
.pagination > li > a:hover,
.pagination > li > span:hover,
.pagination > li > a:focus,
.pagination > li > span:focus { z-index: 2; color: #23527c; background-color: #eee; border-color: #ddd; }
.pagination > .active > a,
.pagination > .active > span,
.pagination > .active > a:hover,
.pagination > .active > span:hover,
.pagination > .active > a:focus,
.pagination > .active > span:focus { z-index: 3; color: #fff; cursor: default; background-color: #337ab7; border-color: #337ab7; }
.pagination > .disabled > span,
.pagination > .disabled > a,
.pagination > .disabled > a:hover,
.pagination > .disabled > a:focus,
.pagination > .disabled > span:hover,
.pagination > .disabled > span:focus { color: #777; cursor: not-allowed; background-color: #fff; border-color: #ddd; }

/* ===========================================================================
   Login page (LoginLayout) - BS3-breakpoint override. The login box uses
   col-md-* (BS3 md >= 992px). BS4 activates col-md at >= 768px, so at 768-991px
   the form became a 33% column instead of PROD's full-width. Scope BS3's
   md>=992 behaviour to the login columns: full-width below 992px (they pick up
   col-md-4 + offset/swap at >= 992, matching PROD). Targeted by id because an
   app-wide BS4->BS3 breakpoint shift would mean re-implementing the whole grid.
   =========================================================================== */
@media (max-width: 991.98px) {
  #loginMessage,
  #loginSection {
    -ms-flex: 0 0 100%;
    flex: 0 0 100%;
    max-width: 100%;
    margin-left: 0;
    left: auto;
    right: auto;
  }
}

/* Footer (ucMasterLoginFooter / ucMasterPageFooter) center column uses
   col-lg-4 col-md-6 (BS3 md>=992). BS4 activates col-md at >=768, so at 768-991px
   the footer text squeezed into 50% width and wrapped taller (90px vs PROD 68px)
   - same BS4-vs-BS3 breakpoint issue as the login form. The flanking version/IP columns
   hide below lg (1200px), so the middle copyright column must span full-width there too,
   else its centered text rides the left edge. Full-width below 1200 to match PROD.
   Shared .main-footer, so this covers every layout's footer. */
@media (max-width: 1199.98px) {
  .main-footer [class*="col-md-"] { -ms-flex: 0 0 100%; flex: 0 0 100%; max-width: 100%; width: 100%; }
}

/* ===========================================================================
   Field labels (.tdLabelLeftAlignSimple) - short table-cell form labels. Under BS4's
   lowered grid breakpoints the surrounding columns are narrower, so the cell can wrap
   the label onto two lines (e.g. "Select a Client:" on CascadeGroupMaintenance). Keep
   them single-line like PROD.
   =========================================================================== */
.tdLabelLeftAlignSimple { white-space: nowrap; }

/* ===========================================================================
   Cascade / CascadeGroup Maintenance toolbar. The "Go To Cascades" button (col-lg-2) and
   the client picker (#ClientSelection, col-lg-5) sit side-by-side. BS4 activates col-lg at
   >=992 but BS3/QA at >=1200 (stacking below that), so at 992-1199 LOCAL squeezes them
   side-by-side in columns too narrow for the nowrap button -> it overflows into the client
   column and "Select a Client:" overlaps. QA stacks them below 1200; match that by dropping
   the client picker onto its own line below 1200 (shared #ClientSelection covers both pages).
   =========================================================================== */
@media (max-width: 1199.98px) {
  #ClientSelection { -ms-flex: 0 0 100%; flex: 0 0 100%; max-width: 100%; }
}

/* ===========================================================================
   Active tab/pill PANE on load. BS3 marked the shown pane .fade.in; BS4 uses .fade.show
   for the opacity, so a pane authored as "tab-pane fade in active" renders display:block
   but opacity:0 (invisible) until BS4's JS adds .show on the first tab switch (e.g. the
   Edit User modal's first permissions tab loads blank). Bridge BS3's .in to .show opacity.
   (Hidden panes stay hidden - display:none from the missing .active still wins.)
   =========================================================================== */
.fade.in { opacity: 1; }

/* BS3 .collapse.in = expanded (display:block); BS4 renamed it to .collapse.show. The eonasdan
   datetimepicker shows its calendar/time views via .collapse.in, so under BS4 the calendar stays
   display:none and only the clock/clear footer renders (e.g. OrderStatus Appointment Date). Map it. */
.collapse.in { display: block; }
