[Feature]: Update chromium-bidi

Open
#44,036 7 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@pavelfeldman is already working on this.

Since Nov 20, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, typescript
Domain
backend, testing

Research direction

Start by reading bidiOverCdp.ts and tests_bidi.yml, then check the supported chromium-bidi releases and their Node.js compatibility. Update the devDependency and adjust the paths and LoggerFn usage described in the issue. Run the BiDi Chromium tests; done means browser.newContext() and browser.newPage() work and the previously failing tests pass.

Written by the indexing model from the issue text.

Description

milestone
🚀 Feature Request

Update the chromium-bidi devDependency from 12.1.0 to a recent release.

Since 157.0.8080-0, chromium-bidi is built from the Chromium source tree, and its version matches the Chrome version. For example, 158.0.8127-x releases match the bundled Chromium 158.0.8127.18.

Things to know for the update:

  • The package is now ESM only, and its files moved from lib/cjs/... to out/Default/gen/src/..., so the paths in bidiOverCdp.ts must change. require() still works on the Node.js versions that the package supports (20.19+ and 22.12+).
  • The LoggerFn type changed to (type) => ((...messages) => void) | undefined.
  • 159.x releases use DisposableStack, which Node.js 20 and 22 do not have. tests_bidi.yml uses Node.js 20. 158.0.8127-x releases do not use DisposableStack.
Example

No response

Motivation

#43668 (merged on 2026-10-28) changed BidiBrowserContext.initialize() to always send emulation.setMediaFeaturesOverride. [email protected] does not implement this command, so browser.newContext() and browser.newPage() fail on bidi-chromium:

Error: browser.newPage: Protocol error (emulation.setMediaFeaturesOverride): unknown command
Message: Unknown command 'emulation.setMediaFeaturesOverride'.

Since the 2026-10-29 run, about 4,000 bidi-chromium tests fail with this error in the daily tests BiDi workflow. For example, the 2026-11-10 run has 4,007 failed and 883 passed tests: https://github.com/microsoft/playwright/actions/runs/42728590598. This is why the Chrome results dropped on https://firefox-dev.tools/playwright-bidi-dashboard/. The checks on #43668 did not show the problem, because tests_bidi.yml does not run bidi-chromium on pull requests.

Recent chromium-bidi releases implement emulation.setMediaFeaturesOverride. Also, Playwright adds new BiDi commands over time, as #43668 did. With an old chromium-bidi, bidi-chromium fails on these commands even when Chromium supports them, so the dashboard shows less Chromium BiDi support than Chromium really has.

Dominant language
TypeScript
Stars
100k
Forks
6.9k
Avg merge
16h 8m
Merged PRs (30d)
281

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/playwright

All issues in microsoft/playwright

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.