- From: Jeffrey Yasskin <notifications@github.com>
- Date: Thu, 26 May 2016 16:18:35 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc:
- Message-ID: <w3c/permissions/pull/97/r64837203@github.com>
> + state</a> with the same <a>current settings object</a> should return the > + same value, unless the UA receives new information about the user's > + intent. > + </p> > + > + <p class="issue" id="issue-current-entry-incumbent-or-relevant"> > + Safari is the only known UA that returns different results from this > + algorithm for different settings objects with the same origin. We should > + test which of the <a > + href="https://html.spec.whatwg.org/multipage/webappapis.html#realms-settings-objects-global-objects">several > + possible settings objects</a> it uses. > + </p> > + > + <p> > + Some powerful features have more information associated with them than > + just a {{PermissionState}}. For example, {{MediaDevices/getUserMedia()}} I actually expect that the "camera" permission descriptor will become more like [`MediaStreamConstraints`](https://w3c.github.io/mediacapture-main/#idl-def-MediaStreamConstraints), rather than just the device ID that's there now. The descriptor is about describing a desired permission, while the `extra permission data` is about describing a granted permission, and they can be totally different kinds of data. I've updated the example above to make that more clear, by using `"bluetooth"` instead of `"camera"`. --- 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/pull/97/files/247f065b3c9d8d80a94fefbcee1b83488700000c#r64837203
Received on Thursday, 26 May 2016 23:19:30 UTC