- From: KOLANICH <notifications@github.com>
- Date: Thu, 21 Dec 2017 07:27:34 +0000 (UTC)
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 21 December 2017 07:27:56 UTC
I vote agains't an API to inspect glyphs and get their parameters. I insist on that the existing fingerprinting vectors must be eliminated, including [measureText and getBoundingClientRectangle-based](https://github.com/KOLANICH/Article-2015-Dull-captaincy-or-the-way-Tor-Project-fights-browser-fingerprinting). For example it is possible try to make the text rendering identical on all the systems, shipping the fonts, maybe even a separate pack of fonts for each operation system targeted to compensate the differrences between rendering. Then you can decouple results of text-measuring API from the real results and just hope that they correspond. If they don't, c'est la vie, someone's rendering got a little broken. -- 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-353278101
Received on Thursday, 21 December 2017 07:27:56 UTC