Maksim Sadym
Maksim Sadym
This is Puppeteer implementation, specifically `connectBidiOverCdp`: https://github.com/puppeteer/puppeteer/blob/bfd41286d2f04d3aebf6df79116f97e75ec8314b/packages/puppeteer-core/src/bidi/BidiOverCdp.ts
I believe this PR can be closed, as using extension to run Mapper is not feasible.
Closing for now, as not reproducible.
It looks like this is what WebDriver BiDi specifies to do: 1. Puppeteer sends he command **'browsingContext.navigate'** with **wait: 'interactive'** and **url: 'https://x.com'**. The navigation will be finished on **'domContentLoaded'**...
Spec: * [`browsingContext.navigate`](https://w3c.github.io/webdriver-bidi/#command-browsingContext-navigate) * [Aawait a navigation](https://w3c.github.io/webdriver-bidi/#await-a-navigation): * [Navigate](https://html.spec.whatwg.org/multipage/browsing-the-web.html#navigate) navigable... * [navigate](https://html.spec.whatwg.org/#navigate), step 22.3: [abort a document and its descendants](https://html.spec.whatwg.org/#abort-a-document-and-its-descendants) given navigable's [active document](https://html.spec.whatwg.org/#nav-document). * [Abort a document and its...
types roll: https://github.com/GoogleChromeLabs/chromium-bidi/pull/2386
@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?
> 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...
It is documented now