Karl Seguin 766c0d05d6 bidi: protocol selection CLI, start of [classic] WebDriver ...

In order to support Selenium the way people are used to, it looks  like we need
to support both WebDriver classic (WebDriver) and WebDriver BiDi (BiDi). Typical
scripts look like a mix of the two, e.g. using WebDriver to control the browser
and using BiDi  to receive notifications. This commit:

1 - adds a --protocol (cdp|webdriver) CLI argument to the `serve` command to
    enable one or the other protocol (defaulting to CDP)

2 - adds basic WebDriver endpoint to let a Selenium client connect. This
    implementation is hackish and sits on top of our simple Handshake handler.

The handshake handler is well past its original design. Serving /json/version
and /metrics from it was one thing. But Driving the entire browser session? This
will get a follow up PR.

2026-08-31 22:45:15 +08:00

..

agent-regression.yml

agent regression explictly load workers and iframes

2026-08-27 18:32:36 +08:00

cla.yml

ci: pin github actions to commit shas

2026-07-20 14:56:59 +02:00

e2e-integration-test.yml

ci: pin github actions to commit shas

2026-07-20 14:56:59 +02:00

e2e-test.yml

bidi: protocol selection CLI, start of [classic] WebDriver

2026-08-31 22:45:15 +08:00

package-debian.yml

ci: pin github actions to commit shas

2026-07-20 14:56:59 +02:00

plumber.yml

ci: add plumber to watch workflow security

2026-07-20 15:12:58 +02:00

release.yml

ci: increase release build timeout 20 -> 30

2026-08-26 15:32:21 +02:00

wpt.yml

chore: bump WPT --max-mem from 100 to 200

2026-08-13 21:06:31 +08:00

zig-test.yml

ci: pin github actions to commit shas

2026-07-20 14:56:59 +02:00