Maksim Sadym

Results 89 comments of Maksim Sadym

The fragmentNavigated is emitted on the history updates that are not fragment navigations

Verified in https://github.com/GoogleChromeLabs/chromium-bidi/pull/3508

Clarify "dispatch action chain" behavior when executed within a frame

This issue is not about the coordinates, but rather about the origin of the event, right?

[Feature]: Implement file dialog automation for WebDriver BiDi

* Requires Chrome `135.0.7029.0` or later. * Requires chromium-bidi [3.0.0](https://github.com/GoogleChromeLabs/chromium-bidi/pull/3191) or later.

[Feature]: Implement file dialog automation for WebDriver BiDi

Addressed: https://wpt.fyi/results/webdriver/tests/bidi/browsing_context/navigation_started/navigation_started.py?run_id=5122897422319616&run_id=6246211372974080&run_id=6203227138949120

Invoke WebDriver BiDi history updated

LGTM (I'm not a committer, so cannot formally approve it)

feat(bidi): remove non-spec-compliant bidi commands

Removing deprecated channel should be done after 2025-03-31, so that give everyone using it some time to switch to the new API

feat(bidi): remove non-spec-compliant bidi commands

This TODO should be addressed as well: https://github.com/GoogleChromeLabs/chromium-bidi/blob/a18cd6f567fc395e25904b84d5b74af464f0ec6d/src/protocol/chromium-bidi.ts#L154

feat(bidi): remove non-spec-compliant bidi commands

> @sadym-chromium Please review this PR and share the valuable feedback please fix rebase first before I can review the PR. Also please note that even after completion, this PR...

feat(bidi): remove non-spec-compliant bidi commands

Addressed in #3288 and #3289