/**
 * Quizpio Pro — host leaderboard ranking-transition animation.
 *
 * One colour language across both motion modes: gained rank = green,
 * dropped = grey. The wash is always a one-shot class tied to the moment of
 * change — never a persistent element — so rows stay exactly the core
 * markup. Full motion: the wash rides the row's slide (core's own
 * `transition: transform 0.3s ease` drives the movement) and decays as the
 * row lands. Reduced motion: no movement; the same wash, held longer.
 *
 * Keyframes end unset so every row decays to its own resting background
 * (including the gold/silver/bronze rank tints) automatically.
 */

.quizpio-mount .qp-sidebar-row.qp-pro-moving {
	position: relative;
	z-index: 2;
}

/* Full motion — wash rides the slide. */
.quizpio-mount .qp-sidebar-row.qp-wash-up {
	animation: qp-pro-wash-up 0.65s ease;
}

.quizpio-mount .qp-sidebar-row.qp-wash-down {
	animation: qp-pro-wash-down 0.65s ease;
}

/* Reduced motion — same wash on an instant reorder, held longer. */
.quizpio-mount .qp-sidebar-row.qp-flash-up {
	animation: qp-pro-wash-up 1.15s ease;
}

.quizpio-mount .qp-sidebar-row.qp-flash-down {
	animation: qp-pro-wash-down 1.15s ease;
}

@keyframes qp-pro-wash-up {
	0% {
		background: #dcfce7;
		border-color: #86efac;
	}

	100% {}
}

@keyframes qp-pro-wash-down {
	0% {
		background: #f3f4f6;
		border-color: #e5e7eb;
	}

	100% {}
}

/*
 * The OS setting always wins: the Pro script never applies transforms under
 * reduced motion, and this block additionally disables core's row transition
 * so no positional animation can occur from any source.
 */
@media ( prefers-reduced-motion: reduce ) {
	.quizpio-mount .qp-sidebar-row {
		transition: none !important;
	}
}

/* ==== OI-122 — the streak flame sits below the avatar (moved at P192) ====

   The flame used to take its own grid track beside the score, and that track
   came straight out of the name's space: on a 390px phone the name had 41px
   where Core's own row gives it 83px, so short names broke mid-word. The flame
   now takes no track. It is out of flow, pinned to the start of the row's
   second track, where the avatar sits, so a name keeps exactly the room Core
   gives it (screens/streak-rows.py proves it by measuring each row with and
   without the flame).

   ★ NO GRID RULE ON CORE'S ROWS, AND NONE MAY COME BACK. Adding a track is what
   caused OI-122, and retyping Core's tracks is what OI-19 removed. Docs-gate
   check 24 fails on any such rule.

   ★ WHAT PRO STILL RELIES ON, declared in the handoff's §3: the avatar sits at
   the start of the row's second track, in both rows, and is 2rem square. The
   tracks differ. In `.qp-sidebar-row` the second track is only 1.75rem, and
   the avatar overflows it: the flame follows the avatar, not the track. In
   `.qp-lb-row` there is no avatar track at all: the second track holds
   `.qp-lb-left`, which starts with the avatar.

   The heights: 2rem avatar + 4px gap + 13px pill. The row padding drops from
   Core's 8px to 6px so the pair sits comfortably, and the avatar lifts 8px so
   the pair, not the avatar alone, is what is centred in the row.

   ★ P194 (OI-132): THE MINIMUM IS THE CONTENT'S, SO THE BOX MODEL IS STATED.
   The 2rem + 17px above is the pair's height, so it must measure the content
   box. Core's rows set no box-sizing and inherit the theme's, and many popular
   themes reset every box to border-box: there the minimum swallowed the padding
   and border, rows came out 49px instead of 63px, and the flame sat on the
   row's bottom edge (the dev's site, 2026-11-14). Core's rows have no set width,
   so this changes their height only. screens/streak-rows.py checks every view
   under such a reset as well as without one. */
.quizpio-mount .qp-sidebar-row.qp-pro-has-streak,
.quizpio-mount .qp-lb-row.qp-pro-has-streak {
	position: relative;
	box-sizing: content-box;
	min-height: calc( 2rem + 17px );
	padding-top: 6px;
	padding-bottom: 6px;
}

/* Every row matches once any flame is showing, so the list stays even (the
   dev's choice, mockup v2, A3).

   ★ THIS RULE STANDS ALONE, AND MUST. A browser without :has() throws away the
   whole selector list it appears in. Kept apart, such a browser loses only this
   rule: flame rows are still taller and correct, and the others stay Core's. */
.quizpio-mount .qp-sidebar-list:has( .qp-pro-streak ) .qp-sidebar-row,
.quizpio-mount .qp-leaderboard:has( .qp-pro-streak ) .qp-lb-row {
	box-sizing: content-box;
	min-height: calc( 2rem + 17px );
	padding-top: 6px;
	padding-bottom: 6px;
}

.quizpio-mount .qp-pro-has-streak .qp-avatar {
	position: relative;
	top: -8px;
}

/* ★ P29 — the player's certificate button sits ABOVE core's "Play another quiz".
   Core's .qp-final-actions is a flex column (frontend.css:542#display @A56), so
   `order` places Pro's appended button first without Pro touching core's DOM.
   Core's own buttons carry no explicit order (default 0), so a negative value
   lifts Pro's above them and nothing else moves.
   ★ THIS IS A DECLARED CROSS-LAYER CSS COUPLING — §3 C24, row 2. Pro now depends
   on that container being flex and on core's buttons having no order set. It is
   in b3-manual-reverify.md and re-walked at every core re-pin. It was added ON
   PURPOSE, after the fourteen existing couplings were finally written down —
   not by accident, which is how the first fourteen happened. */
.quizpio-mount .qp-final-actions .qp-pro-cert-mine {
	order: -1;
}

/* ★ grid-area NAMES ALL FOUR LINES. For an absolutely placed grid item, a bare
   `grid-row: 1` leaves the end line `auto`, which means the container's padding
   edge and not the end of row 1. The 50% below would then measure a taller box,
   and the flame would drift down, away from the avatar. */
.quizpio-mount .qp-pro-streak {
	position: absolute;
	grid-area: 1 / 2 / 2 / 3;
	inset-inline-start: 0;
	top: calc( 50% + 1rem - 4px );
	display: inline-flex;
	align-items: center;
	justify-content: center;
	gap: 3px;
	box-sizing: border-box;
	min-width: 2rem;
	background: #fcd34d;
	color: #78350f;
	font-size: 10px;
	font-weight: 800;
	padding: 1px 4px;
	border-radius: 9px;
	line-height: 1.1;
	animation: qp-pro-badge-in 0.4s ease;
}

.quizpio-mount .qp-pro-streak svg {
	display: block;
}

@keyframes qp-pro-badge-in {
	from {
		opacity: 0;
	}
	to {
		opacity: 1;
	}
}

@media (prefers-reduced-motion: reduce) {
	.quizpio-mount .qp-pro-streak {
		animation: none;
	}
}

/* ---------- Question images (P11) ----------
   One image above the question text, everywhere the core slot fires.
   Contain (never crop — the answer might live in the cropped part),
   height-capped so the options stay reachable, centered, letterboxed
   on a soft background when the ratio differs from the frame. */
.quizpio-mount .qp-pro-qmedia {
	display: block;
	max-width: 100%;
	max-height: 225px;
	margin: 0 auto 16px;
	object-fit: contain;
	border: 1px solid #e5e7eb;
	border-radius: 10px;
	background: #f9fafb;
}

@media ( max-width: 600px ) {
	.quizpio-mount .qp-pro-qmedia {
		max-height: 145px;
	}
}

/* ---------- Option images (P13) ----------
   One element, context-styled.

   BASE = the 26px thumbnail: what reveal-bar labels always show, and what
   answer buttons show in browsers without :has() support (the progressive
   fallback — same picture, humbler frame, zero breakage).

   CARD = inside an answer button, modern browsers reflow the whole button
   via :has(): image on top, letter + text in the row beneath. Grid areas,
   not column-flex, because core's DOM order is letter / image / text.

   Contain everywhere — at any size, the answer may live in the part a
   crop would remove. */
.quizpio-mount .qp-pro-omedia {
	width: 26px;
	height: 26px;
	border-radius: 5px;
	border: 1px solid #e5e7eb;
	background: #f9fafb;
	object-fit: contain;
	flex: 0 0 auto;
}

.quizpio-mount .qp-options .qp-option:has( .qp-pro-omedia ) {
	display: grid;
	grid-template-columns: auto 1fr;
	grid-template-areas:
		'img  img'
		'shape text';
	align-items: center;
	padding: 0;
	overflow: hidden;
	gap: 0;
}

.quizpio-mount .qp-options .qp-option:has( .qp-pro-omedia ) .qp-pro-omedia {
	grid-area: img;
	width: 100%;
	height: 120px;
	border: 0;
	border-radius: 0;
	border-bottom: 1px solid #e5e7eb;
}

.quizpio-mount .qp-options .qp-option:has( .qp-pro-omedia ) .qp-shape {
	grid-area: shape;
	margin: 11px 10px 11px 14px;
}

.quizpio-mount .qp-options .qp-option:has( .qp-pro-omedia ) .qp-opt-text {
	grid-area: text;
	padding: 11px 14px 11px 0;
}

@media ( max-width: 600px ) {
	.quizpio-mount .qp-options .qp-option:has( .qp-pro-omedia ) .qp-pro-omedia {
		height: 96px;
	}
}

/* ============================================================
   P23 — the seam consumers.
   ============================================================ */

/* The 2× Points tag (quizpio.question.tags). Core's poll-tag GEOMETRY, so
   the heading's rhythm is unbroken — but Pro's amber, so it reads as Pro's
   own and can never be mistaken for core's indigo chrome. It speaks the same
   visual language as the streak pill, which is the point: both are Pro
   telling you about points. */
.quizpio-mount .qp-pro-double-tag {
	display: inline-block;
	vertical-align: 4px;
	margin-left: 10px;
	font-size: 12px;
	font-weight: 800;
	background: #fef3c7;
	color: #92400e;
	border: 1px solid #fcd34d;
	padding: 2px 10px;
	border-radius: 999px;
	letter-spacing: 0.2px;
	white-space: nowrap;
}

/* The host's projected screens carry the question at 28px; the tag scales
   with it or it disappears from the back of a classroom. */
.quizpio-mount .qp-host-question .qp-pro-double-tag,
.quizpio-mount .qp-host-reveal .qp-pro-double-tag {
	font-size: 15px;
	padding: 3px 13px;
	vertical-align: 6px;
}

/* The player's own streak line (core A55 renders it; the class is core's and
   core has promised not to reach into it). Amber, so the note and the flame
   are visibly the same feature speaking. It is a SUB-LINE of the feedback
   banner it explains — no border, no background, nothing that would make it
   read as a second banner (composition rule, Collision 4).

   The measure is deliberate: side padding keeps it off the edges of a 330px
   phone at any bonus number, and the max-width stops it stretching toward a
   900px line on a desktop, where core gives the player 912px of content. */
.quizpio-mount .qp-reveal-note {
	max-width: 42rem;
	margin: -8px auto 16px;
	padding: 0 14px;
	box-sizing: border-box;
	color: #b45309;
	font-size: 13.5px;
	font-weight: 700;
	line-height: 1.45;
	text-align: center;
}

/* OI-13 — the join-screen certificate hint.
   Sizing follows CORE'S OWN subdued-helper pattern, .qp-lobby-help
   (frontend.css:449 @A84 — 13px, muted), rather than a new invention.
   Colour is core's --qp-muted TOKEN (frontend.css:1119 @A84), never a retyped
   hex: if core restyles, Pro follows. Same reasoning as qp-btn-primary at P30.

   margin -4px: core's .qp-join input carries margin-bottom 12px and Pro must
   not touch it, so the negative pull is the honest way to reach 8px above /
   16px below. The asymmetry ties the hint to the field it describes instead of
   letting it float midway to the button.

   display:flex is NOT decoration. With an inline icon a wrapped translation
   runs its second line back underneath the icon and the block loses its left
   edge. English never wraps, so this would have shipped invisible and surfaced
   only in a translated locale; the German panel in the approved mockup is what
   caught it.

   The icon is drawn in CSS rather than as an inline SVG because it is geometry
   plus a font glyph — a circle and a letter — not a shape CSS cannot draw.
   Pro's streak flame IS an SVG (pro-frontend.js) because a flame silhouette
   has no CSS expression. That is the dividing line, and it is the rule.
   Trade accepted knowingly: generated content is announced by some screen
   readers. The sentence carries the whole meaning, so an announced "i" is
   noise, not a barrier. */
.quizpio-mount .qp-pro-join-hint {
	display: flex;
	align-items: flex-start;
	margin: -4px 0 16px;
	font-size: 13px;
	line-height: 1.45;
	color: var( --qp-muted );
}

.quizpio-mount .qp-pro-join-hint::before {
	content: 'i';
	flex: 0 0 auto;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 14px;
	height: 14px;
	margin-inline-end: 7px;
	margin-top: 1px;
	border: 1px solid currentColor;
	border-radius: 50%;
	font-size: 9px;
	font-weight: 700;
	font-style: italic;
	line-height: 1;
}

/* ── "Scan to join" — the lobby QR (OI-56) ──────────────────────────────────
   Carried from the mockup the dev approved, per WM-22: these are the values
   that were looked at, not values re-derived to look equivalent.

   ★ THE BINDING CONSTRAINT IS THE HOST'S LAPTOP LID, NOT THE ROOM. A projected
   stage scales together, so scan DISTANCE is not what limits this — available
   WIDTH is. That is why the slot core ships is block-level, and why the size
   below is expressed against the lobby's own column rather than in absolute
   terms. Core's A121 recorded that this argument corrected its own reasoning.

   The position — beneath the PIN display, above the players list — is CORE's
   contract, not Pro's CSS. Do not attempt to move it from this file. */
.quizpio-mount .qp-pro-lobby-qr {
	margin: 0 auto 24px;
	max-width: 260px;
}

.quizpio-mount .qp-pro-lobby-qr svg {
	display: block;
	width: 100%;
	height: auto;
	border-radius: 12px;
}

.quizpio-mount .qp-pro-lobby-qr-label {
	margin-top: 10px;
	font-size: 15px;
	font-weight: 600;
	color: var( --qp-text, #1f2937 );
	letter-spacing: .01em;
}

@media ( max-width: 640px ) {
	.quizpio-mount .qp-pro-lobby-qr {
		max-width: 190px;
	}
}

/* ── Full-screen join mode ─────────────────────────────────────────────────
   ★ THESE RULES ARE DELIBERATELY NOT SCOPED UNDER .quizpio-mount.

   Every other rule in this file is, and that is right — but the overlay is
   PORTALLED to document.body, so it is not inside the mount and a scoped
   selector would simply never match it. This is the one documented exception;
   do not "fix" it by adding the scope back.

   Why it is portalled at all: position:fixed stops resolving against the
   viewport if any ancestor carries a transform, filter or perspective — that
   element becomes the containing block. Themes and page builders apply those
   invisibly for scroll animations, so the overlay would be bounded by that
   container, scrolling with the page, and the code (which sizes to the space it
   is given) could come out SMALLER than the inline one it replaced. It varies
   per PAGE and cannot be settled by sampling themes.

   Every class here carries the qp-pro- prefix, so nothing can collide with
   core's namespace even outside the mount. */
.qp-pro-qr-expand {
	margin-top: 10px;
	border: 1px solid #d1d5db;
	background: #fff;
	color: #374151;
	border-radius: 8px;
	padding: 6px 12px;
	font-size: 13px;
	font-weight: 600;
	cursor: pointer;
}

.qp-pro-qr-expand-icon { margin-right: .4em; }

.qp-pro-qr-expand-hint {
	margin: 6px auto 0;
	max-width: 280px;
	font-size: 12px;
	line-height: 1.5;
	color: #6b7280;
}

.qp-pro-qr-full {
	position: fixed;
	inset: 0;
	background: #fff;
	display: grid;
	place-items: center;
	padding: clamp( 12px, 3vh, 32px );
	/* A deliberate top-of-stack claim for a host-initiated, instantly
	   dismissible presentation mode — NOT a number tuned to beat someone
	   else's, which would go stale the moment theirs changed. */
	z-index: 2147483000;
}

/* The content column: a click here does NOT dismiss. The surround does. */
.qp-pro-qr-full-col {
	display: grid;
	grid-template-rows: auto minmax( 0, 1fr ) auto auto;
	place-items: center;
	gap: clamp( 6px, 1.6vh, 16px );
	width: 100%;
	height: 100%;
	min-height: 0;
}

/* ★ ONE LINE, ONE SIZE: “Quiz PIN: 321197”. Chosen by the dev after seeing it
   at the larger size too.

   ★ AND NOTE WHAT THE PIN IS, because an earlier draft of this comment had it
   backwards. The PIN is NOT a fallback for the code. Scanning only reaches the
   JOIN SCREEN — every player then types the PIN and a nickname, scanner or not.
   The QR saves typing the ADDRESS and nothing more; that is exactly why PIN
   prefill was struck rather than deferred (OI-56). So the PIN is the universal
   element here and the code is the optional convenience.

   The size is therefore a READABILITY floor, not a hierarchy statement: it must
   be readable from wherever the room is, and it does not need to dominate.

   The label stays GREY. With the size difference gone, colour is the only
   thing left telling the eye which part is the label and which is the value;
   an all-black run of sixteen characters buries the six digits that matter. */
.qp-pro-qr-full-pin {
	display: flex;
	align-items: baseline;
	justify-content: center;
	gap: .3em;
	flex-wrap: wrap;
	text-align: center;
	max-width: 100%;
}

.qp-pro-qr-full-lab {
	font-size: clamp( 22px, 5.4vh, 64px );
	font-weight: 800;
	letter-spacing: .04em;
	line-height: 1.05;
	color: #6b7280;
}

.qp-pro-qr-full-num {
	font-size: clamp( 22px, 5.4vh, 64px );
	font-weight: 800;
	letter-spacing: .04em;
	color: #111827;
	line-height: 1.05;
}

/* The code sizes to whatever row remains after the PIN, footer and address —
   never to a viewport fraction, which would not know about them. */
.qp-pro-qr-full-code {
	min-height: 0;
	min-width: 0;
	width: 100%;
	height: 100%;
	display: grid;
	place-items: center;
}

.qp-pro-qr-full-code svg {
	display: block;
	height: 100%;
	width: auto;
	max-width: 100%;
}

.qp-pro-qr-full-foot {
	display: flex;
	align-items: center;
	gap: clamp( 10px, 2vw, 24px );
	font-size: clamp( 12px, 1.8vh, 17px );
	color: #374151;
}

.qp-pro-qr-full-count { font-weight: 700; color: #111827; }

.qp-pro-qr-full-exit {
	display: inline-flex;
	align-items: center;
	gap: .5em;
	border: 1px solid #d1d5db;
	background: #fff;
	color: #374151;
	border-radius: 999px;
	padding: .4em .9em .4em .5em;
	font-size: inherit;
	font-weight: 600;
	cursor: pointer;
}

.qp-pro-qr-full-x {
	display: grid;
	place-items: center;
	width: 1.5em;
	height: 1.5em;
	border-radius: 50%;
	background: #111827;
	color: #fff;
	font-size: 1em;
	line-height: 1;
	font-weight: 700;
}

/* The address is a TRUST SIGNAL before it is an instruction — people hesitate
   to scan an unknown code, and a recognisable domain is what makes them
   willing. Carried from the certificate's fitBlock LESSON, not its code (that
   measures a canvas): shrink before breaking, and when it must break, break
   only where a reader can interpret it. The markup emits no <wbr>, so wrapping
   is left to normal word rules and a URL will not be split mid-token. Never
   truncated: a cut-off address looks complete and is unusable. */
.qp-pro-qr-full-addr {
	max-width: 100%;
	font-size: clamp( 11px, 1.9vh, 20px );
	font-weight: 700;
	color: #111827;
	line-height: 1.35;
	text-align: center;
	overflow-wrap: normal;
	word-break: normal;
	hyphens: none;
}

/* ★ P193 (OI-127): the certificate's step on Share Result. It lives on
   document.body, outside .quizpio-mount, so none of Core's rules reach it — and
   a theme's bare <button> and <h2> rules would. So every property a theme might
   set is decided here, for every state (Core's A188 lesson with its Leave links:
   a theme added a shadow, corners and 18 px text wherever a rule was silent).
   The look is Core's journey mockup (v5, Option A): a white card, 12 px corners,
   at most 420 px wide and 16 px from the screen's edge, over a 55% dim; the
   title and a close button, the real certificate, two full-width buttons. */
.qp-pro-share-step {
	position: fixed;
	inset: 0;
	z-index: 2147483000;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 16px;
	background: rgba( 0, 0, 0, 0.55 );
	box-sizing: border-box;
	overscroll-behavior: contain; /* a swipe on the dim does not scroll the page behind */
}
.qp-pro-share-step .qp-pro-share-card {
	width: 100%;
	max-width: 420px;
	max-height: 100%;
	overflow-y: auto;
	box-sizing: border-box;
	padding: 16px 20px 20px;
	background: #fff;
	border-radius: 12px;
	box-shadow: 0 20px 50px rgba( 0, 0, 0, 0.3 );
	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
	color: #1f2937;
	text-align: start;
}
.qp-pro-share-step .qp-pro-share-head {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 12px;
	margin: 0 0 12px;
}
.qp-pro-share-step .qp-pro-share-head h2 {
	margin: 0;
	padding: 0;
	border: 0;
	background: none;
	font-family: inherit;
	font-size: 18px;
	font-weight: 600;
	line-height: 1.3;
	letter-spacing: normal;
	text-transform: none;
	color: #111827;
}
.qp-pro-share-step .qp-pro-share-preview {
	display: block;
	width: 100%;
	height: auto;
	max-width: 100%;
	margin: 0 0 16px;
	padding: 0;
	border: 1px solid #e5e7eb;
	border-radius: 8px;
	background: none;
	box-shadow: none;
}
/* ★ P194 (OI-133): min-width and min-height too. A theme's floor on every <button>
   (120 x 60 px in the hostile-theme check) widened the close button and pushed the
   title aside; the two choices restate their own 44px floor below. */
.qp-pro-share-step button {
	box-sizing: border-box;
	min-width: 0;
	min-height: 0;
	margin: 0;
	font-family: inherit;
	letter-spacing: normal;
	text-transform: none;
	text-shadow: none;
	box-shadow: none;
	cursor: pointer;
	-webkit-appearance: none;
	appearance: none;
}
.qp-pro-share-step .qp-pro-share-close {
	flex: none;
	width: 32px;
	height: 32px;
	padding: 0;
	border: 0;
	border-radius: 0;
	background: none;
	color: #6b7280;
	font-size: 28px;
	font-weight: 400;
	line-height: 1;
}
.qp-pro-share-step .qp-pro-share-close:focus { background: none; color: #6b7280; box-shadow: none; outline: none; }
.qp-pro-share-step .qp-pro-share-with,
.qp-pro-share-step .qp-pro-share-without {
	display: block;
	width: 100%;
	min-height: 44px;
	padding: 10px 18px;
	border-radius: 8px;
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	text-align: center;
	text-decoration: none;
}
/* :focus restates the resting look, so a theme's own focus rules cannot recolour the
   buttons; the step moves focus to Share With Certificate as it opens. */
.qp-pro-share-step .qp-pro-share-with,
.qp-pro-share-step .qp-pro-share-with:focus { border: 1px solid #4f46e5; background: #4f46e5; color: #fff; box-shadow: none; outline: none; }
.qp-pro-share-step .qp-pro-share-without,
.qp-pro-share-step .qp-pro-share-without:focus { border: 1px solid #d1d5db; background: #fff; color: #1f2937; box-shadow: none; outline: none; }
.qp-pro-share-step .qp-pro-share-without { margin-top: 10px; }
/* The ring is for the keyboard only, and outranks the resting looks above (0,3,1 over
   0,3,0), so a theme's own :focus outline never rings a button the step focused itself. */
.qp-pro-share-step .qp-pro-share-card button:focus-visible { outline: 2px solid #4f46e5; outline-offset: 2px; }
/* ★ P194 (OI-133): a theme's lift or press (a transform on :hover, :focus or :active,
   at 0,1,1) never moves these buttons. */
.qp-pro-share-step .qp-pro-share-card button,
.qp-pro-share-step .qp-pro-share-card button:hover,
.qp-pro-share-step .qp-pro-share-card button:focus,
.qp-pro-share-step .qp-pro-share-card button:active { transform: none; }
/* A mouse only: a touch browser leaves :hover where the last tap was, which here is
   where Share Result sat, so a button of the step would open looking pressed
   (Core's A188 lesson with its answer cards). */
@media ( hover: hover ) {
	.qp-pro-share-step .qp-pro-share-close:hover { color: #111827; }
	.qp-pro-share-step .qp-pro-share-with:hover { border-color: #4338ca; background: #4338ca; }
	.qp-pro-share-step .qp-pro-share-without:hover { background: #f3f4f6; }
}
.qp-pro-share-step .qp-pro-share-hint {
	margin: 12px 0 0;
	padding: 0;
	font-family: inherit;
	font-weight: 400;
	letter-spacing: normal;
	text-transform: none;
	font-size: 13px;
	line-height: 1.45;
	color: #6b7280;
}
