Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Product-card JS controls stay raw HTML after the product grid resolves through the shop provider

Aperta
  • Qualcosa non va?
#3,389 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

Start by tracing the html_product_grid_fallback resolution path through the WooCommerce provider and how product-card buttons are classified as core/html. Read related issues #3328, #3255, and static-site-importer#2331 for existing mapping decisions. Determine whether add-to-cart controls should map to a provider button and how wishlist toggles should be represented; done means both controls have an agreed handling that passes the quality gate.

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

Descrizione

Summary

Product-card controls whose behavior comes from page JavaScript stay raw HTML blocks and fail the quality gate as interactive_control_behavior_lost (client_event_handler), even after the product grid itself is resolved by the shop provider (WooCommerce, resolved_by_provider).

Reduced reproduction

Three identical cards in a grid:

<article class="card"><h3>Headphones</h3><p>$299</p>
  <footer>
    <button class="btn" data-action="add-to-cart">Add to Cart</button>
    <button data-action="toggle-wishlist" aria-pressed="false" aria-label="Add to wishlist"><svg>…</svg></button>
  </footer>
</article>

Observed on a real import (a 16-route site): the html_product_grid_fallback resolves through WooCommerce, yet the 6 card buttons remain core/html (block_grammar). They count as 6 of the 11 unsupported fallbacks that fail the gate.

Open design questions

  1. Inside a provider-resolved product loop, should the card's add-to-cart control map to the provider's native product button (for example woocommerce/product-button), in line with #3328 and static-site-importer#2331 for product pages?
  2. A toggle with aria-pressed and no platform equivalent (wishlist): should it be an editable static core/button with an accepted editable_approximation diagnostic, or stay a preserved runtime island?

Related: #3328, static-site-importer#2331, #3255.

Filed by Claude Opus (Pi coding agent, via Roadie) from an import investigation.

Lingua principale
PHP
Stelle
22
Fork
2
Merge medio
7h 59m
PR unite (30g)
674

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.