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

> Prompts are far from an ideal solution and if UAs can find good ways to make
> permission decisions in other ways it will result in a better user
> experience.

Oh! This is very useful context for me; I had assumed that prompts were
fundamental to the Permissions API. Given that this is *not* the case, then it
seems unwise to define a testing API which is geared around prompts, or really,
any user interaction at all. This makes the "proactive API" seem much more
fitting.

At first, I thought this style of API tended to subvert the "driver is a real
user" conceit. In other words: if users can't arbitrarily set permission status
at any time, then WebDriver shouldn't expose that functionality (since it would
encourage people to write tests that don't reflect real user flows). But that's
a faulty assumption. I can set my permissions for this domain via the Firefox
UI right now.

So consider me convinced. The "proactive API" is the most fitting solution.
I'll work on updating this patch accordingly (expecting it to become much
simpler).

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