Re: [w3c/permissions] Drop .request() (#83)

I kind of lost track when this discussion started to heated up and had no time to read everything. 

But i just wanted to share with you my own way of dealing with query and requesting permission. I call it [browser-su](https://github.com/jimmywarting/browser-su) It isn't really a pollyfill since it doesn't follow the standard exactly but it dose more then what it's supposed to do (checkout the wiki). Maybe you can get some inspiration from that? I don't know...

I don't like the "ask first, open later" approach i always try to ignore them until i'm sure what it will do to me or that they get it when i want them to get it. That's why a user interaction should be required IMO. Kind of neutral if it stays persistent or not.
I don't like the fact that they can request multiple stuff at once. Like some old Android apps.

Either way i think a request model of some sort is useful since it can fix all the different way we have of asking for permission of something. Instead of dropping the request how about changing the definition of what it means to request permission for `fullscreen, geolocation, midi, notifications, pointerlock, userMedia, push, filesystem, bluetooth, screen, NFC`? cuz there is way to many way to request for all of this things. 

What i tried to do with browser-su is to report back if a request have been denied or dismissed which i think is useful.

-- 
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/83#issuecomment-244429328