WebDriver BiDi support in testdriver needs documentation

[rakuco]

Now that #45823 has been merged, it would be good to update the existing testdriver documentation. Having support for https://w3c.github.io/permissions/#webdriver-bidi-command-permissions-setPermission in testdriver would be great, but it is unclear how this is supposed to happen.

Specifically, at least https://web-platform-tests.org/writing-tests/testdriver.html and https://web-platform-tests.org/writing-tests/testdriver-extension-tutorial.html should be updated.

[rakuco]

cc @OrKoN @foolip

[OrKoN]

@rakuco extending testdriver.js with a WebDriver BiDi command does not require an RFC so you should be able to add the testdriver.js wrapper if you need to use the command.

[sadym-chromium]

@rakuco even though we will happily extend the documentation, I wonder what extension of the existing https://web-platform-tests.org/writing-tests/testdriver.html#permissions do you need?

[rakuco]

I wonder what extension of the existing https://web-platform-tests.org/writing-tests/testdriver.html#permissions do you need?

The support for specifying an origin, which only exists in the BiDi endpoint. Without this, it's not possible to set permissions in cross-origin iframes.

[OrKoN]

I think set_permission is a bit special since it exists in both specs. I would suggest to change the implementation in tools/wptrunner/wptrunner/testdriver-extra.js to use the webdriver-bidi endpoint. I guess the third argument can be changed to be a context (window) or an origin (string), and if the context is a window, we take the window.location.origin as the default origin.

[sadym-chromium]

I think set_permission is a bit special since it exists in both specs. I would suggest to change the implementation in tools/wptrunner/wptrunner/testdriver-extra.js to use the webdriver-bidi endpoint. I guess the third argument can be changed to be a context (window) or an origin (string), and if the context is a window, we take the window.location.origin as the default origin.

I assume this comment was done before we figured out, that the switch to WebDriver BiDi transport will be a gradual. I guess we should map the bidi methods to test_driver.bidi... to avoid confusion by different APIs, and to allow for enabling BiDi on-demand.

I created PRs adding test_driver.bidi.permissions.set_permission #49170 and documenting the process #49168. I guess they are addressing the issues you are facing.

Please note that test_driver.bidi is not available yet and is blocked by web-platform-tests/rfcs#214 and its implementation #49122.