Library › Book 1 › Protocol Overview
Protocol Overview
17.1🔒What WebDriver BiDi IsWebDriver BiDi (Bidirectional) is a W3C standard for browser automation. It combines the two things that, for most of automation history…
17.2🔒Message TypesEvery BiDi interaction is built from three message types.
17.3🔒The Six Core ModulesBiDi organizes its command surface into modules; the method name tells you the module (browsingContext.navigate, script.evaluate). Six…
17.4🔒Sessions and HandshakesThere are two ways to establish a BiDi session. The standard session starts life as a classic WebDriver HTTP session that asks for a…
17.5🔒Browsing Contexts, User Contexts, and SubscriptionsA "browsing context" is more general than a tab: it covers tabs, iframes, and popup windows. Each has a unique ID, and contexts form a tree:
17.6🔒Browser Support as of July 2026Firefox is the quiet headline: BiDi support is native to the browser, no separate driver binary. Safari remains the laggard -- partial…
17.7🔒Worked Example: The BiDi Proxy PatternThe cleanest illustration of building on top of BiDi is Vibium, the BiDi-native tool from Jason Huggins, the creator of Selenium back in…
17.8🔒Key Takeaways- WebDriver BiDi is the W3C successor to both classic WebDriver and CDP: JSON over WebSocket, with commands, correlated responses, and…
17.9🔒Q&ASelf-Assessment Quiz1. What two properties does BiDi combine that WebDriver and CDP each only had one of? 2. How does a client match a BiDi response to the…
17.10🔒Exercises[Beginner] Exercise 17.1: For each of these agent actions -- navigate, click, run JavaScript, capture console errors, block a request…
17.11🔒Career Translation- Developed protocol-level expertise in WebDriver BiDi (W3C) -- six core modules, message correlation, event subscriptions -- enabling…
17.12🔒Q&AInterview Depth CheckPrompt: Explain how the BiDi event subscription model works and why it matters for AI-driven test automation.