- From: youennf <notifications@github.com>
- Date: Mon, 16 Jul 2018 06:53:19 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 16 July 2018 13:53:43 UTC
> If https://w3c.github.io/permissions/#set-permission-command has enough leeway to allow for the behavior that Safari has, then what we could do in testdriver.js is just to not allow use of the API except in top-level frames, so that tests can't depend on such differences. That'd be enough to unblock almost all getUserMedia and WebRTC tests, I'd bet. Sounds like a good step forward. > That step is intentionally vague, written to allow exactly the kind of variance that Safari exhibits. If this text were implemented in Safari, wouldn't a call to "Set Permissions" within a nested browsing context trigger the "single value for all browsing contexts" behavior that you've described? Probably. The issue is that if the spec allows very different behaviors, the interop story might not be very good. It would be good to understand the scenarios that require this highly flexible approach. Maybe we can do some simplification here which might actually help both implementors and users of this API. -- 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/181#issuecomment-405254771
Received on Monday, 16 July 2018 13:53:43 UTC