The Future of Cross-Browser Automation: WebDriver BiDi
summary
WebDriver BiDi claims to combine WebDriver’s cross‑browser compatibility with CDP’s bi‑directional messaging and fine‑grain low‑level control, using a new Web standard backed by vendors including Apple and Mozilla. Implementation follows spec → verification test suites → browser implementations; status is trackable per browser. It targets faster, event‑driven automation (no polling) and ergonomic test APIs; project is work‑in‑progress so tools will adopt at different speeds and early integration will reveal any remaining gaps.
AI-written summary · about
chapters (8)
- 0:00Introduction to WebDriver BiDi
- 1:06How browser automation works
- 2:32WebDriver protocol explained
- 4:00Chrome DevTools Protocol (CDP)
- 6:28Limitations of existing protocols
- 7:30Introducing WebDriver BiDi
- 8:36WebDriver BiDi development status
- 9:38Why you should care about BiDi
related talks
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...
24mWebDriver BiDi: work in progress.- 31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
33mBeyond WebDriver!
26mHow browser automation works behind the scenes
42mAdvancing WebDriver BiDi support in WebKit
15mBrowser automation/testing with BiDi and minimal dependencies
25mKeynote: What's New in Web Standards