Re: [w3c/permissions] Automation: "set permission" granularity (#181)

For context, here's the reference to the "current browser context":

> 5. Let settings be the environment settings object of the current browsing
>    context’s active document. 

This is fine-grained, but we designed it that way for completeness: a web application may include an iframe which requests permissions, and we wanted the "Set Permissions" command to support such use cases.

It sounds like Safari doesn't recognize the distinction. I may be mistaken, but I believe the current text allows such a simplification:

> 10. [...]
>     1. [...]
>        1. Interpret parameters.state as if it were the result of an
>           invocation of permission state for typedDescriptor with the
>           argument target made at this moment. 

That step is intentionally vague, written to allow exactly the kind of variance that Safari exhibits. If this text were implemented in Safari, wouldn't a call to "Set Permissions" within a nested browsing context trigger the "single value for all browsing contexts" behavior that you've described?

-- 
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/181#issuecomment-404242489