[Bug]: Full-page screenshots in Chromium lose forcedColors: 'active' rendering, and the page doesn't recover
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- playwright, typescript
- Área
- backend, testing-qa
Línea de trabajo
The reproduction uses page.screenshot() and expect(locator).toHaveScreenshot() with Chromium and forced colors; the report points to Page.captureScreenshot with captureBeyondViewport: true. Start by tracing full-page screenshot capture and forced-colors emulation in Chromium. Reproduce with the provided test in the Playwright 1.65.0 Chromium project; done means full-page captures preserve forced-colors rendering and the page remains in that rendering afterward.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Version
1.65.0
Steps to reproduce
import { expect, test } from '@playwright/test'
test.use({ colorScheme: 'dark', forcedColors: 'active' })
test('forced colors survive a full-page screenshot', async ({ page }) => {
await page.setContent('<p>Text</p><div style="height: 3000px"></div>')
const bodyColor = () => page.evaluate(() => getComputedStyle(document.body).color)
expect(await bodyColor()).toBe('rgb(255, 255, 255)')
await page.screenshot()
expect(await bodyColor()).toBe('rgb(255, 255, 255)')
await page.screenshot({ fullPage: true })
expect(await bodyColor()).toBe('rgb(255, 255, 255)')
})
Run with the Chromium project in mcr.microsoft.com/playwright:v1.65.0-jammy.
Expected behavior
The page keeps forced-colours rendering after every screenshot, and the full-page screenshot is drawn with forced colours.
Actual behavior
- The viewport screenshot is fine.
- The full-page screenshot comes out without forced colours: normal colours on a white background.
- After it, the page stays out of forced-colours rendering. Body text is
rgb(0, 0, 0)instead ofrgb(255, 255, 255), and later viewport screenshots are wrong too. matchMedia('(forced-colors: active)').matches stillreturns true throughout. Only the rendering is lost, not the media query.
The same thing happens with expect(locator).toHaveScreenshot() when the element is taller than the viewport. That's how we found it: all our high-contrast visual regression snapshots came out in light mode after upgrading.
Additional context
- It seems to happen whenever Playwright sends
Page.captureScreenshotwithcaptureBeyondViewport: true(when the capture doesn't fit the viewport). Screenshots that fit the viewport are unaffected. - The screenshot code (
captureBeyondViewport: !fitsViewport) and the media emulation code look the same in 1.58.2 and 1.65.0. Our snapshots rendered correctly with 1.58.2 (Chromium 145), which suggests a change in Chromium rather than in Playwright. - Emulation works correctly without the full-page capture, with either
forcedColorsset directly orcontextOptions: { forcedColors: 'active' }.PLAYWRIGHT_LEGACY_SCREENSHOT=1makes no difference to a viewport-sized capture. We haven't tried it with a full-page capture. - We haven't tested Firefox, WebKit, or Playwright 1.64.
- #15211 is a different bug, but is in a similar area.
Environment
- Operating System: Ubuntu 22.04 (mcr.microsoft.com/playwright:v1.65.0-jammy)
- Browser: Chrome Headless Shell 158.0.8127.18
- @playwright/test: 1.65.0
- 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