[Feature]: Update chromium-bidi
Maintainers usually reply within 1 day
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
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
🚀 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/...toout/Default/gen/src/..., so the paths inbidiOverCdp.tsmust change.require()still works on the Node.js versions that the package supports (20.19+ and 22.12+). - The
LoggerFntype changed to(type) => ((...messages) => void) | undefined. 159.xreleases useDisposableStack, which Node.js 20 and 22 do not have.tests_bidi.ymluses Node.js 20.158.0.8127-xreleases do not useDisposableStack.
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
agent-triage-done
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/playwright#44264 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44290 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
microsoft/playwright#44288 ·
Maintainers usually reply within 1 day
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Open
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44287 ·
Maintainers usually reply within 1 day
All issues in microsoft/playwright
Similar issues
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nwverse/persona#12800 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WISE-Community/WISE-Client#2404 ·
Maintainers usually reply within 1 day