/* ---------------------------------------------------------------------------
 * Site-wide overrides carried across from the live C5 site.
 *
 * MUST be linked AFTER /themes/SSO/css/syed-main.css in the layout <head>.
 * These rules have the same specificity as the theme's own (#header, .navigation
 * ul li a …), so the later stylesheet wins. They previously lived in
 * src/app/globals.css, which Next injects BEFORE the manually linked theme CSS —
 * so every rule here was silently losing to syed-main.css and the header rendered
 * as the theme's transparent overlay instead of the live site's static white band.
 *
 * On the live site these rules ship inside the alert-bar HTML block's <style>.
 * They are NOT alert styling — they define the header's actual appearance on
 * every page, and the alert bar happens to be on every page. The alert bar itself
 * is config-driven (src/data/alert.ts) and currently disabled; toggling it must
 * not change the header, which is why these live separately.
 * ------------------------------------------------------------------------- */

#header {
  position: static;
}

#header:after {
  content: none;
}

#header .head-right:before {
  background-color: #d6d5d6;
}

#header .head-right .head-top-l a {
  color: #700426;
}

#header .head-right .head-top-l a.phone {
  border-color: #d6d5d6;
}

.navigation ul li a {
  color: #453f42;
}

#_header {
  position: relative;
}

#mobile-menu .menu-trigger {
  border-color: #000;
}

#mobile-menu .menu-trigger span,
#mobile-menu .menu-trigger span:after,
#mobile-menu .menu-trigger span:before {
  background: #000;
}

/* Alert-bar presentation, kept so enabling it in src/data/alert.ts needs no CSS work. */
.custom_alert {
  background-color: #eaf7eb;
  border-color: #eaf7eb;
  border-radius: 0;
  margin: 0;
  text-align: center;
  font-size: 15px;
  font-weight: 500;
  color: #34942d;
}

.custom_alert a {
  text-decoration: underline;
  color: #354180;
}

.custom_alert .phead {
  font-size: 16px;
  font-weight: bold;
  margin-bottom: 10px;
  color: #34942d;
}

button.close {
  float: right;
  font-size: 21px;
  font-weight: normal;
  line-height: 1;
  color: #34942d;
  text-shadow: 0 1px 0 #222;
  opacity: 0.7;
}

/* Honeypot field — in the DOM for bots, invisible to humans. */
.fake,
#fake {
  margin: 0 !important;
  padding: 0 !important;
  width: 0 !important;
  height: 0 !important;
  display: block !important;
  visibility: hidden !important;
  opacity: 0 !important;
}

.sidebar .consultation-form .form-title {
  font-size: 25px;
}

/* ---------------------------------------------------------------------------
 * Browser autofill.
 *
 * Chrome paints autofilled fields with its own pale-blue background and dark
 * text, overriding the page's styling. On the maroon consultation form — whose
 * inputs are transparent with white text — that turns every autofilled field
 * into a visible pale box with unreadable dark text, which is what it looked
 * like in testing.
 *
 * The long background-color transition is the reliable way to keep the field's
 * own background: Chrome's autofill background is applied in a way that cannot
 * be overridden directly, but it will not animate, so a transition that never
 * completes leaves the original showing. -webkit-text-fill-color handles the
 * text, since `color` alone is ignored while autofilled.
 * ------------------------------------------------------------------------- */
input:-webkit-autofill,
input:-webkit-autofill:hover,
input:-webkit-autofill:focus,
input:-webkit-autofill:active,
textarea:-webkit-autofill,
select:-webkit-autofill {
  transition: background-color 100000s ease-in-out 0s;
}

/* Maroon sidebar form — white text on a transparent field. */
.consultation-form input:-webkit-autofill,
.consultation-form input:-webkit-autofill:hover,
.consultation-form input:-webkit-autofill:focus,
.consultation-form input:-webkit-autofill:active {
  -webkit-text-fill-color: #fff;
  caret-color: #fff;
}

/* ---------------------------------------------------------------------------
 * Upload button.
 *
 * On the live site .btn_purple / .full_width are defined in a stylesheet served
 * by growdentaltest7.info — the reviews widget's own CSS. So the live upload
 * button's styling depends on that test domain being up; if it goes away, the
 * button loses its appearance. Defining the rules here instead means the form
 * does not depend on a third party for its own chrome.
 *
 * Values taken from the live computed style: #700426, white, 4px radius, 14px,
 * full width, 34px tall.
 * ------------------------------------------------------------------------- */
.btn_purple {
  background-color: #700426;
  color: #fff;
  border: none;
  border-radius: 4px;
  font-size: 14px;
  line-height: 1.4;
  padding: 6px 12px;
  min-height: 34px;
  cursor: pointer;
  text-align: center;
}

.btn_purple:hover,
.btn_purple:focus {
  background-color: #aeacad;
  color: #fff;
}

.full_width {
  width: 100%;
  display: block;
}

.upload_files .drops {
  margin-bottom: 10px;
}

/* ---------------------------------------------------------------------------
 * Full-width pages.
 *
 * syed-main.css sizes `.inner-content .inner-left` at a fixed 680px floated left,
 * which is correct for the two-column pages but leaves the full-width ones (the
 * footer/legal pages, the two PDF medical forms) using half the container with
 * dead space where the sidebar would have been.
 *
 * Live gets its full-width rule from the reviews widget's stylesheet on
 * growdentaltest7.info — the same test domain that supplies .btn_purple. That
 * makes the live layout of these pages dependent on a third party staying up, so
 * the rule is defined here instead, keyed on the page's own `full_width` html
 * class. Matches live exactly at desktop: 1130px inside the 1160px container.
 *
 * Only above the tablet breakpoint: below 1024px syed-main.css already sets
 * width:100%/float:none for every page, so there is nothing to override.
 * ------------------------------------------------------------------------- */
@media (min-width: 1160px) {
  html.full_width .inner-content .inner-left {
    float: none;
    width: 100%;
  }
}
