Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92)

No objection to `requestAll()`. I removed `request(sequence<>)` because it needed some fixing in the the spec that I didn't want to do right then, and it isn't what [Chrome implemented](https://code.google.com/p/chromium/codesearch/#chromium/src/third_party/WebKit/Source/modules/permissions/Permissions.idl), but I'm not fundamentally opposed to it either.

Personally I kinda like @alvestrand's option 1, where the browser collects up all the `request()` calls made within a single turn and shows them in a sensible UI, but I do see that this might be hard to predict for developers.

On `request(sequence<sequence<PermissionDescriptor>>)` -> `Promise<sequence<PermissionsStatus>>`, I'd imagined that as a group of `request({name: 'camera', options: [option1, option2, ...]})`. I see that `getUserMedia` may have interacting preferences for the camera and mic, but I'm worried about how we specify that in a generic `request()` API, and how the UI should look for arbitrary combinations of these things. Maybe for individual interacting things, we need to keep some separate request APIs? (This may reinforce #83.)

---
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/92#issuecomment-215180279