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

> I don't think the purpose of .request() should be to cause .query() to return a different value.

@jyasskin So it's not a simple permission-elevation API anymore like it used to be. And if you return a stream with disabled tracks then it's no longer a straightforward request-functionality API either...
 
Is your idea that developers must first ask permission with `permission.request({name: "camera"})`, hold onto the object it resolves with, and then call `getUserMedia(constraints)`?

@alvestrand I’m all for individual browsers innovating, but you’re asking to change how the web works to do it, which is different. From where I'm sitting there's no problem today, and I haven't read a compelling blog on why we should steer developers toward permission bundling.

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