- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 May 2017 06:00:24 +0000
- To: public-media-capture-logs@w3.org
This error is specific to Chrome's permission model and UX, which uses "Allow", "Block" and "[x]", where the first two are permanent.
Apps probably use it to discern whether Chrome's users have permanently blocked them or not. Unfortunately, this doesn't generalize to other browsers' permission models.
Instead, the [spec](https://w3c.github.io/permissions/#dom-permissions-query) says apps should use:
```js
await navigator.permissions.query({name: "camera", deviceId}) == "blocked"
```
to learn whether they've been blocked (not implemented yet in any browser AFAIK).
@fippo I found one [hit](https://w3c.github.io/permissions/#status-of-a-permission) for "dismiss", but it appears to have no clear normative meaning.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/451#issuecomment-302616238 using your GitHub account
Received on Friday, 19 May 2017 06:00:30 UTC