Captured gallery frames with responsive capture classes lose their frame attributes
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 50/100
Direzione di ricerca
Start where responsive capture classes cause a layout-shell wrapper to keep only class, and check why the data-blocks-engine-capture-gallery-* attributes are dropped there, while the homepage slideshow without those classes keeps them. Add a neutral two-frame captured gallery fixture whose frame 0 has responsive classes, then confirm data-blocks-engine-capture-gallery-frame="0" survives on the emitted wrapper. Done when next/previous steps through both frames with the gallery runtime kept.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
When a captured gallery's visible frame carries responsive capture classes, its frame wrapper is lowered to a layout-shell that keeps only class; the capture gallery attributes on that wrapper are dropped:
<div class="slides" data-blocks-engine-capture-gallery-stage data-blocks-engine-capture-gallery-initial="0">
<div class="slide data-blocks-engine-capture-responsive-…" data-blocks-engine-capture-gallery-frame="0" data-blocks-engine-capture-gallery-image="/media/a.jpg" data-blocks-engine-capture-gallery-display="block" data-blocks-engine-capture-gallery-text="[]">…<img src="/media/a.jpg">…</div>
<div class="slide data-blocks-engine-capture-responsive-…" data-blocks-engine-capture-gallery-frame="1" … hidden>…<img src="/media/b.jpg">…</div>
</div>
In a Studio import of a captured site built on a hosted site builder, one blog post's two-frame slideshow is emitted with frame 1 still carrying data-blocks-engine-capture-gallery-frame="1", but frame 0's wrapper is now <div class="wp-block-group slide data-blocks-engine-capture-responsive-… blocks-engine-attribute-…"> with no data-blocks-engine-capture-gallery-* attributes.
Effect at 1440: the kept capture gallery runtime sees only one frame. The gallery root is 13px tall with no visible frame on load, and clicking Next shows frame 1 and then stays there. Previous does not step back. The homepage slideshow on the same site, whose frames carry no responsive classes, keeps every frame attribute and steps correctly.
This happens with php-transformer v0.41.19 and current trunk. It is independent of #2883, which concerns the direction controls.
Expected
Every captured gallery frame keeps the gallery frame contract (…-gallery-frame, …-gallery-image, …-gallery-display, …-gallery-text, hidden) on the block that owns the frame, whatever presentation classes the frame carries. The kept runtime should then step through all captured frames.
Acceptance
- A neutral fixture of a two-frame captured gallery where frame 0 carries responsive capture classes keeps
data-blocks-engine-capture-gallery-frame="0"on its emitted wrapper. - With the gallery runtime kept, next/previous cycles through both frames.
AI disclosure: Claude (Anthropic) via Claude Code investigated and drafted this under Chris Huber's direction; operator-authorized direct fallback outside Homeboy.
- Lingua principale
- PHP
- Stelle
- 21
- Fork
- 2
- Merge medio
- 8h 50m
- PR unite (30g)
- 609
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Automattic/blocks-engine
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Automattic/blocks-engine#3090 ·
I maintainer di solito rispondono entro 1 giorno
-
Solved site promotion gate fails on runner PHP patch drift (expects 8.2.33, runner installs 8.2.34)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Automattic/blocks-engine#2161 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Automattic/blocks-engine#2061 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Automattic/blocks-engine#1701 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Automattic/blocks-engine#775 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di Automattic/blocks-engine
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
grokability/snipe-it#19869 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 77/100
I maintainer di solito rispondono entro 3 giorni
-
Перевод устарел
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 74/100