[Feature]: Update chromium-bidi

Abierto
#44,036 7 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@pavelfeldman ya está trabajando en esto.

Desde el 20/11/2026.

  • #44278 de @OrKoN — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
65/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
backend, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
100k
Forks
6.9k
Merge medio
16 h 8 min
PR fusionados (30 d)
281

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.