/*
 * The only hand-written CSS in the port.
 *
 * Everything else is Duda's own cascade, lifted from the live document and
 * linked in its original order. These rules exist because a single static
 * document has to stand in for three device documents, or because a piece of
 * Duda's behaviour lived in its runtime rather than in its stylesheets.
 * Each one says which.
 */

/* 1. Both headers ship in one document; show the one for this width.
 *    The marker class is added BY THE PORTER onto Duda's own top-level chrome
 *    elements — never onto a wrapper around them, because the sheets are full
 *    of child and sibling selectors that an extra box would break, and never
 *    onto a hand-guessed selector, which missed the hamburger bar and painted
 *    it across every desktop page. */
/* Specificity matters here, not just !important. Duda styles these widgets
 * through selectors like `#dm .dmBody div.u_<id>` (1,2,1) carrying their own
 * !important, so a bare `.marker { display: none !important }` (0,1,0) loses
 * and the hidden variant keeps its box. Each override is written to outweigh
 * that shape. */
@media (max-width: 767px) {
  #dm .dmBody div.gy-chrome-d.gy-chrome-d,
  .gy-chrome-d.gy-chrome-d {
    display: none !important;
  }
}
@media (min-width: 768px) {
  #dm .dmBody div.gy-chrome-m.gy-chrome-m,
  .gy-chrome-m.gy-chrome-m {
    display: none !important;
  }
}

/* 1b. Photo galleries are laid out by Duda's runtime per device — 5 columns
 *     on desktop/tablet, 2 on a phone — so the phone tree has MORE ROWS, not
 *     just different attributes, and no attribute patch can express that.
 *     Both variants ship and the media query picks one. Desktop and tablet
 *     galleries are byte-identical on this site, so two variants suffice. */
@media (max-width: 767px) {
  #dm .dmBody div.gy-only-dt.gy-only-dt,
  .gy-only-dt.gy-only-dt {
    display: none !important;
  }
}
@media (min-width: 768px) {
  #dm .dmBody div.gy-only-m.gy-only-m,
  .gy-only-m.gy-only-m {
    display: none !important;
  }
}

/* 2. Parallax is frozen by Duda's RUNTIME on touch, not by its CSS. At 768 the
 *    live document computes background-attachment: scroll even though three
 *    !important rules declare it fixed. Without the runtime the ported rules
 *    win, the background attaches to the viewport, and a full-page capture
 *    renders the hero at roughly 3x zoom.
 *    Duda ships two spellings of the same idea, so both are matched, and the
 *    selector needs enough specificity to beat #dm .dmBody div.u_<id>. */
@media (max-width: 1024px) {
  #dm .dmBody div.dmSectionParallaxNew,
  #dm .dmBody div.dmSectionParallex,
  #dm .dmBody div[class*='dmSectionParallax'],
  #dm .dmBody div[class*='dmSectionParallex'] {
    background-attachment: scroll !important;
  }
}

/* 3. Honeypot. Off-screen rather than display:none — bots skip obviously
 *    hidden fields, and taking it out of flow means it costs no layout, which
 *    the pixel gate would otherwise measure as a difference. */
.gy-hp {
  position: absolute !important;
  left: -9999px !important;
  top: auto !important;
  width: 1px !important;
  height: 1px !important;
  overflow: hidden !important;
}

/* 4. reCAPTCHA is removed rather than reserved (its keys are Duda's and
 *    domain-restricted). Close the gap its container left behind so the form
 *    reads naturally. */
.dmform-recaptcha,
.dmforminput.recaptcha {
  display: none !important;
}

/* 5. The drawer's open state. Duda's rule keys off the `open` attribute; this
 *    only restores the transition and the overlay, which lived in the runtime. */
.layout-drawer-overlay {
  opacity: 0;
  pointer-events: none;
  transition: opacity 0.2s ease;
}
.layout-drawer-overlay.is-open {
  opacity: 1;
  pointer-events: auto;
}