- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 20 Dec 2017 22:30:10 -0800
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 21 December 2017 06:30:52 UTC
Inspecting what code points the browser can find a glyph for basically has the same privacy implications. Though given that you can determine it through rendering perhaps we should offer some kind of more straightforward API around that (and make it async so it can be blocked more easily)... @tabatkins has the CSS WG been thinking about such a thing? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/165#issuecomment-353269379
Received on Thursday, 21 December 2017 06:30:52 UTC