Alex Rudenko comments

Results 1168 comments of


                                            Alex Rudenko

browsingContext.traverseCommand does not emit navigation events anymore

cc @sadym-chromium

Add ability to trigger autofill on form elements in webdriver-bidi specs

Please remove me from the WebKittens section as I do not think I am in position to review the spec from the webkit perspective.

Bug: network requests that happen before the page load a sometimes emitted after it

@sadym-chromium @Lightning00Blade do you have thoughts on to solve it? it looks like requestWillBeSentExtraInfo might be delayed and chromium-bidi waits for it.

browsingContext.navigationStarted the URL is always an empty string

Firefox sends the URL where the context is being navigated to, which I believe might not be what Puppeteer expects either.

browsingContext.navigationStarted the URL is always an empty string

I have changed Puppeteer implementation to not rely on the navigationStarted. The issue is still worth fixing though.

browsingContext.navigationStarted the URL is always an empty string

I believe @sadym-chromium you are working on this

Computing the Accessible Backing Node, or a similar test-only interface

I have opened a PR to add ability to query by a11y attributes to https://github.com/w3c/webdriver-bidi/pull/660

[Bug]: offline mode loads remote content in iframe

Can confirm, Puppeteer does turn on the offline mode correctly via CDP but something on the browser side is not working.

run-e2e.mjs and run-bidi-server.mjs should kill child process on exit

I think in general it might be OS-specific but I do not think Node will try to auto-kill child processes.

[Feature]: Easier automation of scrolling by touch

Have you tried https://pptr.dev/api/puppeteer.touchscreen / https://github.com/puppeteer/puppeteer/blob/main/test/src/touchscreen.spec.ts#L207? (if you want to test touches and now the mouse). I believe that would trigger the https://developer.mozilla.org/en-US/docs/Web/API/Document/scroll_event event.