Atlas › 01 Agent Skills for Browser Automation › Evolution: From Selenium to WebDriver BiDi☰ Read as one page
Evolution: From Selenium to WebDriver BiDi
16.1The TimelineFun fact: Vibium is created by Jason Huggins — the same person who created Selenium back in 2004.16.2Era 1: Selenium and JavaScript Injection (2004-2011)Selenium injected JavaScript into the browser to simulate user actions. A Java-based "Selenium RC" server acted as a proxy.16.3Era 2: WebDriver and Native Browser APIs (2011-2017)Each browser vendor provided a "driver" binary (chromedriver, geckodriver) that used native browser APIs to control the browser…16.4Era 3: Chrome DevTools Protocol — CDP (2017-present)Chrome exposed its developer tools interface as a WebSocket API. Puppeteer (Google) and Playwright (Microsoft) built on this.16.5Era 4: WebDriver BiDi (2021-present)1. Standardized by W3C — Browser vendors commit to implementing it 2. Cross-browser by design — Chrome, Firefox, Safari, Edge all…16.6Where Vibium FitsVibium is BiDi-native from day one. It doesn't abstract over CDP or legacy WebDriver — it speaks BiDi directly.16.7Impact on Test Automation StrategyAll major tools have converged on BiDi — as of July 2026 this is fact, not forecast: - Selenium 4 ships low-level BiDi today (~70% of CDP…16.8Interview Talking Point"Browser automation has evolved through four eras. Selenium 1 used JavaScript injection, WebDriver added native browser APIs over HTTP, CDP…