- From: Jan-Ivar Bruaroey <notifications@github.com>
- Date: Wed, 26 Aug 2020 20:42:39 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 27 August 2020 03:42:51 UTC
> The order of firing the events is unclear to me when reading the spec. The order of [reacting-to-revocation](https://w3c.github.io/permissions/#reacting-to-revocation) and [PermissionStatus-update](https://w3c.github.io/permissions/#PermissionStatus-update) seems unclear, so this might affect all permissions. @jyasskin may know the intent. > I have a slight preference for firing the PermissionStatus event first. Me too, in a cause and effect kind of way. > Also, https://w3c.github.io/permissions/#media-devices should ideally link to https://w3c.github.io/mediacapture-main/#ends-nostop in the section dealing with stopping MediaStreamTrack when permission is revoked. This I think we can model on how [ambient-light-sensor](https://w3c.github.io/permissions/#ambient-light-sensor) does it, but adding a _"generic capture device permission revocation algorithm"_ to mediacapture, and calling it. I can do a PR in https://github.com/w3c/mediacapture-main/issues/439. -- 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/223#issuecomment-681327793
Received on Thursday, 27 August 2020 03:42:51 UTC