/*!
 * FAZ Cookie Manager — Cookie Policy frontend styles.
 *
 * Deliberately minimal: inherits font, colours, spacing from the host
 * theme. The only interventions are:
 *   1. Lift the typographic max-width constraint that block themes like
 *      Twenty Twenty-Four/Five impose via `.entry-content` (60ch) — which
 *      makes a long legal document feel cramped.
 *   2. Style the optional disclaimer so it is visually distinct from
 *      body copy (warning-coloured callout, light backdrop). Visibility
 *      and text are now admin-configurable; CSS still gives it the
 *      callout treatment whenever it is rendered.
 *   3. Style the per-category accordion (<details>/<summary>) and the
 *      cookie table inside it. Accordion is HTML5-native, JS-free,
 *      keyboard-accessible. The table inside uses a mobile-friendly
 *      data-label fallback so the layout collapses to a card stack on
 *      narrow screens without media queries fighting the theme.
 *   4. Neutralise <code> inside the policy. The policy uses <code> for
 *      cookie names and technical tokens; many themes style the global
 *      `code {}` element with a coloured background + border (often via
 *      their own `--theme-color-*` custom properties), which looks out of
 *      place inside a legal document. We force a transparent, border-less,
 *      inherit-colour monospace token so the policy renders neutrally on
 *      any theme.
 *
 * Anything else (headings, link colours, paragraph rhythm) is theme.
 */

/* 1. Fill the available column. Most block themes constrain content to ~60ch. */
.faz-cookie-policy {
	max-width: none;
	width: 100%;
	box-sizing: border-box;
}

/* 4. Neutral <code> regardless of the active theme. `!important` is a
   deliberate, tightly-scoped exception to this file's otherwise no-!important
   convention: a theme's `code {}` rule may itself be flagged !important or use
   an equal-specificity `.entry-content code` selector, and the policy must look
   clean on every theme. Only the box/colour properties are forced; the
   monospace family is left to the theme/UA. */
.faz-cookie-policy code {
	border: 0 !important;
	background: transparent !important;
	background-color: transparent !important;
	color: inherit !important;
	box-shadow: none !important;
	padding: 0;
}

/* 3. Cookie list (auto-populated). One <details> per category. */

/* Summary layout — selector specificity is intentionally higher
   (details.X > summary.Y) so block themes that hit `summary` with
   `display: block` via .entry-content selectors lose the cascade
   battle. The category heading inside is forced to inline-flex so
   the theme's default `h3 { display: block; width: 100% }` cannot
   push the count badge onto a second line. */

/* Hide the native marker on every engine (Blink/WebKit + Gecko + spec). */

/* Custom chevron — sits left of the title, rotates on [open]. */

/* Category name. The renderer emits this as <span role="heading"
   aria-level="3"> (changed from <h3> in 1.16.2 because block-level
   headings inside <summary> get coerced to display:block by every
   block-theme reset and break the inline layout). Force inline-flex
   + flex:1 so the chevron, name, count all sit on ONE row. */

/* Cookie table inside the accordion. */

/* Mobile: collapse the table into a card-per-row layout using
   the data-label attributes the renderer emits on each <td>. */

/* 2. Disclaimer — admin-configurable callout. */
.faz-cookie-policy-disclaimer {
	margin-top: 2em;
	padding: 0.85em 1em;
	background: var(--faz-disclaimer-bg, #fff5d6);
	border-left: 4px solid var(--faz-disclaimer-accent, #d4a017);
	font-size: 0.9em;
	line-height: 1.55;
}