~/talk

Revolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium

links:none on file
slides:none on file

WebDriver BiDi promises a single, event-driven protocol that merges CDP-style low‑level control with WebDriver’s cross‑browser reach, using WebDriver BiDi over bi-directional via WebSockets to send events and receive console errors in real time. Selenium, WebDriverIO and Puppeteer already offer initial support; Web Platform Tests show browsing context passes ~444/482 in Chrome while Edge network is 2/16. Network interception is noted as not implemented (15 Sep); demos catch JS exceptions and assert them successfully.

AI-written summary · about

  1. 0:00Browser automation challenges
  2. 1:04Automation testing issues
  3. 2:08Browser automation history
  4. 3:54High-level vs low-level
  5. 6:43WebDriver Classic protocol
  6. 12:42Chrome DevTools Protocol
  7. 17:21Merging protocols into BiDi
  8. 19:30Implementing WebDriver BiDi
  9. 21:17Demo: real-time JS errors
  10. 23:46Network interception with BiDi
  11. 25:11Accessibility testing with BiDi
  12. 28:26BiDi future features
  13. 30:17Conclusion & Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.