/*
 * Self-hosted Roboto (Task 8 — SEA landing-page font optimization).
 *
 * The RevSlider hero declares `font-family: Roboto` on its layers but loads the
 * webfont from Google Fonts (fonts.googleapis.com). That third-party request is
 * intercepted by Real Cookie Banner's "Google Fonts" content blocker until the
 * visitor grants consent, so pre-consent the hero has no Roboto to render and —
 * because RevSlider outputs no generic fallback — drops to the browser default
 * serif.
 *
 * Serving Roboto first-party from this theme fixes that: the blocker only matches
 * fonts.googleapis.com, so this @font-face is never blocked and Roboto is
 * available at first paint for every visitor, regardless of consent. It also
 * keeps the font off Google entirely (the reason it was consent-gated to begin
 * with). Weights 300/400/700 match what the sliders request; latin + latin-ext
 * cover German (umlauts, ß) and common punctuation.
 *
 * See _docs/SEA-Optimization/README.md (Task 8).
 */

@font-face {
	font-family: "Roboto";
	font-style: normal;
	font-weight: 300;
	font-display: swap;
	src: url("roboto-300.woff2") format("woff2");
}

@font-face {
	font-family: "Roboto";
	font-style: normal;
	font-weight: 400;
	font-display: swap;
	src: url("roboto-400.woff2") format("woff2");
}

@font-face {
	font-family: "Roboto";
	font-style: normal;
	font-weight: 700;
	font-display: swap;
	src: url("roboto-700.woff2") format("woff2");
}

/*
 * Hero fallback. RevSlider writes `font-family: Roboto` inline on each layer with
 * no generic fallback, so only an !important rule can add one. Scoped to sr7
 * layers whose inline font is Roboto, so it never touches layers set to another
 * family. Now, if Roboto is unavailable for any reason, the hero falls back to
 * the site's Arial stack instead of serif.
 */
sr7-module [style*="font-family: Roboto"] {
	font-family: "Roboto", Helvetica, Arial, sans-serif !important;
}