non core block: layout-shell@a[data-testid][href][target]

Aperta
  • Qualcosa non va?
#4,888 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@chubes4 ci sta già lavorando.

Dal 7/11/2026.

  • #4904 di @chubes4 — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
46/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php, wordpress
Ambito
backend

Direzione di ricerca

Start with the reduced HTML and reproduce the finding using the provided predicate command from the specified static-site-importer and blocks-engine checkouts. Trace how the PHP transformer handles the generated link inside the logo wrapper and why it emits a non-core block. Done means the content uses core blocks, renders as before, and passes the importer's pixel parity gate; the issue does not identify specific transformer files or tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Finding

editability/non_core_block on layout-shell@a[data-testid][href][target], seen in 2 route/width cell(s) of an imported site:

route width evidence
/about/ 1440 {"route":"/about/","count":1,"of":129}
/ 1440 {"route":"/","count":1,"of":339}

Reduced page (425 bytes)

Reduced from 448939 bytes in 159 predicate calls.

<!DOCTYPE html><html><head><style>#main_MF :where(.comp-dla5b7368da_r_comp-mmc8u23k) { min-height: 0px; }</style></head><body><div id="main_MF"><div class="logo-wrapper _logo_ackza_1 builder-root builder-root comp-dla5b7368da_r_comp-mmc8u23k"><a data-testid="linkElement" href="/index.html" target="_self"><wow-image><img src="/media/c837a6_1f682fef9fae4fe6974f26e1d8173148-mv2.png"></wow-image></a></div></div></body></html>

Reproduce

The predicate exits 0 while the defect reproduces (checked against blocks-engine trunk a06112e4). Run it from a static-site-importer checkout at 8b698851, with the reduced page saved as reduced.html:

PREDICATE_TARGET='{"subject":"layout-shell@a[data-testid][href][target]","route":"/about/","width":1440,"evidence":{"route":"/about/","count":1,"of":129}}' \
  WORDPRESS_PATH=<wordpress with static-site-importer active> WP_CLI='studio wp' \
  node tools/import-loop/predicates/non_core_block.mjs <blocks-engine>/php-transformer reduced.html
predicates/non_core_block.mjs 
// Exit 0 while the Blocks Engine output of a page still emits the generated
// block <prefix>/<subject>, a block outside WordPress core. An editor can only
// change its structure through the importer's own block, not with core tools.
// The defect is gone when the same content is built from core blocks and the
// page renders exactly as before; the acceptance gate holds the whole import to
// pixel parity (see emits.mjs, gates/collateral.mjs).
import { exitWhileEmitted } from './emits.mjs';
exitWhileEmitted();

Loop signature: 9022a2491a6e

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.

Lingua principale
PHP
Stelle
25
Fork
3
Merge medio
2h 29m
PR unite (30g)
931

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Automattic/blocks-engine

Tutte le issue di Automattic/blocks-engine

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.