WebDriver: Make it possible to pass a different origin to "Set Permission"

[rakuco]

https://w3c.github.io/permissions/#set-permission-command changes permissions for "all environment settings objects whose origin is the same as the origin of [the current settings object]".

This is somewhat problematic from a testdriver perspective when cross-origin tests are involved: there are limitations that end up making all WebDriver communication go through the context that includes testharness.js, so if a given test includes a cross-origin iframe that needs to invoke "Set Permission" the call will go through the main frame and not have the desired effect.

Even though this is a testdriver limitation, I guess fixing it is not trivial, so I was wondering if the editors would be open to changing the spec itself to make it possible to (optionally) pass different origins.

[miketaylr]

I guess we could do that w/ an optional POST body like {"origin": "example.com"}. I don't have any sense of how feasible this would be to implement in the various webdriver implementations though.

[rakuco]

I'm only familiar with the ChromeDriver code. At least there I don't think it'd be a big issue, as the code that fetches the current origin and passes it along is fairly simple. Gecko seems to have very limited support for this endpoint, but I dunno about WebKit.

[miketaylr]

Maybe @jgraham or @whimboo could comment on the feasibility for Marionette/Geckodriver.

[miketaylr]

I had a chat with @jgraham in person at TPAC, and while he hasn't studied this issue in depth, he speculated that it shouldn't be too difficult for marionette/geckodriver if/when they implement the commands.

[OrKoN]

Origin will be (hopefully) available in WebDriver BiDi command #436

[miketaylr]

WebDriver BiDi command #436

Note: this has landed now.