Re: [w3c/permissions] Automation: "Get Permission" (#180)

> Overall, I agree that the get API is probably not high priority .
> If the approach I suggested was sufficient for all use cases, then the "Get Permissions" command wouldn't just be low priority; it would be unnecessary. Can you say more about the use cases which motivate the command?

I am not sure there is a precise use case except convenience. Since the app can retrieve these values, it frees the app to store these values itself.

> This sounds acceptable as long as the "Set Permission" command is rejected in accordance with the following algorithm step:
> 
> If parameters.state is an inappropriate permission state for any implementation-defined reason, return a WebDriver error with WebDriver error code invalid argument.

Well, it could somehow work if the set permission is focusing on a specific context.
This might get messy when the set permission is about several contexts.

At least in WebKit implementation, this would also be somehow a layer violation.
WebDriver is a replacement to what Safari does and does not know about WebKit engine internal states.

-- 
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/180#issuecomment-404222220