Skip to content

fix: stabilize README screenshot rendering - #121

Merged
vitormattos merged 1 commit into
mainfrom
fix/deterministic-readme-screenshot
Sep 22, 2026
Merged

vitormattos merged 1 commit into
mainfrom
fix/deterministic-readme-screenshot

Conversation

@vitormattos

Copy link
Copy Markdown
Member

This reduces false positives in the README screenshot check without increasing the pixel tolerance.

The screenshot generator now waits for web fonts to be ready, waits for two animation frames after the final UI state, and disables animations during capture.

This is based on the failure observed in #119, where the same pinned Playwright image produced a 0.7136% visual difference even though the PR only changed @types/node.

The existing 0.1% tolerance is intentionally kept unchanged so real visual regressions are not hidden.

@vitormattos
vitormattos requested a review from a team as a code owner September 21, 2026 22:46
github-actions Bot added a commit that referenced this pull request Sep 21, 2026
github-actions Bot added a commit that referenced this pull request Sep 21, 2026
@github-actions

Copy link
Copy Markdown

README screenshot check failed

The generated README screenshot differs from the committed version.

Expected

Expected screenshot

Generated

Generated screenshot

Diff

Visual diff

If the visual change is expected, run npm run screenshots:update and commit the updated screenshot.

github-actions Bot added a commit that referenced this pull request Sep 21, 2026
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
vitormattos force-pushed the fix/deterministic-readme-screenshot branch from 021d259 to 7315bac Compare September 22, 2026 00:53
@vitormattos
vitormattos merged commit 807c135 into main Sep 22, 2026
6 checks passed
@vitormattos
vitormattos deleted the fix/deterministic-readme-screenshot branch September 22, 2026 00:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant