- Issue created by @kiwad
This issue is closely related to an older one, but it has been adapted for Drupal 10+.
I marked it 2.x but I think everything also applies to 3.x from a test I did on simplytest.me
In Drupal 10/11:
There is no message prompting the user to save the entire form when unsaved changes are detected.
The core “You have unsaved changes…” message triggered by tabledrag reorder disappears when you edit an element—even if there are still unsaved changes.
When using a cardinality of 1 with a complex widget, removing the existing item results in no visible message and no “Add” button. This creates a broken user experience.
In that same case (cardinality 1), if there’s a destination parameter that redirects away from the form after submission, the user has to return manually to re-add the item—this is not an ideal UX.
Again, with cardinality 1, if a validation requires at least one item, the user is blocked from adding a new one because the existing item must be deleted first.
Active
2.0
Code