You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a list widget configured with types, reordering the list items via drag-and-drop breaks the data connection for any markdown widgets inside those items.
If the markdown widgets have the same name, i.e. two instances of the same object, the state bleeds between the two. If the objects have different names but both contain markdown fields. The bug report CMS config examples allow you to test both the freeze and state bleed issues. I have included videos of both in action.
In some cases, the editor pane correctly updates the underlying file. The user must save and reload to restore the live preview.
Note: I have explicitly added a unique id field that gets used as the React key for each block to ensure the issue does not lie with simply missing unique keys. The bug persists even with stable keys.
To Reproduce
Create a list widget in config.yml that uses two variable types.
Inside both of those types, include a markdown widget.
Create a custom preview template and render the markdown widgets.
In the CMS editor, add two list items.
Drag and drop the list items to swap their order.
Attempt to type inside a markdown widget in the editor pane.
Expected behavior
After reordering typed list elements, the markdown fields within continue to render the correct contents in the preview.
Describe the bug
When using a list widget configured with types, reordering the list items via drag-and-drop breaks the data connection for any markdown widgets inside those items.
If the markdown widgets have the same name, i.e. two instances of the same object, the state bleeds between the two. If the objects have different names but both contain markdown fields. The bug report CMS config examples allow you to test both the freeze and state bleed issues. I have included videos of both in action.
In some cases, the editor pane correctly updates the underlying file. The user must save and reload to restore the live preview.
Note: I have explicitly added a unique id field that gets used as the React key for each block to ensure the issue does not lie with simply missing unique keys. The bug persists even with stable keys.
To Reproduce
Expected behavior
After reordering typed list elements, the markdown fields within continue to render the correct contents in the preview.
Screenshots
Freeze
Screen.Recording.2026-08-10.at.14.36.38.mov
State bleed
Screen.Recording.2026-08-10.at.14.09.32.mov
Applicable Versions:
CMS configuration
Additional context
Preview