Re: [w3c/permissions] A new permission for canvas data (#165)

1. A new glyph-detecting API seems out of scope for this repository and specification.
1. It's easy to use https://wpt.fyi/ to find test cases that distinguish just about any two browser versions, so I stop listening when the justification for a change is "prevent people from distinguishing browser versions". It only makes sense to hide in a crowd consisting of people using the same version of the same browser as you.
1. @tomrittervg's and @isislovecruft's goals for Tor still seem reasonably well served by a new `PermissionName` here, unless they want to rescind that request for now in favor of trying to get a GPU-independent path added to Firefox. This can proceed independently of an asynchronous replacement of the synchronous canvas-reading APIs. (The asynchronous APIs can improve the UX of requesting permission, but they don't replace sites' need to know whether a prompt will show at all.



-- 
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-353466045