- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Mar 2020 15:09:20 +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. 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, which doesn't make this a great solution for large numbers of people. If i understand correctly, the problem arises because people serving web pages are able to inspect which fonts are available on a users system. Could someone explain for me (in simple terms) why users and implementers need to jump through all the hoops described above rather than simply preventing the web browser from communicating back what fonts are available on the user's system? -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4497#issuecomment-593449193 using your GitHub account
Received on Monday, 2 March 2020 15:09:22 UTC