Skip to content

test: re-add comprehensive.html regression fixture#2260

Open
pankaj443 wants to merge 4 commits into
masterfrom
restore/comprehensive-html-fixture
Open

test: re-add comprehensive.html regression fixture#2260
pankaj443 wants to merge 4 commits into
masterfrom
restore/comprehensive-html-fixture

Conversation

@pankaj443
Copy link
Copy Markdown
Contributor

Summary

Re-adds test/regression/pages/comprehensive.html, which was removed in #2239 ("test: remove unused comprehensive.html regression fixture").

The fixture is restored verbatim from its state prior to deletion (added originally in #2145). It exercises fonts (@font-face), pseudo-class CSS rules (:hover, :focus), and other web features used by the regression suite.

Why

Re-adding the comprehensive regression fixture so it's available again for the regression test pages.

🤖 Generated with Claude Code

Restore the comprehensive regression test page that was removed in
PR #2239. The fixture exercises fonts, pseudo-class CSS rules, and
other web features used by the regression suite.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@pankaj443 pankaj443 requested a review from a team as a code owner June 2, 2026 09:03
pankaj443 and others added 3 commits June 2, 2026 14:50
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The <video> carried a header-only base64 mp4 <source> (a 32-byte ftyp
box with no moov/mdat). It's unplayable and serves no purpose for this
fixture, whose goal is exercising video *poster* handling — serialize-
video.js skips elements that already have a poster attribute, so the
source was never part of any capture path.

The stub engages the browser media pipeline, which the upgraded (v143-
era) Firefox renderer handles differently than v126, causing the
Comprehensive snapshot to fail rendering on Firefox. Removing the
source leaves networkState=EMPTY (no load attempt) in both Chromium and
Firefox while keeping the poster — the actual thing under test.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the header-only/truncated base64 mp4 (a 32-byte ftyp box with no
moov/mdat) with a complete, spec-valid minimal mp4 (ftyp+free+mdat+moov).

The original stub engaged the media pipeline in a way the upgraded
Firefox 146 renderer (percy-renderer #1775, FF 139.0.4 -> 146.0.1) failed
to render, causing the Comprehensive snapshot to time out on Firefox. The
discovery/serialization path is identical across CLI versions (verified:
old v126 and new v143 CLI both timed out), so the fixture must carry media
the renderer can actually parse.

Using a valid source keeps the data-URI video serialization path under
test (serialize-video / serializeBase64) while no longer hanging the
renderer. Locally the video now reports networkState=IDLE with no decode
error in both Chromium and Firefox (the stub reported NO_SOURCE).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

2 participants