Re: [w3c/permissions] Introduce "Automation" section (#151)

Okay, I've re-written this patch to manipulate permission state directly. As
expected, this is much simpler! The functionality is exposed via a single
command, "Set Permission" whose URI template looks like this:

    /session/{session id}/permissions/set

Given that this is the only command, the `set` part is kind of superfluous. Due
to the way the WebDriver extension mechanism is worded, though, we have to
specify some value there.

Alternatively, we could expose this as three commands:

    /session/{session id}/permissions/grant
    /session/{session id}/permissions/prompt
    /session/{session id}/permissions/deny

...but this may be confusing, since I think most people would assume that
POSTing to `prompt` would cause a prompt to be displayed. And further, these
URLs sound like they would work as a means to interact with active prompts, but
(as discussed above), they would not. (Although maybe that can change--I've
opened gh-153 to discuss a modification that would make this "proactive" API
also work "reactively".)

-- 
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/pull/151#issuecomment-310771824