[Bug]: Full-page screenshots in Chromium lose forcedColors: 'active' rendering, and the page doesn't recover
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- playwright, typescript
- Domain
- backend, testing-qa
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- 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