- From: Martin Thomson <notifications@github.com>
- Date: Sun, 10 Feb 2019 17:32:58 -0800
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 11 February 2019 01:33:25 UTC
As the use of the tools in this spec are being used for more different features, we're starting to see the gaps. For instance, requests for media autoplay (#172) and fullscreen (#26) highlight the potential need for conveying additional permissions, specifically engagement. The storage access API implemented variously by Apple and Mozilla also shows how engagement with the origin is a necessary precondition for even showing a permissions prompt, and it might be necessary - even with permission - to have engagement before the associated action can be triggered. The API currently manages this poorly. If a permission is queried, what should it say if a request might be an outright denial in the absence of an engagement gesture, but a prompt if there is a recent click or key press? The permissions state really isn't sufficient for this. -- 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/189
Received on Monday, 11 February 2019 01:33:25 UTC