-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[D8][UX] Multi-value field items should offer some way for individual values to be removed #2917
Comments
There's also a ticket for including this functionality in D8.5 core: https://www.drupal.org/project/drupal/issues/1038316 ...last comment there (a few days ago) is talking about using AJAX vs checkboxes too. I would like to know what people think with regards to what would be the best solution UX-wise. I'm obviously voting for the checkbox, non-AJAX way, because I think that it would be the less complicated and less bug-prone one, plus it would be more straight forward to the user as to what is happening (compared to the removed-from-the-form-changes-not-actually-saved approach that is). |
...added this issue to the list in #378 |
We seem to already have remove buttons for multi-value image fields. How do these work? |
...good catch @Graham-72 👍I have tested this with a link field: We should adapt/abstract the code used in the image multi-value field, so to work with all multi-value fields. |
...I am classifying this as a UX bug. |
I use the Multiple Fields Remove Button module often, +1 for this idea from me. |
This looks like a duplicate of #314 |
This is one of the many, tiny things that has been annoying me in the Drupal (and thus inherently Backdrop) UI for years:
There are currently two modules that address this issue:
Multiple Fields Remove Button:
Field Remove Item:
Both of these modules work the same, in that once the user clicks on either the button or the checkbox, the entry is removed in an AJAXy way. This action removes the item only from the form; there is no actual removal unless the user saves the form. I think that in our implementation, entries should be "marked" for removal, but still remain visible on the form, giving the user the option to change their mind and undo. Perhaps a list of checkboxes in a "remove" column would be more similar to other places in our UI, and thus a familiar UI pattern for the end user.
The text was updated successfully, but these errors were encountered: