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

First of all, Android moved out of this system. Second of all, the problem with it is that Android used to (and still does for some apps) require the user to accept the permissions in order to install the applications. This means that users would be incentivized to say yes and overlook a couple of dodgy permissions.

Obviously, there is no equivalent to this system on the Web and adding `request()` or `requestAll()` isn't actually pushing in that direction. It's just streamlining something that web apps have been doing for a while: asking for permissions. You can already implement `request()` for roughly all the web exposed API. `requestAll()` is simply a way to define multiple permissions to be related. For example, a website requiring geolocation and notifications to work properly will not have to show two prompts. It's better for the user.

If your general concern is that websites would use this to prevent users access to the content unless the permissions are granted they can already do that. Any video chat app will not allow you to start using it unless you granted them at least mic access because you would have a broken experience otherwise. Will streamlining the methods make it more likely that websites will abuse it? Maybe. I don't know. Though, I don't think we should design based on this.

---
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-215669836