Re: [w3c/permissions] "Requesting more permission" algorithms are tightly coupled to prompts (#153)

Ah, I didn't consider that interpretation (clearly). Thanks for helping me understand!

Have you been following [the review for a new "Automation" section](https://github.com/w3c/permissions/pull/151)? For context: we discussed the difference between a "reactive" API (i.e. an API for responding to active prompts) and a "proactive" API (i.e. an API for setting internal permission state before prompts are even issued). Although I initially proposed a "reactive" API, @raymeskhoury [pushed for a "reactive" API instead](https://github.com/w3c/permissions/pull/151#issuecomment-309974220).

I assumed the two API styles were mutually exclusive, but it looks like that may be incorrect. Under this interpretation, if a promise for a given permission request is pending, and the relevant permission descriptor's state is set via WebDriver, then we should expect the promise to be resolved with the new value. In other words, the "proactive" API can be used to react to previously-issued prompts.

@jyasskin Does that sound right to you? @raymeskhoury do you know if Chrome's implementation is well-suited to this behavior?

-- 
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/153#issuecomment-311794882