/* Why: press-only copies of the featuring page's media rules, loaded after
   press.css. The featuring page keeps its own inline copies and never loads
   this file. */

/* Why: mobile Safari's pull-to-refresh reloads the page and restarts the hero
   video mid-listen. The landing page turns it off the same way
   (styles/landing.css sets overscroll-behavior: none on html). */
html {
  overscroll-behavior-y: none;
}

.kicker {
  display: inline-block;
  margin: 0 0 12px;
  padding: 4px 12px;
  border-radius: 999px;
  background: var(--yellow);
  border: 2px solid var(--navy);
  font-size: 14px;
  font-weight: 700;
  line-height: 1.4;
}

/* Why: every phone picture and clip carries Apple's own device frame drawn
   into the image on the background of the section it sits in (the page's
   cream, or the Thanksgiving card's peach for the tree). Apple's rules for
   its frames are upright, untilted and no shadows, so the box draws nothing
   of its own: no outline, no rounded clipping, no offset shadow. The ratio matches the 600 x 1225
   framed iPhone stills; the clips are one pixel taller and contain keeps them
   whole, so every phone in a row is the same height and nothing is cropped. */
.phone {
  position: relative;
  aspect-ratio: 600 / 1225;
  background: var(--cream);
}
.phone img,
.phone video {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: contain;
}

/* Why: the button straddles the bottom edge of the device, below the screen,
   so it is easy to find but never covers the record button, the card, or the
   transcript inside the recording. */
.sound {
  position: absolute;
  left: 50%;
  bottom: -26px;
  transform: translateX(-50%);
  display: inline-flex;
  align-items: center;
  gap: 8px;
  min-height: 48px;
  padding: 10px 18px 10px 14px;
  border: 3px solid var(--navy);
  border-radius: 999px;
  /* Why: white, not yellow, so the pill doesn't read as the app's own yellow
     tab bar showing in the recording just above it. */
  background: #fff;
  color: var(--navy);
  font: inherit;
  font-size: 16px;
  font-weight: 700;
  white-space: nowrap;
  cursor: pointer;
  box-shadow: 0 4px 0 var(--navy);
}
.sound:active { transform: translate(-50%, 2px); box-shadow: 0 2px 0 var(--navy); }
.sound svg { width: 24px; height: 24px; flex: none; }
.sound .icon-on { display: none; }
.sound[aria-pressed="true"] .icon-on { display: block; }

/* Why: some browsers block autoplay (Safari's Never Auto-Play, Low Power
   Mode) and reduced motion holds the clip on its poster, so a big play button
   sits over the clip whenever it is paused. It sits at the middle of the
   clip. */
.play {
  position: absolute;
  left: 50%;
  top: 50%;
  transform: translate(-50%, -50%);
  width: 72px;
  height: 72px;
  display: grid;
  place-items: center;
  padding: 0;
  border: 3px solid #373A60;
  border-radius: 50%;
  background: #fff;
  color: #373A60;
  cursor: pointer;
  box-shadow: 0 6px 18px rgba(55, 58, 96, 0.28);
}
.play[hidden] { display: none; }
.play:active { transform: translate(-50%, -50%) scale(0.96); }
/* Why: the play path is already drawn right of center in its 24-unit
   viewBox, which is the optical offset a play triangle needs, so the svg must
   not be shifted again or the triangle looks pushed right. */
.play svg { width: 34px; height: 34px; }
.sound[aria-pressed="true"] .icon-off { display: none; }
/* Why: each tile clip is its own pause control (no always-visible button), so
   it needs a visible focus ring, drawn just outside the clip's box. */
.lazy-clip { cursor: pointer; }
.lazy-clip:focus-visible, #hero-video:focus-visible { outline: 3px solid var(--navy); outline-offset: 4px; }
/* Why: with JavaScript off the empty video still fills the box, so the
   noscript poster would stack below it and push the phone taller. Laying it
   over the box (.phone is position: relative) keeps the phone's size. */
.phone img.clip-fallback { position: absolute; inset: 0; }

.shot {
  position: relative;
  margin: 0 auto;
  width: 100%;
  max-width: 260px;
}

.steps {
  list-style: none;
  padding: 0;
  margin: 24px 0 0;
  display: grid;
  gap: 40px;
}
@media (min-width: 720px) {
  .steps { grid-template-columns: repeat(3, 1fr); gap: 32px; }
}
.steps .phone {
  max-width: 260px;
  margin: 0 auto 20px;
}
.steps h3 { margin-top: 0; }
.steps p { margin: 0; }

.highlight {
  margin: 40px 0 0;
  padding: 18px 20px;
  background: var(--yellow);
  border: 2px solid var(--navy);
  border-radius: 18px;
  font-size: 1.05em;
}

/* ---------- ready for thanksgiving ---------- */

.thanks {
  background: #FFE7D4;
  border: 3px solid var(--navy);
  border-radius: 24px;
  padding: 28px 18px;
}
@media (min-width: 720px) {
  .thanks { padding: 40px 40px 32px; }
}

/* Why: drawn like the app's own question card (blue card, navy outline, a
   pink card peeking out behind) but with no buttons or phone frame, so it
   reads as an illustration of the questions, not a screenshot. */
.qcards {
  list-style: none;
  padding: 0;
  margin: 24px 0 8px;
  display: grid;
  gap: 28px;
}
@media (min-width: 720px) {
  .qcards { grid-template-columns: 1fr 1fr; gap: 32px; }
}
.qcards li { position: relative; z-index: 0; display: flex; flex-direction: column; }
.qcards .set {
  display: block;
  color: var(--muted);
  font-size: 14px;
  font-weight: 700;
  margin: 0 0 8px;
}
.qcard {
  position: relative;
  flex: 1;
  margin: 0 10px 10px 0;
  min-height: 150px;
  padding: 24px 22px;
  background: #98CDFF;
  border: 3px solid #373A60;
  border-radius: 28px;
}
.qcard::before {
  content: "";
  position: absolute;
  z-index: -1;
  inset: 0;
  transform: translate(10px, 10px);
  background: #FDBBE9;
  border: 3px solid #373A60;
  border-radius: 28px;
  margin: -3px;
}
.qcard p {
  margin: 0;
  font-family: "Momo Trust Display", Georgia, serif;
  font-weight: 400;
  font-size: 1.45rem;
  line-height: 1.25;
  color: #373A60;
}

/* Why: below 720px the hero keeps its phone sizes; from 720px it takes the
   featuring page's hero values so the two pages match side by side. 600 / 836
   is the closed-Duo clip. */
.press-hero { display: grid; gap: 28px; margin-top: 28px; }
.press-hero h1 {
  font-family: "Momo Trust Display", Georgia, serif;
  font-weight: 400;
  font-size: clamp(1.9rem, 6.4vw, 2.2rem);
  line-height: 1.15;
  margin: 0 0 14px;
}
.press-hero .sub { margin: 0 0 12px; }
.press-hero .hero-links { margin: 0; }
.hero-media { margin: 0 auto; width: 100%; max-width: 300px; }
.hero-media .phone { aspect-ratio: 600 / 836; }
.hero-media figcaption { margin-top: 44px; color: var(--muted); font-size: 15px; }
.hero-media figcaption q { font-weight: 700; color: var(--navy); }
@media (min-width: 720px) {
  .press-hero h1 { font-size: clamp(2rem, 7.4vw, 3.2rem); line-height: 1.12; margin: 0 0 16px; }
  .press-hero .sub { font-size: 1.12em; margin: 0 0 18px; max-width: 34em; }
  .hero-media { max-width: 340px; }
}
/* Why: on laptop-height screens the device, sound pill included, should fit
   in the viewport height, so it shrinks with that height. The budget is the
   sky band, the hero's 24px top margin, the pill's 30px overhang and 24px of
   room, turned into a width by the 600 / 836 clip. The caption below the
   device is not in the budget, so it may sit below the fold. */
@media (min-width: 820px) {
  .press-hero { grid-template-columns: 1.4fr 1fr; gap: 48px; margin-top: 24px; align-items: center; }
  .hero-media { max-width: clamp(240px, calc((100vh - var(--sky-h) - 78px) * 600 / 836), 380px); }
}
@supports (height: 1svh) {
  @media (min-width: 820px) {
    .hero-media { max-width: clamp(240px, calc((100svh - var(--sky-h) - 78px) * 600 / 836), 380px); }
  }
}
.steps h3 {
  font-family: "Momo Trust Display", Georgia, serif;
  font-weight: 400;
  font-size: 1.25rem;
  line-height: 1.25;
  margin: 0 0 6px;
}
/* Why: from 720px the step headings take the featuring page's size. This
   block must stay after the base .steps h3 rule: equal specificity, so
   source order decides. */
@media (min-width: 720px) {
  .steps h3 { font-size: 1.35rem; margin: 0 0 8px; }
}
.section.thanks { margin-top: 48px; }
.thanks h2 { margin-top: 0; }
/* Why: the tree clip sits beside its text from 720px and above it on a
   phone, at the same 260px cap as every other phone on the page. */
.tree { display: grid; gap: 20px; margin-top: 28px; }
.tree h3 {
  font-family: "Momo Trust Display", Georgia, serif;
  font-weight: 400;
  font-size: 1.3rem;
  margin: 0 0 8px;
}
.tree p { margin: 0; }
@media (min-width: 720px) {
  .tree { grid-template-columns: 200px minmax(0, 1fr); gap: 28px; align-items: center; }
}
/* Why: the surprise and taps clips sit on the page background right under the
   New in 1.0 card, not inside it, because their cream frames would show as a
   box on the white card. Two across from 720px at the page's 260px phone
   size, stacked at that cap on a phone. */
.clip-pair { list-style: none; padding: 0; margin: 40px 0 0; display: grid; gap: 32px; }
.clip-pair figcaption { margin-top: 12px; color: var(--muted); font-size: 15px; text-align: center; }
@media (min-width: 720px) {
  .clip-pair { grid-template-columns: repeat(2, minmax(0, 260px)); justify-content: center; gap: 48px; }
}

/* Why: the tree clip's frame is rendered on the card's peach, so the box
   behind it must be the same peach or a cream edge shows before the poster
   loads and along the clip's one extra pixel row. */
.thanks .phone { background: #FFE7D4; }

.launch-line {
  margin: 0 0 20px;
  font-weight: 700;
  max-width: 34em;
}

/* Why: the downloads are a plain list, one row per file, ruled like the
   fact sheet; the clips themselves already play higher up the page. */
.file-list {
  list-style: none;
  padding: 0;
  margin: 12px 0 0;
  max-width: var(--measure);
  border-bottom: 1px solid rgba(55, 58, 96, 0.14);
}
/* Why: the Download link keeps its own column at the right, so on a phone
   the name and its meta wrap beside it instead of pushing it to a new line. */
.file-list li {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  align-items: center;
  column-gap: 16px;
  border-top: 1px solid rgba(55, 58, 96, 0.14);
}
.file-name { margin: 0; padding: 8px 0; font-weight: 600; }
@media (min-width: 560px) {
  .file-name .meta { display: inline; margin-left: 8px; }
}

/* ---------- wide column ---------- */

/* Why: press.css holds the whole column to a 62ch reading measure, which
   left the hero, phones and download grids much smaller than on the
   featuring page. The column widens to the featuring page's 1080px and the
   running text below keeps the measure inside it. Below 720px the column is
   already narrower than either cap, so phones keep press.css's gutters. */
.wrap { max-width: 1080px; }
@media (min-width: 720px) {
  .wrap { padding: 0 32px 40px; }
  .footer { margin-top: 24px; }
}

.section > p:not(.highlight),
.intro-note,
.features,
.tree-text,
.facts { max-width: var(--measure); }
.about-panel { max-width: calc(var(--measure) + 36px); }

/* Why: from 820px the story sits on the featuring page's story grid (text
   wider than the photos), so its lines stay near the measure while the
   photos keep a sensible size. */
@media (min-width: 820px) {
  .story { grid-template-columns: minmax(0, 1.5fr) minmax(0, 1fr); column-gap: 40px; }
}

/* Why: in the wide column three tiles across would make each screenshot
   taller than a How it works phone, so from 960px every grid takes four
   columns, keeping the tiles near the 260px phones and the grids lined up. */
@media (min-width: 960px) {
  .cards { grid-template-columns: repeat(4, 1fr); }
}

/* Why: from 720px the top-level sections take the featuring page's 88px gap
   and 2rem headings, with the heading's own top margin dropped so the gap is
   the whole space between sections. Sections inside the kit keep their
   smaller step. This block must stay last: it overrides equal-specificity
   rules above and in press.css by source order. */
@media (min-width: 720px) {
  .wrap > .section,
  .wrap > .story,
  .wrap > .band,
  .band > .section { margin-top: 88px; }
  .band > .section:first-child { margin-top: 0; }
  .band { padding-bottom: 0; }
  .band h2,
  .story h2,
  .section h2 { font-size: 2rem; margin: 0 0 12px; }
}
