From ee77490b5e139dc01c4265a60dbaec43db50ebc6 Mon Sep 17 00:00:00 2001 From: "Myles C. Maxfield" Date: Wed, 24 Aug 2022 00:21:17 -0700 Subject: [PATCH] [css-fonts-4] Rename "system font fallback" to "installed font fallback" to avoid confusion with the system font It isn't actually marked as a proper Bikeshed 'term,' so there will be no broken links. --- css-fonts-4/Overview.bs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/css-fonts-4/Overview.bs b/css-fonts-4/Overview.bs index 44277459f9d..76d46f80895 100644 --- a/css-fonts-4/Overview.bs +++ b/css-fonts-4/Overview.bs @@ -1940,7 +1940,7 @@ The ''@font-face'' rule to use downloaded fonts when rendering characters in other documents for which no other available font exists - as part of the system font fallback procedure. + as part of the installed font fallback procedure. However, this would cause a security leak since the contents of one page would be able to affect other pages, something an attacker could use as an attack vector. @@ -3710,7 +3710,7 @@ Cluster matching than the general case of matching a single character by itself. For sequences containing variation selectors, which indicate the precise glyph to be used for a given character, - user agents always attempt system font fallback + user agents always attempt installed font fallback to find the appropriate glyph before using the default glyph of the base character. @@ -3761,7 +3761,7 @@ Cluster matching and the trailing selectors must be ignored. [[!UNICODE]]
  • Otherwise, the user agent may optionally use - system font fallback + installed font fallback to match a font that supports the entire cluster.
    • @@ -3819,7 +3819,7 @@ Character handling issues contain a glyph for that codepoint, user agents must display some form of missing glyph symbol for that character - rather than attempting system font fallback + rather than attempting installed font fallback for that codepoint. When matching the replacement character U+FFFD, user agents may skip the font matching process