- From: Alan Stearns via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Aug 2020 16:09:09 +0000
- To: public-css-archive@w3.org
@litherum knows better, but my understanding is that this sentence was added mostly to describe reality - in that Safari had already implemented this behavior and continues to behave this way. The subsequent fingerprinting discussion has happened in part to figure out how to address problems with this behavior. Two of the suggestions we have considered are: 1) Allow some User-Installed Fonts to match for particular languages where many web pages depend on them 2) User agents that have this font-matching behavior MUST provide UI to let the user opt-in to User-Installed Font matching Would either or both of these requirements make the behavior more acceptable to the i18n WG? -- GitHub Notification of comment by astearns Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5421#issuecomment-674147816 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 August 2020 16:09:11 UTC