@@ -3891,21 +3891,37 @@ The set of <a href="#installed-fonts">installed fonts</a> available
38913891to the Font Matching Algorithm
38923892is explicitly undefined.
38933893
3894+ The default set of installed fonts will vary
3895+ by UA, platform, and locale;
3896+ it is important that users be able to customise
3897+ which installed fonts are available for rendering web pages
3898+ and to which generic font families, if any,
3899+ these fonts are mapped.
3900+
38943901UAs may choose to expose all installed fonts to the web,
38953902regardless of how that font was installed;
38963903doing so is likely to have good internationalization properties
38973904for users whose primary language is not supported
38983905by fonts shipping with their operating system.
3906+
38993907UAs may alternatively choose
3900- to not expose user-installed fonts to aid privacy on the web;
3908+ to not initially expose any user-installed fonts to aid privacy on the web;
39013909for the set of installed fonts a user has installed
39023910is often used as a tracking vector to track users across the web.
3911+ Users would then add to add to or remove fonts from that set,
3912+ according to their needs.
3913+
39033914UAs may choose a hybrid approach, where some user-installed fonts
3904- are exposed for internationalization,
3915+ are initially exposed for internationalization,
39053916but others aren't.
3917+ Again, users would be able to customise this starting set.
3918+
39063919UAs are expected to make informed decisions
3907- on which fonts they expose to the web,
3920+ on which fonts they expose to the web by default ,
39083921so as to balance between internationalization and privacy.
3922+ UAs are expected to also provide a convenient means
3923+ for users to add and subtract fonts
3924+ to meet their particular needs.
39093925
39103926<wpt>
39113927 fallback-remote-to-data-url.html
0 commit comments