/* Shared loading overlay — the single source of truth for the full-page,
   pod-state-aware loading screen used by EVERY streaming viewer: the
   public-link player, the admin viewer, and the share player.

   Why this file exists: the overlay styles used to be duplicated inline in
   each single-file SPA and hand-synced. A one-sided edit (the public-link
   full-page change) silently drifted the surfaces apart. Extracting the
   styles here — linked from each SPA via `<link rel="stylesheet"
   href="../styles/loading-overlay.css">`, the same relative-path pattern the
   shared JS modules use (../scripts/shared/*.js) — makes drift structurally
   impossible: there is now one definition, not three copies.

   Boxed-card treatment: the overlay dims the full viewport, but the
   title/subtitle/spinner sit inside a small bordered card centered on it
   (not flat on the full-bleed page). This mirrors the in-app state panels
   (the base `.card` style each SPA defines) so the loading screen reads as
   one consistent boxed surface across every viewer. */

/* The `hidden` attribute must always win: several elements below set an
   explicit `display` (flex / inline-flex), which would otherwise override the
   attribute's default `display:none` and leave a "hidden" pill/badge visible
   (e.g. a healthy channel-health pill, or a zero-count chat-unread badge). */
[hidden] { display: none !important; }

/* ── RPV2-22 — iOS Safari <16px focus-zoom floor ─────────────────────────────
   Mobile Safari magnifies the WHOLE PAGE when a focusable text-entry control
   (input type text/email/password/number/tel/url/search, textarea, select)
   receives focus with a COMPUTED font-size under 16px, and does NOT restore
   the previous zoom on blur or keyboard close. On a single-page SPA that
   never navigates (player/share), that zoom persists for the rest of the
   session — the reported "too zoomed in, elements out of frame" symptom.
   This is the floor for every text control this stylesheet doesn't already
   have a more specific/later rule for — most notably the <select>
   scripts/shared/registration-form.js renders into the player page's
   registration form, which no shell inline <style> block targets by
   selector at all. It does NOT protect the shells' own <input> elements:
   player/index.html and share/index.html each define a same-specificity
   `input, select, textarea` rule in an inline <style> block that is LINKED
   AFTER this stylesheet in <head>, so at equal specificity that later rule
   wins the cascade regardless of what this rule says — each of those two
   shells carries its own explicit `font-size: 16px` for exactly that reason
   (see the comment there). admin-viewer/index.html defines no
   input/select/textarea at all, so this floor is inert there by design. */
input, select, textarea { font-size: 16px; }

/* ── RPV2-22 hardening — touch-action ─────────────────────────────────────────
   Hardening, not the proven root cause (that's the focus-zoom floor above) —
   there was no `touch-action` declared anywhere under
   services/webserver/public/ before this, leaving iOS Safari's native
   double-tap-to-zoom gesture live on ordinary page chrome.
   `manipulation` (= pan-x pan-y pinch-zoom, i.e. no double-tap-zoom) is safe
   on html/body: it does NOT disable pinch-zoom — the viewport meta in every
   shell deliberately omits user-scalable=no/maximum-scale=1 for
   accessibility (see the viewport comment in each shell's <head>) and this
   rule doesn't touch that axis, it only removes the double-tap gesture.
   #stream (the shared id for the <video> element in all three shells) is
   deliberately excluded from that and pinned to `none` instead:
   scripts/shared/input-channel.js already attaches touchstart/touchmove/
   touchend/touchcancel listeners on the video with `{ passive: false }` and
   calls preventDefault() on every one, forwarding raw touch coordinates to
   the game — the video's touch gestures are already fully consumed by the
   app, so `none` here only declares that to the browser's gesture
   recognizer up front and changes no observed input behavior. */
html, body { touch-action: manipulation; }
#stream { touch-action: none; }

/* ── Viewer stacking order — the z-index ledger (RPV2-107) ───────────────────
   Every fixed/absolute overlay in the three viewer shells is appended to
   <body> and nothing on the page creates a stacking context above it (no
   `isolation`, `filter`, `will-change`, `contain` or positioned+z-indexed
   ancestor exists anywhere under services/webserver/public/ — `#stage` and
   `#stream` are both `z-index: auto`). So these values are all compared in the
   ONE root stacking context and this flat ledger is the whole truth:

     (auto)  #stage / #stream / .rp-canvas-presenter   the picture
       4     .rp-url-anchor-layer                      game-authored links  ← below
       5     #loading-overlay · admin #terminated / #pre-error
      10     #status · #channel-health · #connection-quality.cq-standalone
      11     #chat-panel · admin #show-overlay
      12     .rp-fullscreen-btn / -dismiss / -hint
      18     share #toast-stack
      20     player+share #reconnect-banner
      21     .rp-unmute-pill  (the sound control)
      22     .rp-resume-pill  ("Tap to resume", RPV2-120 — over the reconnect overlay)
      30     share #menu-bar
      31     share #menu-toggle
      32     .cq-tip · share .viewer-roster
      33     .cq-detail
      40     share #qr-modal

   THE INVARIANT: the anchor layer sits ABOVE the media element and BELOW every
   piece of SPA chrome. A `request_url_anchor` rect is authored by the streamed
   game against its own screen; the SPA's own controls are not the game's to
   cover. `.rp-url-anchor` children are transparent and `pointer-events: auto`,
   so a layer that out-ranks a control does not merely paint over it — it
   silently STEALS the tap, with nothing on screen to explain why.

   WHY THIS RULE IS HERE AND NOT IN JAVASCRIPT: it used to be
   `container.style.zIndex = '30'` in url-anchor-overlay.js, and 30 out-ranked
   the "Tap for sound" pill (21). A viewer aiming at the pill on any title with
   a bottom banner anchor (Sleep_Apnea, measured 2026-09-22) hit the invisible
   anchor instead and the ad opened in a new tab. `d8beb177` had moved the pill
   INTO that strip after enumerating its neighbours — but it enumerated this
   stylesheet, and the colliding value was in JS, invisible both to that survey
   and to unmute-shell-parity.test.ts, which pins the pill's stacking by parsing
   CSS. 30 also tied share's `#menu-bar`, where DOM order put the anchor layer
   on top of the hamburger menu's own controls. One number, one place, one test
   (`url-anchor-overlay.test.ts` → "z-index ledger"): never set a viewer
   overlay's z-index from JavaScript again.

   4 = the highest value still under `#loading-overlay` (5), so an anchor is
   never clickable through the loading / reconnecting / session-ended screens.
   (`#rp35-canvas`, the `?rp35=1` dev-only experiment canvas, also sits at 5 and
   would occlude anchors while armed — deliberate: it is a measurement rig, not
   a viewer surface.) */
.rp-url-anchor-layer {
  z-index: 4;
}

#loading-overlay {
  position: fixed;
  inset: 0;
  z-index: 5;
  display: none;
  place-items: center;
  padding: 32px;
  /* Mobile-safe: this is a position:fixed (genuinely fixed-height) overlay, so
     a card taller than the visible viewport — e.g. a long loading subtitle or a
     loading image on a very short / landscape phone — can't be reached by
     scrolling the document. Make the overlay itself scrollable; the card's
     auto margins (below) keep it centred when it fits and flush to the
     scrollable top (not clipped) when it overflows. */
  overflow-y: auto;
  -webkit-overflow-scrolling: touch;
  /* Cosmic "Deep Space Data" page backdrop — matches the dashboard's body
     gradient (services/dashboard/src/index.css) so every streaming surface
     shares one void-to-deep-space look instead of a flat fill. */
  background: radial-gradient(ellipse at center, #0f172a 0%, #020408 100%) #020408 fixed;
}
#loading-overlay.visible {
  display: grid;
}
/* Cosmic vignette — deepens the edges for depth (mirrors the dashboard's
   .cosmic-vignette layer). Sits behind the centered card (given position +
   z-index below) and never intercepts pointer events. */
#loading-overlay::after {
  content: "";
  position: fixed;
  inset: 0;
  background: radial-gradient(transparent 40%, #020408 100%);
  pointer-events: none;
}

/* The .card holds the title/subtitle/spinner inside a bordered box
   (background + border + radius + padding) centered on the dimmed overlay,
   matching the in-app state panels' `.card` look. */
#loading-overlay .card {
  width: 100%;
  max-width: 480px;
  background: rgba(5, 11, 20, .9);
  border: 1px solid rgba(148, 163, 184, .3);
  border-radius: 12px;
  padding: 32px;
  text-align: center;
  /* Auto margins center the card in the grid when there's room, but collapse
     to 0 on overflow so an over-tall card sits flush to the (now scrollable)
     top instead of being clipped — see the overflow-y note on #loading-overlay. */
  margin: auto;
  /* Stack above the cosmic ::after vignette. */
  position: relative;
  z-index: 1;
}
#loading-overlay h1 {
  margin: 0 0 12px 0;
  font-size: 22px;
  color: #CDDE00;
}
/* Branded title (R-P0-2): the operator's loading_text (the operator branding
   route caps it at 200 bytes) replaces the constant "Loading" in the h1;
   createLoadingController toggles the class, and only the public-link player
   ever sets it. Smaller than the constant title and allowed to break anywhere,
   so a 200-character sentence fits a phone in both orientations without the
   overlay scrolling (390x844 and 844x390, no loading image; pinned by
   e2e/player.spec.ts). Specificity (1,1,1) out-ranks `#loading-overlay h1`
   (1,0,1) whatever the source order. */
#loading-overlay h1.is-branded {
  font-size: 18px;
  line-height: 1.25;
  overflow-wrap: anywhere;
  word-break: break-word; /* older WebKit without overflow-wrap: anywhere */
}
#loading-overlay p {
  margin: 8px 0;
  color: #94A3B8;
  line-height: 1.5;
  font-size: 14px;
}

/* Self-contained spinner so a SPA linking this file gets a working overlay
   without depending on its own inline spinner CSS. The keyframe name is
   namespaced (rp-loading-spin) so it never collides with a SPA's own
   `@keyframes spin` used by other spinners. */
#loading-overlay .spinner {
  width: 48px;
  height: 48px;
  margin: 16px auto 0;
  border: 3px solid rgba(205, 222, 0, .15);
  border-top-color: #CDDE00;
  border-radius: 50%;
  animation: rp-loading-spin .9s linear infinite;
}
@keyframes rp-loading-spin {
  to { transform: rotate(360deg); }
}

/* Start-up progress bar (R-P0-4): four milestone segments under the subtitle,
   built and driven by scripts/shared/loading-progress.js through
   createLoadingController. Track and fill reuse the spinner's two values
   (its ring and its arc), so the card gains no new hue. It lives INSIDE
   .card: no new stacking layer, no z-index set from JavaScript (see the
   z-index ledger at the top of this file). The global `[hidden]` rule above
   hides it until the controller shows it. */
#loading-overlay .rp-progress {
  display: flex;
  gap: 4px;
  width: 100%;
  max-width: 320px;
  height: 6px;
  margin: 14px auto 0;
}
#loading-overlay .rp-progress-seg {
  flex: 1 1 0;
  height: 100%;
  border-radius: 3px;
  background: rgba(205, 222, 0, .15);
  overflow: hidden;
}
#loading-overlay .rp-progress-fill {
  display: block;
  height: 100%;
  width: 0;
  background: #CDDE00;
  border-radius: inherit;
  /* The controller writes the width about four times a second (TICK_MS);
     the transition smooths the steps between writes. */
  transition: width 260ms linear;
}
@media (prefers-reduced-motion: reduce) {
  /* Static segments: loading-progress.js draws no growth under reduced
     motion, and the spinner (which had no guard before R-P0-4) stops too. */
  #loading-overlay .rp-progress-fill { transition: none; }
  #loading-overlay .spinner { animation: none; }
}

/* ── Live channel-health badge ──────────────────────────────────────────
   Small always-on Input/Audio pills over the stream (top-right, clear of the
   top-left ?debug diagnostics panel). Built by scripts/shared/channel-health.js
   and shared by the player + share viewers. Calm when healthy; the dot PULSES
   when a channel is connecting/recovering/failed so a mid-session drop is easy
   to spot. Palette matches the diagnostics panel (.ok/.warn/.err). */
#channel-health {
  position: fixed;
  top: 12px;
  right: 12px;
  z-index: 10;
  display: flex;
  gap: 8px;
  pointer-events: none; /* never intercepts game input */
  font: 11px/1 ui-monospace, SFMono-Regular, Menlo, monospace;
}
#channel-health[hidden] { display: none; }
.ch-pill {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 4px 8px;
  border-radius: 8px;
  background: rgba(5, 11, 20, .75);
  border: 1px solid rgba(148, 163, 184, .5);
  color: #94A3B8;
  letter-spacing: .02em;
}
.ch-dot {
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: currentColor;
  flex: none;
}
/* Levels — color the dot + label via currentColor. */
.ch-idle { color: #94A3B8; opacity: .55; }
.ch-ok   { color: #CDDE00; }
.ch-warn { color: #BC4700; border-color: rgba(188, 71, 0, .65); }
.ch-err  { color: #9F1239; border-color: rgba(159, 18, 57, .8); }
/* Pulse: an expanding ring + dimming so a degraded channel draws the eye. */
.ch-pulse .ch-dot { animation: ch-pulse 1.1s ease-in-out infinite; }
@keyframes ch-pulse {
  0%   { box-shadow: 0 0 0 0 currentColor; opacity: 1; }
  70%  { box-shadow: 0 0 0 6px transparent; opacity: .45; }
  100% { box-shadow: 0 0 0 0 transparent; opacity: 1; }
}
@media (prefers-reduced-motion: reduce) {
  .ch-pulse .ch-dot { animation: none; }
  .ch-pulse { outline: 1px solid currentColor; } /* still distinguishable */
}

/* ── Connection-quality indicator ────────────────────────────────────────
   A network-quality pill (Good / Fair / Poor) built by
   scripts/shared/connection-quality.js and shared by all three streaming
   viewers. Distinct from channel-health (input/audio) — this rates the
   NETWORK path (RTT / loss / fps) from the 1 Hz getStats sample. Unlike the
   channel pills it is always-on (the user asked to SEE connection health),
   so it has no pulse/hide behaviour. The share viewer drops `.el` into its
   top-bar menu; the player + admin viewers pin it top-left (clear of the
   top-right channel-health badge) via the wrapper below. Palette matches the
   diagnostics panel (.ok/.warn/.err). */
.cq-pill {
  position: relative;            /* anchor for the hover tip + expand panel */
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 4px 8px;
  border-radius: 8px;
  background: rgba(5, 11, 20, .75);
  border: 1px solid rgba(148, 163, 184, .5);
  color: #94A3B8;
  font: 11px/1 ui-monospace, SFMono-Regular, Menlo, monospace;
  letter-spacing: .02em;
  white-space: nowrap;
  cursor: pointer;
  user-select: none;
}
.cq-pill:focus-visible { outline: 2px solid #CDDE00; outline-offset: 2px; }
/* viewer_popups_enabled: a hidden pill leaves layout entirely (the author
   `display: inline-flex` above would otherwise beat the UA [hidden] rule). */
.cq-pill[hidden] { display: none; }

/* Custom hover tooltip — replaces the native `title` (whose per-tick
   re-assignment made the tooltip flicker). Shown purely by CSS :hover/:focus
   when NOT expanded; its text is updated in place so it never blinks. */
.cq-tip {
  position: absolute;
  top: calc(100% + 6px);
  left: 0;
  z-index: 32;
  display: none;
  white-space: nowrap;
  background: rgba(5, 11, 20, .97);
  border: 1px solid rgba(148, 163, 184, .5);
  border-radius: 6px;
  padding: 4px 8px;
  color: #fff;
  pointer-events: none;          /* the tip itself never intercepts */
}
.cq-pill:hover:not(.cq-open) .cq-tip,
.cq-pill:focus-visible:not(.cq-open) .cq-tip { display: block; }

/* Click-to-expand in-depth panel. Shown while the pill carries .cq-open
   (toggled on click/Enter/Space). A grid of metric rows updated live. */
.cq-detail {
  position: absolute;
  top: calc(100% + 6px);
  left: 0;
  z-index: 33;
  display: none;
  min-width: 208px;
  background: rgba(5, 11, 20, .98);
  border: 1px solid rgba(148, 163, 184, .5);
  border-radius: 8px;
  padding: 8px 10px;
  box-shadow: 0 8px 28px rgba(2, 4, 8, .55);
  cursor: default;
}
.cq-pill.cq-open .cq-detail { display: block; }
.cq-row { display: flex; justify-content: space-between; gap: 16px; padding: 2px 0; }
.cq-k { color: #94A3B8; }
.cq-v { color: #fff; }
/* Visually-hidden live region — carries the spoken "Connection poor" etc. on a
   level change without occupying layout (standard sr-only clip). */
.cq-live {
  position: absolute;
  width: 1px; height: 1px;
  margin: -1px; padding: 0; border: 0;
  overflow: hidden; clip: rect(0 0 0 0); clip-path: inset(50%);
  white-space: nowrap;
}
.cq-dot {
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: currentColor;
  flex: none;
}
.cq-unknown { color: #94A3B8; opacity: .6; }
.cq-good    { color: #CDDE00; }
.cq-fair    { color: #BC4700; border-color: rgba(188, 71, 0, .65); }
.cq-poor    { color: #9F1239; border-color: rgba(159, 18, 57, .8); }
/* The .cq-label text IS the readable signal (the dot is decorative). The
   saturated brand reds (#BC4700 / #9F1239) fail WCAG AA contrast on the dark
   pill, so brighten the LABEL text to clear 4.5:1 while the dot + border keep
   the brand color via currentColor. */
.cq-fair .cq-label { color: #F59E0B; }
.cq-poor .cq-label { color: #F87171; }
/* Stalled — no new frames are arriving. Deliberately NOT styled as a worse
   shade of Poor: Poor means "degraded but playing", stalled means "stopped",
   and an operator scanning a wall of these needs to tell those apart at a
   glance, not by reading. Brighter and fully saturated so it separates from
   the crimson Poor; label at #FCA5A5 measures ~10.3:1 on the pill's
   rgba(5,11,20,.98), clearing AA with room to spare (the saturated border
   colour would not, which is why the label carries the readable signal here
   exactly as it does for fair/poor above). */
.cq-stalled { color: #DC2626; border-color: rgba(220, 38, 38, .95); }
.cq-stalled .cq-label { color: #FCA5A5; }

/* Standalone placement for the player + admin viewers (the share viewer
   instead nests the pill inside its top-bar menu, so it doesn't use this).
   Top-LEFT so it never collides with the top-right channel-health badge; the
   ?debug #status panel is also top-left but hidden in normal play. */
#connection-quality.cq-standalone {
  position: fixed;
  top: 12px;
  left: 12px;
  z-index: 10;
  pointer-events: none; /* never intercepts game input */
}

/* ── "Tap for sound" pill (RPV2-38) ──────────────────────────────────────────
   Built by scripts/shared/unmute-control.js — never by a shell — so all three
   viewers (player, share, admin viewer) get an identical affordance. Shown
   whenever the stream is playing muted with a live audio track, including an
   operator `mute_audio_on_start` session (which arms no gesture listeners at
   all; the pill is its ONLY way to sound).

   BOTTOM-CENTRE, deliberately. It shipped top-centre first, and a live run on
   Brukinsa (2026-09-11) showed the pill lying across the game's own IMPORTANT
   SAFETY INFORMATION header — regulated content that has to stay readable, so
   the top band is not ours to borrow even briefly. The bottom strip is the
   already-accepted overlay zone (.rp-fullscreen-hint lives there) and covers a
   game's branding footer instead.

   Neighbours in that strip: bottom-left .rp-fullscreen-btn (a real control —
   the max-width below is what keeps a centred pill off it on a narrow phone),
   bottom-centre .rp-fullscreen-hint (the pill lifts above it when it is up,
   and takes its slot when it is not), bottom-right the share #toast-stack
   (pointer-events: none, and it paints under us). Nothing else is down here:
   #status / #connection-quality.cq-standalone are top-left, #channel-health
   top-right, share's #menu-toggle top-right, #chat-panel the right edge, and
   player/share's #reconnect-banner is top-anchored — see the stacking note
   after this block, since that one is declared in those shells' inline
   <style>, not here, which is exactly why a survey of this file alone missed
   it the first time.

   Same visual recipe as .ch-pill so it reads as part of the same overlay
   family, but `pointer-events: auto` (unlike the read-only pills) because it is
   a real button — and that is exactly why it must never sit over the video's
   interactive middle. */
.rp-unmute-pill {
  position: fixed;
  bottom: calc(12px + env(safe-area-inset-bottom, 0px));
  left: 50%;
  max-width: 200px;
  transform: translateX(-50%);
  z-index: 21;
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 6px 10px;
  border-radius: 8px;
  background: rgba(5, 11, 20, .75);
  border: 1px solid rgba(148, 163, 184, .5);
  color: #CDDE00;
  font: 11px/1 ui-monospace, SFMono-Regular, Menlo, monospace;
  letter-spacing: .02em;
  pointer-events: auto;
  cursor: pointer;
}
.rp-unmute-pill[hidden] { display: none; }
.rp-unmute-pill svg {
  width: 14px;
  height: 14px;
  flex: none;
}
.rp-unmute-pill:focus-visible {
  outline: 2px solid #CDDE00;
  outline-offset: 2px;
}
/* Lift the pill clear of the fullscreen hint while the hint is on screen, and
   let it drop back into the hint's own slot once the hint is gone (dismissed,
   retired, or never shown off-iOS).

   60px = the hint's 12px bottom offset + its REAL one-line box (40px) + an 8px
   gap. The box is 40px, not the "~34px" this rule was first derived from: the
   ✕ (.rp-fullscreen-hint-close, 22px) is the tallest item on the line, so the
   height is 8px + 22px + 8px padding + 2px border, not 8 + 15.6 (one 12px/1.3
   text line) + 8 + 2. And the hint IS one line now (RPV2-112) — while
   `left: 50%` halved its width it was three lines (64.8px tall) and the 54px
   lift left the pill sitting on the hint's top 22.8px. unmute-shell-parity.
   test.ts derives the box from the rules below and holds this value to it.

   Keyed with :has() on a common ancestor rather than a sibling combinator on
   purpose. Both elements are appended to <body>, but by DIFFERENT modules, and
   the append order genuinely differs per shell — player and admin viewer arm
   unmute at module load (pill first, hint later), while share arms it late
   inside startStreaming (hint first, pill later). A `~` rule would therefore
   work on exactly one surface and silently not on the other two, which is the
   drift this repo keeps re-learning. The sibling form is kept alongside as a
   fallback for an engine without :has(); there the worst case is the pill
   resting on the hint, still clickable (z-index 21 vs the hint's 12).

   The pill is a BUTTON, so stacking order is not cosmetic — painted under an
   opaque overlay it is also UNCLICKABLE. z-index 21 clears the hint (12) and
   is deliberately kept above player/share's `#reconnect-banner` (z-index 20,
   declared in those shells' inline <style>) even though that banner is
   top-anchored and no longer shares this strip: belt and braces if a shell
   later moves or grows it. The shell-parity vitest pins both comparisons.

   RPV2-121: not when the call to action sits in a SIDE letterbox band — it is
   vertically centred there, nowhere near the hint, and a `bottom` from this
   rule next to that placement's `top` would stretch the element. */
:has(.rp-fullscreen-hint:not([hidden])) .rp-unmute-pill:not([data-place="side"]),
.rp-fullscreen-hint:not([hidden]) ~ .rp-unmute-pill:not([data-place="side"]) {
  bottom: calc(60px + env(safe-area-inset-bottom, 0px));
}

/* ── The sound control's other two states (RPV2-107 / RPV2-108) ──────────────
   ONE element, three presentations, selected by `data-sound` (written by
   unmute-control.js — see its SOUND_STATES / state-machine header):

     policy-muted  the big bottom-centre "Tap for sound" pill above. Unchanged
                   look, unchanged slot, and deliberately NOT faded: it is an
                   unanswered call to action.
     on            small speaker button, the first slot of the bottom-left
                   control row (RPV2-108 round 2, below). "Sound is on — tap
                   to mute."
     user-muted    same button, slashed speaker, slate instead of brand lime.
                   "You muted this — tap to turn it back on."

   Before this the pill hid itself permanently on the first successful unmute,
   so no viewer surface had ANY way back to silence (RPV2-108). 11 of the 32
   streamed titles ship no in-game settings page at all, so on those the viewer
   had no audio control anywhere.

   WHY THE TWO VIEWER-CONTROLLED STATES LEAVE THE CENTRE: the bottom-centre slot
   is a good place for a one-off call to action and a bad place for a permanent
   control — it is the widest part of a game's branding/ISI footer strip, and a
   permanently-parked pill there would cover regulated content on exactly the
   titles that carry it. The bottom-LEFT cluster is already the accepted home
   for persistent viewer chrome (.rp-fullscreen-btn / -dismiss), so the sound
   button joins it: left 86px = the toggle's 12px inset + its 40px + the 6px gap
   + the dismiss ✕'s 22px + another 6px gap. On iOS that cluster is empty (no
   fullscreen button is built there — see fullscreen.js's PLATFORM SPLIT) and
   the sound button keeps the same coordinates anyway, so its position is one
   fact on every platform rather than a per-platform variant to keep in sync.
   The two states never coexist with the centred pill — they are the same
   element — so the `max-width` clearance reasoning for the big pill is
   unaffected.

   RPV2-108 round 2 (2026-09-28): that cluster is now ONE ROW anchored to the
   rendered PICTURE — the sound button first, then the toggle, then its ✕, in
   fixed slots (fullscreen.js CONTROL_ROW_SLOTS: 0 / 46 / 92px). The reporter
   asked for the button "inside the actual game container, with small gaps
   from the bottom and left sides"; pinned to the viewport it straddled the
   picture's bottom edge on her 360x675 Android phone and sat 329px out in
   the black band on a desktop. unmute-control.js measures the picture
   (url-anchor-overlay.js bottomLeftRowAnchor: the left band when it holds the
   row, else the bottom band, else 8px inside the picture's corner) and
   publishes four custom properties on the root element; the rules below and
   the toggle's read them, and each falls back to its pre-anchor slot (86px
   here, 12px and 58px for the toggle and its ✕) whenever nothing is
   published — no geometry yet, or no window to measure. */
.rp-unmute-pill[data-sound="on"],
.rp-unmute-pill[data-sound="user-muted"] {
  left: var(--rp-ctl-row-left, calc(86px + env(safe-area-inset-left, 0px)));
  bottom: var(--rp-ctl-row-bottom, calc(12px + env(safe-area-inset-bottom, 0px)));
  transform: none;
  max-width: none;
  width: 40px;
  height: 40px;
  padding: 0;
  justify-content: center;
  background: rgba(5, 11, 20, .72);
}
/* RPV2-108 round 2: the button's iOS-hint lift. Anchored to the picture, the
   button lifts from its OWN bottom, raised clear of the hint: max(anchored
   bottom, 60px) plus the safe-area inset — the same 60px the call to
   action's lift above uses. At the old slot (12px) that is exactly the
   anchored bottom + 48px; a row that already sits above the hint (in a
   bottom letterbox band) is not moved onto the picture. The same :has()
   rule + sibling fallback as the call to action's, so it holds on all three
   shells whatever order the two modules appended their elements in; it
   comes after that rule at the same specificity, so it wins for the
   button. */
:has(.rp-fullscreen-hint:not([hidden])) .rp-unmute-pill[data-sound="on"],
:has(.rp-fullscreen-hint:not([hidden])) .rp-unmute-pill[data-sound="user-muted"],
.rp-fullscreen-hint:not([hidden]) ~ .rp-unmute-pill[data-sound="on"],
.rp-fullscreen-hint:not([hidden]) ~ .rp-unmute-pill[data-sound="user-muted"] {
  bottom: max(var(--rp-ctl-row-bottom, calc(12px + env(safe-area-inset-bottom, 0px))), calc(60px + env(safe-area-inset-bottom, 0px)));
}
.rp-unmute-pill[data-sound="on"] svg,
.rp-unmute-pill[data-sound="user-muted"] svg {
  width: 20px;
  height: 20px;
}
/* Muted reads as "off" at a glance — the same slate the fullscreen toggle uses
   for its inactive state — while sound-on keeps the brand lime. */
.rp-unmute-pill[data-sound="user-muted"] { color: #94A3B8; }
.rp-unmute-pill[data-sound="on"]:hover,
.rp-unmute-pill[data-sound="user-muted"]:hover {
  background: rgba(15, 23, 42, .95);
  border-color: #CDDE00;
}

/* Idle fade — the RPV2-29 behaviour, on the same 4000ms clock (unmute-control.js
   imports fullscreen.js's IDLE_MS rather than copying the number), and since
   2026-09-24 the same fade as `.rp-fullscreen-btn.is-idle` above: fully out AND
   `pointer-events: none`, woken by the shared bottom-left corner zone or mouse
   motion (unmute-control.js imports isInCornerZone from fullscreen.js).

   This reverses the 2026-09-22 choice (RPV2-107/108) of a 35% fade that stayed
   hit-testable so the only audio control on 11 titles could always be found and
   tapped. The reporter's retest found the always-visible button obscured the
   game, and the fullscreen toggle's behaviour was chosen instead. Accepted with
   it: while faded, a tap where the button was falls through to the game
   (RPV2-107's fall-through, on a control nobody is aiming at), and the button is
   no longer its own wake affordance. The `policy-muted` "Tap for sound" call to
   action is never put on the fade clock at all (unmute-control.js reveal()).

   RPV2-113 (2026-09-24): in an iPhone Safari tab the picture has no letterbox
   band, so this button sits ON the game's bottom row. unmute-control.js
   therefore renders it straight into `.is-idle` after any transition the
   viewer did not make by tapping it (the first-gesture unmute from a tap on
   the game above all), and wakes it from the corner only AFTER the waking
   tap's trailing click — never inside its pointerdown, which is what made a
   corner tap on the button's own spot toggle mute. */
.rp-unmute-pill { transition: opacity .3s ease; }
.rp-unmute-pill.is-idle {
  opacity: 0;
  pointer-events: none;
}
@media (prefers-reduced-motion: reduce) {
  .rp-unmute-pill { transition: none; }
}

/* ── RPV2-121: the call to action never covers or swallows the game ─────────
   unmute-control.js decides where the `policy-muted` prompt goes and writes
   only `data-place`, `data-compact`, `.is-passthrough` and two custom
   properties; everything visual is here. Measured on Cabenuva 1.7.0 (triage
   RPV2-121 §3): with no bottom letterbox band — every iPad and phone browser
   measured — the bottom-centre pill covered 58% of SCROLL DOWN on the
   reporter's iPad and 96–99% of it on phones, plus the CONTINUE buttons, and
   a tap on it never reached the game.

     data-place="side"    a left letterbox band fits it: vertically centred
                          in that band, OFF the picture. The left band, not
                          the right — share's collapsed #chat-panel button is
                          vertically centred on the right edge.
       + data-compact     the band is under the full pill's width + 8px
                          (78–100px on iPad portrait): an icon-over-words tile
                          of PROMPT_COMPACT_WIDTH, the words kept so it cannot
                          read as the slate `user-muted` button.
     data-place="bottom"  the bottom band holds the old slot: unchanged.
     data-place="picture" no band: the old slot, over the picture, and
       .is-passthrough    while a tap on the game can itself turn sound on —
                          a pass-through label (`pointer-events: none`, a
                          tighter box) that fades after IDLE_MS like the other
                          idle-fading chrome; otherwise the old button.

   unmute-shell-parity.test.ts holds unmute-control.js's footprint constants
   (PROMPT_MAX_WIDTH, PROMPT_COMPACT_WIDTH, PROMPT_HEIGHT, the 12px/60px
   offsets) to the values below and to the base rule above. */
.rp-unmute-pill[data-sound="policy-muted"][data-place="side"] {
  left: var(--rp-sound-prompt-x, 50%);
  top: var(--rp-sound-prompt-y, 50%);
  bottom: auto;
  transform: translate(-50%, -50%);
}
.rp-unmute-pill[data-sound="policy-muted"][data-place="side"][data-compact] {
  flex-direction: column;
  gap: 5px;
  width: 64px;
  max-width: 64px;
  padding: 8px 6px;
  line-height: 1.25;
  text-align: center;
}
.rp-unmute-pill[data-sound="policy-muted"][data-place="side"][data-compact] svg {
  width: 18px;
  height: 18px;
}
.rp-unmute-pill[data-sound="policy-muted"].is-passthrough {
  pointer-events: none;
  padding: 4px 8px;
}
/* RPV2-108 round 2: "Tap to resume" (.rp-resume-pill, below) owns the
   bottom-centre slot while it is up. unmute-control.js sets `data-yield` when
   that button overlaps the call to action's slot (lifted or not), and the
   call to action steps out of the way — invisible and inert — until the
   button goes. The resume button is the more urgent action, and its tap is
   itself an activating gesture that turns sound on while a game tap can. */
.rp-unmute-pill[data-sound="policy-muted"][data-yield] {
  visibility: hidden;
  pointer-events: none;
}
/* Reads env(safe-area-inset-*) for unmute-control.js (its computed padding IS
   the four insets): the letterbox bands are measured inside the safe area. */
.rp-sound-safe-area-probe {
  position: fixed;
  top: 0;
  left: 0;
  width: 0;
  height: 0;
  padding: env(safe-area-inset-top, 0px) env(safe-area-inset-right, 0px)
    env(safe-area-inset-bottom, 0px) env(safe-area-inset-left, 0px);
  visibility: hidden;
  pointer-events: none;
}

/* ── "Tap to resume" (RPV2-120) ──────────────────────────────────────────────
   Built hidden by scripts/shared/paint-watchdog.js and shown ONLY when frames
   are being decoded but not presented and the watchdog's own automatic
   re-attach did not bring them back — the last resort, whose click re-attaches
   and plays inside the viewer's gesture. A one-off call to action, never
   permanent chrome, so it takes the viewers' primary-button look (the lime
   `button` of the player/share cards) rather than the sound control's.

   Placement: centred, just BELOW the loading card. On player and share the
   "Reconnecting" overlay is up whenever this is (they hold it until frames are
   presented), and the card is centred and ~200px tall, so 50% + 116px reads as
   the next step under it instead of sitting on its text. The min() keeps it
   on screen above the bottom strip on a short landscape phone: its floor puts
   the button's bottom edge 60px up — which is exactly where the call to
   action's LIFTED slot (above the iOS hint) starts, 60-88px up. So while the
   hint is up on a viewport under ~496px tall (plus twice the safe-area
   inset) the two DO overlap: measured at 667x375 with an iOS UA, the prompt
   was entirely covered. (This comment used to say the lifted slot "ends
   86px up" and that the two "never overlap" — both wrong.) Since RPV2-108
   round 2 they get disjoint slots: while this button is shown and overlaps
   the prompt's slot, the prompt yields
   (`.rp-unmute-pill[data-yield]` above; paint-watchdog.js announces every
   show/hide as `rp:resume-affordance-changed`). On the admin viewer, which
   has no reconnect overlay, it sits over the frozen picture. z-index 22 — the
   ledger above: over the overlay (5), the reconnect banner (20) and the sound
   control (21); under share's menu bar (30). */
.rp-resume-pill {
  position: fixed;
  left: 50%;
  top: min(calc(50% + 116px), calc(100% - 104px - env(safe-area-inset-bottom, 0px)));
  transform: translateX(-50%);
  z-index: 22;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-height: 44px;
  max-width: calc(100vw - 32px);
  padding: 0 20px;
  border: 0;
  border-radius: 6px;
  background: #CDDE00;
  color: #050B14;
  font-family: inherit;
  font-size: 15px;
  font-weight: 600;
  line-height: 1.2;
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
  pointer-events: auto;
  cursor: pointer;
}
.rp-resume-pill[hidden] { display: none; }
.rp-resume-pill:hover { background: #DDEE00; }
.rp-resume-pill:focus-visible {
  outline: 2px solid #fff;
  outline-offset: 2px;
}

/* ── Session chat — right-edge collapsible sidebar ───────────────────────
   Built by scripts/shared/chat-ui.js, shared by the player + share viewers.
   Collapsed: a small chat-icon button pinned to the right edge, vertically
   centered. Open: a full-height sidebar on the right with the connected-users
   roster + scrolling message list + input. Cosmic palette. */
#chat-panel {
  position: fixed;
  right: 0;
  z-index: 11;
  display: flex;
  flex-direction: column;
  background: rgba(5, 11, 20, .92);
  border: 1px solid rgba(148, 163, 184, .45);
  font: 13px/1.4 system-ui, -apple-system, sans-serif;
  color: #fff;
  box-shadow: 0 8px 28px rgba(2, 4, 8, .5);
}
/* Open: full-height sidebar anchored to the right edge (top → bottom).
   overflow stays visible so the edge collapse handle can jut out past the
   left edge; the message list does its own internal scrolling. */
#chat-panel[data-open="true"] {
  top: 0;
  bottom: 0;
  width: 320px;
  max-width: 90vw;
  border-right: 0;
  border-radius: 10px 0 0 10px;
}
/* Edge collapse handle (›) — juts out of the panel's inner (left) edge,
   vertically centered. Click to collapse the sidebar back to the icon. */
.chat-collapse {
  position: absolute;
  left: -22px;
  top: 50%;
  transform: translateY(-50%);
  width: 22px;
  height: 52px;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 0;
  border: 1px solid rgba(148, 163, 184, .45);
  border-right: 0;
  border-radius: 9px 0 0 9px;
  background: rgba(5, 11, 20, .95);
  color: #CDDE00;
  cursor: pointer;
  box-shadow: -4px 0 14px rgba(2, 4, 8, .4);
}
.chat-collapse:hover { background: rgba(15, 23, 42, .98); }
/* Collapsed: no handle (the whole icon button expands it instead). */
#chat-panel[data-open="false"] .chat-collapse { display: none; }
/* Collapsed: a small icon-only button, vertically centered on the right edge. */
#chat-panel[data-open="false"] {
  top: 50%;
  transform: translateY(-50%);
  width: 44px;
  height: 44px;
  border-right: 0;
  border-radius: 10px 0 0 10px;
}
.chat-header {
  display: flex;
  align-items: center;
  gap: 8px;
  width: 100%;
  border: 0;
  background: transparent;
  color: #fff;
  padding: 10px 12px;
  cursor: pointer;
  font: inherit;
  text-align: left;
  flex: none;
}
.chat-icon { display: inline-flex; align-items: center; justify-content: center; color: #CDDE00; flex: none; }
.chat-title { font-weight: 600; color: #CDDE00; }
.chat-count { color: #94A3B8; font-size: 12px; margin-left: auto; }
.chat-unread {
  min-width: 18px;
  height: 18px;
  padding: 0 5px;
  border-radius: 9px;
  background: #CDDE00;
  color: #050B14;
  font-size: 11px;
  font-weight: 700;
  display: inline-flex;
  align-items: center;
  justify-content: center;
}
/* Collapsed: the header fills the small square, centered icon only. */
#chat-panel[data-open="false"] .chat-header {
  height: 100%;
  justify-content: center;
  padding: 0;
  position: relative;
}
#chat-panel[data-open="false"] .chat-title,
#chat-panel[data-open="false"] .chat-count,
#chat-panel[data-open="false"] .chat-body { display: none; }
/* Unread count floats on the icon's corner while collapsed. */
#chat-panel[data-open="false"] .chat-unread {
  position: absolute;
  top: 2px;
  right: 2px;
  min-width: 16px;
  height: 16px;
}
.chat-body {
  display: flex;
  flex-direction: column;
  flex: 1 1 auto;
  min-height: 0;
  border-top: 1px solid rgba(148, 163, 184, .25);
}
.chat-roster {
  display: flex;
  flex-wrap: wrap;
  gap: 4px;
  padding: 8px 12px;
  border-bottom: 1px solid rgba(148, 163, 184, .2);
  max-height: 30%;
  overflow-y: auto;
  flex: none;
}
.chat-chip {
  font-size: 11px;
  color: #94A3B8;
  background: rgba(148, 163, 184, .12);
  border-radius: 6px;
  padding: 2px 6px;
}
.chat-chip-self { color: #CDDE00; background: rgba(205, 222, 0, .12); }
.chat-messages {
  flex: 1 1 auto;
  min-height: 0;
  overflow-y: auto;
  padding: 8px 12px;
  display: flex;
  flex-direction: column;
  gap: 5px;
}
.chat-msg { word-break: break-word; }
.chat-author { color: #94A3B8; font-weight: 600; margin-right: 6px; }
.chat-msg-self .chat-author { color: #CDDE00; }
.chat-text { color: #e2e8f0; }
.chat-input { display: flex; gap: 6px; padding: 8px 12px; border-top: 1px solid rgba(148, 163, 184, .2); flex: none; }
.chat-input input {
  flex: 1;
  min-width: 0;
  background: rgba(15, 23, 42, .9);
  border: 1px solid rgba(148, 163, 184, .4);
  border-radius: 6px;
  color: #fff;
  padding: 6px 8px;
  font: inherit;
  /* RPV2-22: `font: inherit` above pulls in #chat-panel's 13px, so this
     floor must come after it in the same rule — `.chat-input input` is
     already higher-specificity than the plain `input, select, textarea`
     floor above, but that floor's font-size alone would still lose to
     `font: inherit` here without this explicit line. */
  font-size: 16px;
}
.chat-input input:focus { outline: none; border-color: #CDDE00; }
.chat-input button {
  background: #CDDE00;
  color: #050B14;
  border: 0;
  border-radius: 6px;
  padding: 6px 12px;
  font-weight: 600;
  cursor: pointer;
}

/* ── Fullscreen control (scripts/shared/fullscreen.js) ───────────────────────
   Shared by the player + share + admin viewers. Built + toggled in JS; as of
   RPV2-29 the BUTTON exists ONLY on Android Chrome / desktop — ALL iOS (iPhone
   AND iPad) gets the hint below and never the button. iPadOS does expose
   `requestFullscreen`, but its element-fullscreen presentation adds an
   un-styleable swipe-down/✕/PiP bar that re-summons on every tap of the video,
   so it is treated the same as iPhone Safari (no usable fullscreen API) rather
   than as a desktop-class browser. RPV2-29 round 2: nothing available to a web
   page on iOS/iPadOS hides the STATUS bar (clock / Wi-Fi / battery) — Add to
   Home Screen only removes Safari's own bars — so the shells declare
   apple-mobile-web-app-status-bar-style=`black` and lay the page out below it.
   Where it exists, the button hides the
   mobile browser chrome (URL bar) that would otherwise letterbox-occlude the
   top of the stream in landscape.

   Bottom-LEFT so it never collides with the other corner overlays: the
   top-left #status / cq-standalone pill, the top-right channel-health badge /
   share hamburger, the right-edge #chat-panel, or the share bottom-right
   #toast-stack. env() insets keep it clear of the notch / home indicator when
   the chrome is actually gone (fullscreen / iOS landscape).

   Idle fade + dismiss: the button fades to invisible (opacity 0,
   pointer-events none via `.is-idle`) after a period of no interaction and
   comes back from the bottom-left corner zone; the hint never takes a tap at
   all (pointer-events none on everything but its ✕ — RPV2-112) and retires
   for good HINT_RETIRE_MS after it first shows, fading out the same way. Both
   can be dismissed outright — the hint via `.rp-fullscreen-hint-close`
   (remembered in localStorage, see fullscreen.js), the button's row via the
   small `.rp-fullscreen-dismiss` ✕ beside it — and a dismissed or retired one
   stays gone for the rest of the page. The opacity transition is shared so
   the fade reads as one behaviour whichever control is on screen. */
.rp-fullscreen-btn,
.rp-fullscreen-dismiss {
  transition: opacity .3s ease;
}
.rp-fullscreen-btn.is-idle,
.rp-fullscreen-dismiss.is-idle {
  opacity: 0;
  pointer-events: none;
}
@media (prefers-reduced-motion: reduce) {
  .rp-fullscreen-btn,
  .rp-fullscreen-dismiss {
    transition: none;
  }
}
/* RPV2-108 round 2: the toggle is the control row's second slot and its ✕ the
   third (fullscreen.js CONTROL_ROW_SLOTS), placed from the custom properties
   unmute-control.js publishes on the root element when it has measured the
   picture; the fallbacks are the pre-anchor viewport slots. */
.rp-fullscreen-btn {
  position: fixed;
  bottom: var(--rp-ctl-row-bottom, calc(12px + env(safe-area-inset-bottom, 0px)));
  left: var(--rp-ctl-fs-left, calc(12px + env(safe-area-inset-left, 0px)));
  z-index: 12;
  width: 40px;
  height: 40px;
  padding: 0;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  font-size: 20px;
  line-height: 1;
  cursor: pointer;
  color: #CDDE00;
  background: rgba(5, 11, 20, .72);
  border: 1px solid rgba(148, 163, 184, .5);
  border-radius: 8px;
  -webkit-tap-highlight-color: transparent;
}
.rp-fullscreen-btn:hover { background: rgba(15, 23, 42, .95); border-color: #CDDE00; }
.rp-fullscreen-btn.is-fullscreen { color: #94A3B8; }
/* The icon is an inline SVG (fullscreen.js FULLSCREEN_ICON_SVG), not a font
   glyph, so it cannot fall back to a missing-character box on a device font
   that lacks U+26F6. It inherits the button's colour via currentColor. */
.rp-fullscreen-btn svg { width: 20px; height: 20px; display: block; }

/* Small ✕ that sits beside the 40x40 toggle, bottom-left, to dismiss the
   fullscreen control outright without waiting for the idle fade above.
   Fallback left = 58px = the toggle's 12px left inset + its 40px width + 6px
   gap; anchored, it is the row's third slot (RPV2-108 round 2). */
.rp-fullscreen-dismiss {
  position: fixed;
  bottom: var(--rp-ctl-row-bottom, calc(12px + env(safe-area-inset-bottom, 0px)));
  left: var(--rp-ctl-dismiss-left, calc(58px + env(safe-area-inset-left, 0px)));
  z-index: 12;
  width: 22px;
  height: 22px;
  padding: 0;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  font-size: 12px;
  line-height: 1;
  cursor: pointer;
  color: #94A3B8;
  background: rgba(5, 11, 20, .72);
  border: 1px solid rgba(148, 163, 184, .5);
  border-radius: 6px;
  -webkit-tap-highlight-color: transparent;
}
.rp-fullscreen-dismiss:hover { background: rgba(15, 23, 42, .95); border-color: #CDDE00; }

/* iOS-only hint: iOS Safari can't hide its chrome in-browser, so point the user
   at Add to Home Screen — which hides Safari's bars; the iOS status bar stays
   (RPV2-29 round 2). Bottom-center, dismissible, short-lived.

   RPV2-112 (2026-09-24). In an iPhone Safari tab the 9:16 picture fills the
   full height — there is no letterbox band — so this pill sits on the game's
   bottom row (AHA's answers, "Talk to Care Team"). Three rules keep it from
   getting in the way:
   - `pointer-events: none` on the pill, `auto` on its ✕ only: a tap anywhere
     else on it reaches the game underneath. It used to take every tap (20 of
     20 measured, none reached the game).
   - Centred with `left`/`right` + `margin: auto` + `width: max-content`, NOT
     `left: 50%; transform: translateX(-50%)`: with `left: 50%` a fixed box's
     shrink-to-fit width is capped by the half of the viewport to the right of
     `left`, so the copy wrapped to three lines (196.5x64.8px at 393px). Now it
     is one line (40px tall — the ✕ sets the height) on a 375px+ phone.
   - `.is-idle` fades it (and its ✕) out when fullscreen.js retires it; the
     same `pointer-events: none` then covers the ✕ too. */
.rp-fullscreen-hint {
  position: fixed;
  left: calc(12px + env(safe-area-inset-left, 0px));
  right: calc(12px + env(safe-area-inset-right, 0px));
  margin: 0 auto;
  width: max-content;
  max-width: calc(100% - 24px - env(safe-area-inset-left, 0px) - env(safe-area-inset-right, 0px));
  box-sizing: border-box;
  bottom: calc(12px + env(safe-area-inset-bottom, 0px));
  z-index: 12;
  display: flex;
  align-items: center;
  gap: 10px;
  padding: 8px 12px;
  font: 12px/1.3 system-ui, -apple-system, sans-serif;
  color: #e2e8f0;
  background: rgba(5, 11, 20, .92);
  border: 1px solid rgba(148, 163, 184, .45);
  border-radius: 999px;
  box-shadow: 0 8px 28px rgba(2, 4, 8, .5);
  pointer-events: none;
  transition: opacity .3s ease;
}
.rp-fullscreen-hint.is-idle,
.rp-fullscreen-hint.is-idle .rp-fullscreen-hint-close {
  opacity: 0;
  pointer-events: none;
}
@media (prefers-reduced-motion: reduce) {
  .rp-fullscreen-hint { transition: none; }
}
.rp-fullscreen-hint-close {
  pointer-events: auto;
  flex: none;
  width: 22px;
  height: 22px;
  padding: 0;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  font-size: 13px;
  line-height: 1;
  cursor: pointer;
  color: #94A3B8;
  background: transparent;
  border: 0;
  border-radius: 6px;
}
.rp-fullscreen-hint-close:hover { color: #fff; background: rgba(148, 163, 184, .15); }
