Maksim Sadym
Maksim Sadym
Add `require_webdriver_bidi` test metadata. TODO: reference RFC
Depends on https://crrev.com/c/6330754. Should be merged AFTER the same functionality is done in ChromeDriver, as otherwise the still visible Mapper tab will be empty.
Spec: https://github.com/w3c/webdriver-bidi/pull/883
`webdriver/tests/bidi/input/perform_actions/pointer_mouse.py:test_click_at_fractional_coordinates` failing after [this change](https://phabricator.services.mozilla.com/D237688).
https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/13238310539/job/36947860092?pr=3099
https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/13008105443/job/36279458949?pr=3044
Step addressing https://github.com/GoogleChromeLabs/chromium-bidi/issues/2757. Remove non-spec compliant BiDi+ commands and events. Prerequisites: * [x] https://github.com/GoogleChromeLabs/chromium-bidi/issues/2840 * [x] https://github.com/GoogleChromeLabs/chromium-bidi/issues/2841 * [x] https://github.com/GoogleChromeLabs/chromium-bidi/issues/2842 * [x] https://github.com/GoogleChromeLabs/chromium-bidi/issues/2843 * [ ] (2025-03-31) Wait 3 Chrome...
WebDriver BiDi specification restricts vendor-specific [extension modules](https://w3c.github.io/webdriver-bidi/#extension-modules) to have a prefix, in case of Chromium it's `goog:`. Currently, [BiDi+](https://github.com/GoogleChromeLabs/chromium-bidi?tab=readme-ov-file#bidi) don't have that prefixes, which makes the implementation not spec compliant....
Currently, the navigation events are based on [some CDP heuristics](https://github.com/GoogleChromeLabs/chromium-bidi/blob/main/src/bidiMapper/modules/context/BrowsingContextImpl.ts#L85-L106), which do not always allow for proper events emitting and commands results. ### Related documents * [Chromium BiDi navigation overview](http://goto.google.com/webdriver:bidi-navigation)...