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

> Provides a new spelling for several old APIs where we can get their interfaces right.

I don't find this convincing myself.  Old APIs are getting new spellings as we speak.  The poster child here, geolocation, has been talking about a new promise-based API.  But the problem there is that there is nothing functionally wrong with their API, it's just disgusting when viewed with 2016 eyes.

> Provides a uniform spelling for requesting a permission so developers don't have to learn the intricacies of each capability's request function. 

I very much agree with the point on tempering here.  The complexity here is not in the high level "ask for X", it's in the nuance involved with the descriptor.  Of course, we all emphasize the importance of that point that differently.

@jan-ivar's concern is related to this I think.  We aren't dealing well with the different ways that browsers might choose to implement access control.  If all we ever do is vend season passes for sites, then this API is a fine one, but we don't do that for "filesystem" (i.e., `<input type="file">`). 

At some level, I think that we do need to dumb down the interaction across the different APIs, but thus far it's been a little slap-dash.

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