visual parity: text_content

Open
#5,860 1 comment 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
12/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
php
Domain
tooling

Research direction

The finding comes from the import loop's visual parity check, and acceptance is defined by tools/import-loop/gates/accept.mjs in static-site-importer at commit 07268b94. Start there to see how the occurrence count is measured, then run a whole re-import of the capture for / at widths 390, 768 and 1440. Done means the text_content occurrence count drops with no new blockers and no visual parity regressions.

Written by the indexing model from the issue text.

Description

Finding

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

route width evidence
/ 390 text 642 chars !== source 618
/ 768 text 642 chars !== source 618
/ 1440 text 716 chars !== source 676

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: 673fe72b3463


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.