/*
 * Self-hosted Material Symbols (Apache License 2.0), two static woff2 faces.
 *
 * **The family name carries an `MF ` prefix, and that is the whole point of it.**
 * A `font-family` is a global namespace: two `@font-face` rules naming the same family
 * do not merge, the later one in the document wins. The suite declared
 * `"Material Symbols Outlined"` — Google's own name — and lost to a copy of it in the
 * site's CSS, a 3.74 MB file with no `font-display` against this 320 KB one. On an iPhone
 * over mobile data the download missed Safari's block window and the browser fell back;
 * and the fallback for a ligature font is **the ligature name printed as text**, so
 * readers saw `frame_exclamation` in 1.5em beside a heading (divb-hq#166).
 *
 * The source of that copy was never found — not the Customizer, not `theme.json`, not the
 * global-styles post, not `wp_options`, not any file under `wp-content/`. Which is the
 * argument for a namespace rather than a repair: under Google's name **any** foreign rule
 * can win, and this fixes the class instead of the one case. The cost is deliberate and
 * worth saying out loud: a stylesheet outside the suite that targets
 * `"Material Symbols Outlined"` no longer reaches these faces. Nothing in the suite does —
 * `Mf_Suite_IconFontTest` walks the shipped assets and fails if the bare name comes back.
 * DSGVO-safe: served from the plugin, no external requests. Only the @font-face
 * rules live here (their URLs resolve relative to this file); the icon chip
 * styling is on .mb__chip in the block stylesheet, and the symbol element's own
 * rules are in assets/symbol/symbol.css.
 *
 * Both files are STATIC INSTANCES, not the variable font — neither carries an
 * `fvar` table, so `font-variation-settings` ('FILL', 'wght', 'GRAD', 'opsz')
 * has no effect here and a filled glyph has to be a second file. That is what
 * "Filled" below is; it is fetched only by a page that actually renders one,
 * because no rule references the family until .mf-symbol.is-filled matches.
 *
 * The `font-weight: 100 700` range is deliberate and load-bearing, not a
 * description of the file: it tells the browser this face covers those weights,
 * which is what stops SYNTHETIC BOLDING from smearing a glyph that sits inside a
 * heading or a <strong>. Narrowing it to 400 would change how existing icons
 * render across the whole suite.
 */
@font-face {
	font-family: "MF Material Symbols Outlined";
	font-style: normal;
	font-weight: 100 700;
	font-display: block;
	src: url(fonts/material-symbols-outlined.woff2) format("woff2");
}

@font-face {
	font-family: "MF Material Symbols Outlined Filled";
	font-style: normal;
	font-weight: 100 700;
	font-display: block;
	src: url(fonts/material-symbols-outlined-filled.woff2) format("woff2");
}