Send input actions over WebDriver BiDi targeting a specific browsing context, as a lower-level alternative to element-targeted Actions

domain: selenium.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Enable BiDi on the session in the browser Options for your language binding, since it is not on by default
  2. Construct the BiDi input module against the driver, and obtain a browsing-context ID (e.g. the window handle) to target
  3. Build one or more action sequences with the normal Actions builder, retrieve its underlying sequences, and pass them to the BiDi input module's perform call together with the context ID, targeting a context rather than a single WebElement
  4. Call the module's release function afterward to reset key/pointer state for that context
  5. Reach for this path when input needs to target a browsing context directly rather than being tied to one element, as with the classic element-scoped Actions API

Known gotchas

Related routes

Subscribe to browsingContext DOM content loaded and navigation events with Selenium 4 BiDi
selenium.dev · 6 steps · unrated
Intercept and modify HTTP requests and responses using Selenium 4 WebDriver BiDi addIntercept
selenium.dev · 6 steps · unrated
Check Puppeteer's documented WebDriver BiDi support before relying on it, since Chrome and Firefox support differ and some CDP-parity features aren't yet implemented over BiDi
pptr.dev · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans