- From: Jeffrey Yasskin <notifications@github.com>
- Date: Mon, 29 Aug 2016 13:43:54 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Message-ID: <w3c/permissions/issues/42/243249735@github.com>
Ah, right, and for midi we'd have <code>"midi-[sysex](https://webaudio.github.io/web-midi-api/#widl-MIDIOptions-sysex)-[software](https://webaudio.github.io/web-midi-api/#widl-MIDIOptions-software)"</code>, etc. That's plausible, but I think it gets klunky when you have more than one option. UAs do have to do more than store a string here: we [should forbid](https://w3c.github.io/permissions/#permissiondescriptor-stronger-than) weird behaviors like `"geolocation"` being denied while `"geolocation-precise"` is granted. However, that doesn't imply anything for the shape of the API. @alvestrand has a different vision for how `query()` and `request()` should work than I do (his `query()` stays orthogonal to [`enumerateDevices()`](https://w3c.github.io/mediacapture-main/#enumerating-devices) instead of obsoleting it), but even his more tightly scoped view involves a string in the descriptor dictionary: https://w3c.github.io/permissions/#media-devices. -- 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/42#issuecomment-243249735
Received on Monday, 29 August 2016 20:44:32 UTC