/* BS5: Restore bold labels (BS3 had font-weight:700 on labels by default) */
label:not(.list-group-item):not(.form-check-label):not(.btn) {
    font-weight: 700;
}

/* BS5: modal-lg is 800px vs BS3 900px — restore wider default */
@media (min-width: 992px) {
    .modal-lg,
    .modal-xl {
        --bs-modal-width: 900px;
    }
}

#loading {
    position:fixed;
    top:50%;
    left:50%;
    z-index:1104;
}

.top-buffer {
    margin-top: 10px;
}

.top-buffer-30 {
    margin-top: 30px;
}

 .no-wrap {
    white-space: nowrap;
}

.hiddenElement {
visibility: hidden;
display: none;
}

.hide {
    display: none !important;
}

.noBorder {
    border: 0;
}

.totalPolicyContainer {
    border: none;
    background-color: transparent;
    pointer-events: none;
}

#idletimeout { 
    background:#CC5100; 
    border:3px solid #FF6500; 
    color:#fff; 
    font-family:arial, sans-serif; 
    text-align:center; 
    font-size:12px; 
    padding:10px; 
    position:relative; 
    top:0px; 
    left:0; 
    right:0; 
    z-index:100000;  
}
#idletimeout a { 
    color:#fff; 
    font-weight:bold 
}
#idletimeout span { 
    font-weight:bold 
}

.error {
    color:#FF0000;
    font-weight: bold;
}
.color-red {
    color: #cb262b;
}

.color-blue {
    color: #87dadf;
}

.color-white {
    color: white;
}

.color-black {
    color: black;
}
img {
    max-width: 100%;
    height: auto;
}

span.fa {
    margin-left:  10px;
    margin-right: 10px;
    color: black;
}

.back-button-appearance {
-webkit-appearance: none;
-moz-appearance: none;
	color: #777777;
}

.bg-color-grey {
    background-color: #99999a;
}

/* BS5: removed unscoped grey backgrounds that bleed into disclosure modals.
   Why: PROD (BS3) didn't load this stylesheet — the link was commented in _Layout.
   BS5 migration enabled the file, exposing these rules as a regression.
   Specific tables retain grey via #privacy-table rules below. */

.printable-footer {
    padding: 10px 0;
    background-color: transparent;
    border-top: none;
    border-bottom: none;
    color: #2f3033;
    font-size: 14px;
}

.printable-page {
    max-width: 1200px;
    margin: 0 auto;
    padding: 0 24px;
}

.popover {
    color: black;
}

.pt-25 {
    padding-top: 25px;
}

.calendar-modification {
    color: black;
    background-color: #ffffff !important;
}

.invalid-zip > .validation-summary-errors > ul > li {
    list-style-type: none;
    color: red;
    text-align: center;
}

.Summit-hero-image {
    background-image: url(https://Summitcarlson.com/wp-content/uploads/2018/03/real-estate_web-1.jpg);
    background-repeat: no-repeat;
    background-position: center;
    background-size: cover;
}

td {
    border: 1px solid black;
    background-color: #99999A;
}

/* Printable Privacy / SupplementalPrivacy pages match PROD where this
   stylesheet was never loaded — the global td bg #99999A combined with
   the table { color: #999 } rule in style.css renders the data column as
   grey-on-grey (invisible). Restore PROD parity with a transparent bg
   scoped to printable pages. The existing #supplemental-table override
   below still wins via id specificity. */
.printable-page td {
    background-color: transparent;
}

/* Bug 102411: Restore PROD-style dark band on the dynamic footer's .subfooter.
   The marketing style.css served on TEST/BS5 was redesigned and now has
   `.light .subfooter { background-color: var(--Builder-White) }` which paints
   the band white. The disclosure paragraphs inside use `.color-white`, so the
   text becomes white-on-white (invisible) and only the bordered "Privacy
   Policy Updated" box is readable. PROD's older style.css had no `.light`
   override, so the dark `.subfooter` bg won and the disclosure text was
   visible. Force the dark band back. */
footer#footer.light .subfooter {
    background-color: #585858;
    color: #fff;
}

footer#footer.light .subfooter a {
    color: #fff;
}

/* Bug 102411 follow-up: The "here" hyperlink inside the .privacybox
   ("Privacy Policy Updated" notice) was painted white by the rule above
   but the privacybox itself has a white background — so the link became
   invisible. Restore PROD parity by inheriting the privacybox's black
   color (PROD's "here" links inside .privacybox compute to rgb(33,33,33)
   on the same white bg). Higher specificity (id + 3 classes + element)
   wins over the broader subfooter rule above. */
footer#footer.light .subfooter .privacybox a {
    color: inherit;
}

#supplemental-table tbody tr td {
    background-color: #FFF;
}

.table-padding {
    padding-right: 25%;
}

.privacybox {
    background-color: white;
    color: black;
    border: 3px solid black;
}

.privacybox {
    background-color: white;
    color: black;
    border: 3px solid black;

}

.column-sizing {
    width: 70%;
}

#privacy-table tbody tr td {
    background-color: #FFF;
}

.modal-body #privacy-table tbody tr td {
    background-color: #99999A;
}

/* BS5: Suppress red exclamation SVG on .form-control.is-invalid when inside an
   .input-group (calendar/$ addon already provides visual context — the SVG
   would crowd the right side). Same for green check on .is-valid. */
.input-group > .form-control.is-invalid,
.input-group > .form-select.is-invalid,
.input-group > .form-control.is-valid,
.input-group > .form-select.is-valid {
    background-image: none !important;
    padding-right: 0.75rem !important;
}

/* Bug 102529: Force opaque white background and visible border on the
   Flatpickr calendar dropdown when it opens on the Summit Quote pages.
   The page background bleeds through the open calendar otherwise, leaving
   the months header and weekday row visually mixed with the address text
   underneath even after the calendar root was made opaque. flatpickr's
   default CSS sets background:transparent on .flatpickr-month and
   .flatpickr-weekdays, which here lets the body text bleed through the
   header strip. Force every internal container to inherit white. */
.flatpickr-calendar.open,
.flatpickr-calendar.inline {
    background: #fff !important;
    opacity: 1 !important;
    border: 1px solid #e6e6e6;
    box-shadow: 0 3px 13px rgba(0, 0, 0, 0.15);
    z-index: 1056;
}

.flatpickr-calendar.open .flatpickr-months,
.flatpickr-calendar.open .flatpickr-months .flatpickr-month,
.flatpickr-calendar.open .flatpickr-current-month,
.flatpickr-calendar.open .flatpickr-weekdays,
.flatpickr-calendar.open .flatpickr-innerContainer,
.flatpickr-calendar.open .flatpickr-rContainer,
.flatpickr-calendar.open .flatpickr-days,
.flatpickr-calendar.open .dayContainer {
    background: #fff !important;
}

/* Bug 102529 follow-up: Force the Flatpickr month/year header to retain
   its 34px height so the weekday row sits below it instead of rendering
   on top. .flatpickr-current-month is position:absolute and only its
   parent .flatpickr-month holds the height — pin both, plus reset BS5
   form-control/form-select reboot styles on the month <select> and year
   <input> so they render inline-block at the right size. */
.flatpickr-calendar.open .flatpickr-months {
    display: flex !important;
    align-items: stretch !important;
    height: 34px !important;
    min-height: 34px !important;
    flex: 0 0 34px !important;
    overflow: visible !important;
}

.flatpickr-calendar.open .flatpickr-months .flatpickr-month {
    height: 34px !important;
    min-height: 34px !important;
    line-height: 1 !important;
    text-align: center !important;
    position: relative !important;
    overflow: hidden !important;
    flex: 1 1 auto !important;
}

.flatpickr-calendar.open .flatpickr-current-month {
    font-size: 135% !important;
    line-height: 1 !important;
    font-weight: 300 !important;
    color: inherit !important;
    position: absolute !important;
    width: 75% !important;
    left: 12.5% !important;
    padding: 7.48px 0 0 0 !important;
    height: 34px !important;
    display: inline-block !important;
    text-align: center !important;
}

.flatpickr-calendar.open .flatpickr-current-month .flatpickr-monthDropdown-months,
.flatpickr-calendar.open .flatpickr-current-month .numInputWrapper input.cur-year {
    background: transparent !important;
    border: 0 !important;
    border-radius: 0 !important;
    box-shadow: none !important;
    height: auto !important;
    margin: 0 !important;
    line-height: inherit !important;
    font-family: inherit !important;
    font-size: inherit !important;
    font-weight: 600 !important;
    color: inherit !important;
    display: inline-block !important;
    vertical-align: baseline !important;
    width: auto !important;
    max-width: none !important;
}

.flatpickr-calendar.open .flatpickr-current-month .numInputWrapper input.cur-year {
    padding: 0 !important;
    -webkit-appearance: none !important;
    -moz-appearance: none !important;
    appearance: none !important;
}

/* Bug 102529 follow-up #2: Keep the native chevron arrow on the month <select>
   so users can tell it's a dropdown. Prior fix stripped it via appearance:none.
   Use BS5's form-select chevron SVG inlined as a background-image; reserve room
   for it via right padding. The select itself still has no border / transparent
   bg so it sits flat in the month header. */
.flatpickr-calendar.open .flatpickr-current-month .flatpickr-monthDropdown-months {
    -webkit-appearance: none !important;
    -moz-appearance: none !important;
    appearance: none !important;
    background-image: url("data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3e%3cpath fill='none' stroke='%23343a40' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m2 5 6 6 6-6'/%3e%3c/svg%3e") !important;
    background-repeat: no-repeat !important;
    background-position: right 0 center !important;
    background-size: 12px 12px !important;
    padding: 0 14px 0 0 !important;
    cursor: pointer !important;
}

.flatpickr-calendar.open .flatpickr-current-month .numInputWrapper {
    width: 7ch !important;
    display: inline-block !important;
    height: auto !important;
    vertical-align: baseline !important;
}

.flatpickr-calendar.open .flatpickr-prev-month,
.flatpickr-calendar.open .flatpickr-next-month {
    position: absolute !important;
    top: 0 !important;
    height: 34px !important;
    padding: 10px !important;
    z-index: 3 !important;
}

.flatpickr-calendar.open .flatpickr-prev-month { left: 0 !important; }
.flatpickr-calendar.open .flatpickr-next-month { right: 0 !important; }

.flatpickr-calendar.open .flatpickr-innerContainer {
    display: block !important;
    overflow: hidden !important;
}

.flatpickr-calendar.open .flatpickr-weekdays {
    width: 100% !important;
    height: 28px !important;
    line-height: 28px !important;
    text-align: center !important;
    overflow: hidden !important;
    display: flex !important;
    align-items: center !important;
}

.flatpickr-calendar.open .flatpickr-weekdaycontainer {
    display: flex !important;
    flex: 1 !important;
}

.flatpickr-calendar.open span.flatpickr-weekday {
    cursor: default !important;
    font-size: 90% !important;
    background: transparent !important;
    line-height: 1 !important;
    margin: 0 !important;
    text-align: center !important;
    display: block !important;
    flex: 1 !important;
    font-weight: bolder !important;
}

/* BS5: Suppress red exclamation SVG on .form-control.is-invalid when inside an
   .input-group (calendar/$ addon already provides visual context — the SVG
   would crowd the right side). Same for green check on .is-valid. */
.input-group > .form-control.is-invalid,
.input-group > .form-select.is-invalid,
.input-group > .form-control.is-valid,
.input-group > .form-select.is-valid {
    background-image: none !important;
    padding-right: 0.75rem !important;
}