visual parity: widest_image_px

Open
#5,870 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
tooling

Research direction

Start by reading tools/import-loop/gates/accept.mjs at the referenced commit, then reproduce the whole-site import and trace the materialization/visual_parity check for widest_image_px. The issue gives no specific file to change; done means a whole re-import lowers this finding’s occurrence count without another blocker appearing or growing, or a visual parity regression on any route or width.

Written by the indexing model from the issue text.

Description

Finding

materialization/visual_parity on widest_image_px, seen in 2 cell(s) of an imported site:

route width evidence
/about/ 768 widest image 705px !== source 711px (Δ-6)
/about/ 1440 widest image 712px !== source 1395px (Δ-683)

Acceptance

This is a whole-site check: it measures the imported site, so there is no reduced page. A fix is accepted when a whole re-import of the capture with the change lowers this finding's occurrence count, with no other blocker appearing or growing and no visual parity regression on any route or width. The import loop's acceptance gate measures exactly that (static-site-importer tools/import-loop/gates/accept.mjs, at 07268b94).

Loop signature: 66d46cf249a7


AI disclosure: filed by the static-site import findings loop (Homeboy workflow on the Lab). The finding, reduction, and body are generated by deterministic scripts; Claude (Anthropic) wrote those scripts with Chris Huber.

Dominant language
PHP
Stars
28
Forks
5
Avg merge
2h 59m
Merged PRs (30d)
942

Getting set up

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.