Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Nested Replicator inside Bard set remounts and resets collapsed state on field interaction

Abierto
  • ¿Algo no está bien?
#15,687 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@edalzell ya está trabajando en esto.

Desde el 21/10/2026.

  • #15688 de @edalzell — abierto
  • #15690 de @edalzell — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
laravel, php
Área
backend

Línea de trabajo

Start by tracing the Bard NodeView attribute sync and the Replicator initialization from node.attrs.values and meta.collapsed; the issue does not name source files or tests. Reproduce the nested Bard → set → Replicator → Grid interaction and inspect whether a remount resets expanded state. Done means editing a nested field preserves the expanded set.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bard fieldtypes

Bug description

When a Replicator (with collapse: true) lives inside a Bard set, interacting with nested fields (e.g. Grid stacked rows, nested Bard) destroys and remounts the parent Bard NodeView. The nested Replicator re-initializes from meta.collapsed, which still lists every set as collapsed from page load, so an expanded set snaps shut.

This makes nested page-builder blocks (Accordion / FAQ style sets with Grid + Bard inside) very hard to edit: open the set, click a field inside, the whole set collapses.

How to reproduce

  1. Bard field with a set that contains a Replicator (collapse: true).
  2. That Replicator set contains a Grid (stacked) and/or nested Bard fields.
  3. Edit an entry, expand one Replicator set.
  4. Click into a nested field (heading input, ProseMirror, field header, etc.).
  5. Observe: the Bard NodeView / Replicator DOM is remounted (data-replicator-set node replaced), and the set is collapsed again.
Evidence from debugging
  • After expand: data-collapsed="false".
  • After clicking nested UI: previous set node is gone (document.contains(oldNode) === false), new node mounts with data-collapsed="true" when collapse: true.
  • The Replicator set header toggle button does not receive the click; collapse comes from remount + collapsed: clone(this.meta.collapsed) re-init.
  • Workaround: collapse: false on the nested Replicator — remount still happens, but sets stay open.

Expected behaviour

Expanding a nested Replicator set should survive interaction with its own fields. Collapsed state (and preferably the set DOM) should not reset when nested values cause the parent Bard set NodeView to sync/remount.

Environment

  • Statamic 6.36.0
  • Reproduced in Chromium (Cursor browser) against a Prime site page-builder Bard → set → Replicator → Grid/Bard nest

Related

Possibly related to Bard NodeView attr sync / remount behaviour when nested publish values change (watcher updating node.attrs.values).

Lenguaje dominante
PHP
Estrellas
4.9k
Forks
647
Merge medio
1 d 13 h
PR fusionados (30 d)
133

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de statamic/cms

Todos los issues de statamic/cms

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.