Run parity fixtures at more than one viewport

Open
#1,893 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
php
Domain
ci-cd, testing

Research direction

Start with the existing parity fixture harness and the geometry assertions used by the 311 fixtures. Trace how fixtures are opted in and run the current parity suite, then add desktop and small-viewport coverage only for opted-in fixtures. Done means responsive geometry is asserted at both viewports and the existing fixtures still pass.

Written by the indexing model from the issue text.

Description

All 311 parity fixtures passed through #1854, #1865, #1872, #1879 and #1883. Every one of those was a real, visible defect on an imported site, and parity never saw them, because fixtures render at a single width.

Two would have failed immediately at 390px:

  • #1865 — headings baked the desktop size, so a 48px mobile heading rendered at 72px and the page ran 311px long
  • #1879 — a md:hidden menu button rendered at every width and took a slot in its parent's flex row

This is a harness change, not an engine change, and it converts a whole bug class from found by a human importing a real site into caught by CI.

Proposal: render each fixture at a desktop and a small viewport and assert geometry at both. Start by opting fixtures in, so the cost is paid only where responsive behaviour matters.

Highest leverage of the five pillars, and the one that makes the others verifiable.

AI assistance: analysis by Claude Sonnet 4.6 via opencode, derived from five fixes landed while importing a live Tailwind v4 site. Reviewed before filing.

Dominant language
PHP
Stars
15
Forks
2
Avg merge
2h 21m
Merged PRs (30d)
796

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/blocks-engine

All issues in Automattic/blocks-engine

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.