- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Sep 2023 11:50:43 +0000
- To: public-css-archive@w3.org
I think what makes sense is: 1. It doesn't make any sense to discuss this in the taxonomy section. I think the taxonomy section should just simply describe, well, taxonomy, rather than its implications on other algorithms. There fore, I think we should replace both "The set of [installed fonts](https://drafts.csswg.org/css-fonts-4/#installed-fonts) available in the [Font Matching Algorithm](https://drafts.csswg.org/css-fonts-4/#font-matching-algorithm) is explicitly undefined" and "User agents may choose to ignore User-Installed Fonts for the purpose of the [Font Matching Algorithm](https://drafts.csswg.org/css-fonts-4/#font-matching-algorithm)" with "Please see [Font Matching Algorithm](https://drafts.csswg.org/css-fonts-4/#font-matching-algorithm) for a description of how user-installed fonts may interact with the font matching algorithm. 2. Add a paragraph to 5. Font Matching Algorithm that describes the tradeoff. Something like: > The set of [installed fonts](https://drafts.csswg.org/css-fonts-4/#installed-fonts) available in the [Font Matching Algorithm](https://drafts.csswg.org/css-fonts-4/#font-matching-algorithm) is explicitly undefined. > > Note: UAs may choose to expose all installed fonts to the web, regardless of how that font was installed; doing so is likely to have good internationalization properties for users whose primary language is not supported by fonts shipping with their operating system. UAs may alternatively choose to not expose user-installed fonts to aid privacy on the web; for the set of installed fonts a user has installed is often used as a tracking vector to track users across the web. UAs may choose a hybrid approach, where some user-installed fonts are exposed for internationalization, but others aren't. UAs are expected to make informed decisions on which fonts they expose to the web, so as to balance between internationalization and privacy. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5421#issuecomment-1727571304 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 September 2023 11:50:45 UTC