Maksim Sadym
Maksim Sadym
https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/11664960578/job/32476607089 [chromedriver-headful-1.6-artifacts.zip](https://github.com/user-attachments/files/17619643/chromedriver-headful-1.6-artifacts.zip) ``` ▶ Unexpected subtest result in /webdriver/tests/bidi/browsing_context/navigate/error.py: │ FAIL [expected PASS] test_with_new_navigation │ → Failed: DID NOT RAISE │ │ bidi_session = │ subscribe_events = │ inline =...
Example: https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/11386575484/job/31679154398?pr=2698 ``` Tests with unexpected results: ▶ Unexpected subtest result in /webdriver/tests/bidi/input/perform_actions/queue.py: │ FAIL [expected PASS] test_parallel_key │ → KeyError: 'code' │ │ bidi_session = │ top_context = {'children':...
wpt-metadata/mapper/headless/webdriver/tests/bidi/session/subscribe/events.py.ini
### Is your feature request related to a problem? In order to run chromium-based browser, I need both browser binaries and chromedriver. However, chromedriver is not required, as [Chromium BiDi](https://github.com/GoogleChromeLabs/chromium-bidi)...
Spec: https://github.com/w3c/webdriver-bidi/pull/924
As discussed in https://github.com/w3c/webdriver-bidi/issues/795, the actions should be dispatched from the top-level browsing context. *** Preview | Diff
Alternative to https://github.com/w3c/webdriver/pull/1847, keeping the event dispatch implementation-specific. *** Preview | Diff