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

@martinthomson I completely agree that "variations in how browsers interact with users [are] an important property to preserve."

I don't think the purpose of `.request()` should be to cause `.query()` to return a different value. It should be to ask the user for permission to use a feature. Once permission is granted, you should get a capability object that lets you use the feature without further prompts (unless the user takes action to revoke permission), but having that capability object shouldn't imply that a subsequent `.request()` call won't show a prompt.

The only [objections](https://github.com/w3c/permissions/issues/83#issuecomment-242664188) to the polyfill's behavior were that it would cost resources/time to open the camera and would leave the camera light on. Resource optimization isn't restricted by specs, and [Jan-ivar thinks the camera light is a bug in Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1299515). So adding `.request()` definitely wouldn't "[force] [permission model] changes on browsers that they don't want".

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