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

Bard: dropdown menu of a newly inserted set closes immediately (can't delete/collapse/duplicate the set)

Cerrado
  • ¿Algo no está bien?
#15,704 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #15709 de @o1y — fusionado

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
laravel, php
Área
backend, frontend

Línea de trabajo

Start by tracing the Bard set dropdown and its node view, then inspect how ProseMirror's DOMObserver handles the aria-hidden attribute mutations described in the issue. Reproduce by inserting a set containing a Grid and opening its menu; compare the newly inserted set with a saved and reloaded set. Done means the menu stays open after insertion and its actions work without losing the node view.

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

Descripción

bard
Bug description

After inserting a new set into a Bard field, the set's "…" dropdown (Collapse / Duplicate / Delete Set) does not open. Clicking the trigger does nothing visible. The same happens for dropdowns inside the set, e.g. the row actions of a Grid field within the set.

Sets that were already saved are not affected. Their dropdown opens normally, even when expanded or after their fields were edited. Once the entry is saved and reloaded, the dropdown of the previously "new" set works again.

Expected: the dropdown opens and the set can be deleted right after inserting it.

What I found while debugging:

  • The set's dropdown is a modal Reka dropdown (DropdownMenuRootContext.modal === true).
  • Clicking the trigger sets open to true. The menu content is mounted into body and removed again in the same tick.
  • At that moment aria-hidden / data-aria-hidden get set on the editor's top-level children (h1, p, h2, … inside .ProseMirror), apparently from the modal "hide others" behaviour.
  • ProseMirror's DOMObserver registers these attribute mutations as DOM changes and marks the range dirty. DOMObserver.flush() → view.updateState() → docView.updateChildren() → destroyRest() then destroys the set's node view. No transaction is dispatched.
  • The Vue component of the set (including the open dropdown) is unmounted and a fresh instance is rendered with the dropdown closed.

So the modal dropdown mutates attributes inside the ProseMirror DOM, ProseMirror re-renders that range, and the re-render destroys the node view that owns the dropdown. For saved sets the node view seems to survive the re-render, which is why only freshly inserted sets are affected.

How to reproduce

  1. Create a Bard field with a set containing a Grid (any fields will do), e.g.:

    handle: text
field:
  type: bard
  sets:
    main:
      sets:
        buttons:
          fields:
            -
              handle: buttons
              field:
                type: grid
                min_rows: 1
                fields:
                  - { handle: label, field: { type: text } }
                  - { handle: link, field: { type: link } }

  2. Open an entry with this field in the CP.

  3. Place the cursor on an empty line in the Bard field and insert the set.

  4. Click the "…" button in the header of the newly inserted set.

  5. The dropdown does not open, so the set can't be deleted, collapsed or duplicated.

  6. Save and reload the entry, then click "…" again. Now the dropdown opens.

Logs
Environment
Environment
Laravel Version: 13.38.0
PHP Version: 8.5.12
Composer Version: 2.10.3
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: Europe/Berlin
Locale: de

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: CACHED
Views: CACHED

Drivers
Broadcasting: null
Cache: file
Database: sqlite
Logs: debug / single
Mail: sendmail
Queue: sync
Session: file

Storage
public/storage: LINKED

Statamic
Addons: 5
License Key: Not set
Sites: 5 (German, English (US), English, Hungary, Spanish)
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.36.0 PRO

Statamic Addons
heidkaemper/statamic-toolbar: 1.7.0
jacksleight/statamic-bard-texstyle: 4.2.4
ndx/statamic-bard-color-picker: 3.1.0
ndx/statamic-simple-redirects: 1.4.0
spatie/statamic-responsive-images: 6.2.0
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

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

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.