- From: Henri Sivonen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Mar 2020 09:56:19 +0000
- To: public-css-archive@w3.org
> I'm worried about the impact of this on minority language users, and also specialists such as egyptologists, and other script researchers. (Non-Linux-using) egyptologists will be fine. macOS, Windows 10, Android, and Chrome OS ship with font support for Egyptian hieroglyphs by default. Unfortunately, Ubuntu and Fedora don't install font support for Egyptian hieroglyphs by default. I think the correct way forward is convincing them that they should. If egyptologists want JSesh specifically, the options are including it as a Web font or opting out of privacy protection. > If users can opt to allow certain fonts which are never likely to appear in the browser defaults, it sounds like they expose themselves to fingerprinting, The alternative seems to be leaving everyone exposed to fingerprinting. > which doesn't make this a great solution for large numbers of people. I believe the number of people is much smaller than it appears considering that the most popular systems already have even long-dead scripts covered. > Canʼt we simply put a limit on the number of fonts a single site may use? How would that work? Scripting can change the page over time, and trying to maintain quota state over time make the quota maintenance state itself fingerprintable local state. -- GitHub Notification of comment by hsivonen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4497#issuecomment-594426913 using your GitHub account
Received on Wednesday, 4 March 2020 09:56:20 UTC