[Feature]: Update chromium-bidi
Los mantenedores suelen responder en 1 día
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
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
🚀 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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 100k
- Forks
- 6.9k
- Merge medio
- 16 h 8 min
- PR fusionados (30 d)
- 281
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
microsoft/playwright#44289 ·
Los mantenedores suelen responder en 1 día
-
agent-triage-done
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
microsoft/playwright#44264 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG] WebKit keeps every removed iframe's JS heap alive (memory grows until the page crashes)Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 12/100
microsoft/playwright#44290 ·
Los mantenedores suelen responder en 1 día
-
[Regression]: requestFullscreen() in a popup rejects with "not granted" in 1.65 (Chromium 159)Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
microsoft/playwright#44288 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 12/100
microsoft/playwright#44287 ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/playwright
Issues similares
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
openclaw/openclaw#203385 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nwverse/persona#12800 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 Medio día Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
WISE-Community/WISE-Client#2404 ·
Los mantenedores suelen responder en 1 día