I initially posted this suggestion here as a potential solution to another problem, but I think it bears consideration as an issue in itself: It's confusing and unintuitive to ask users to delete the content of a field value to signify that they want to remove the whole position at that delta. I don't think the action corresponds to the function. Much more logical, in my mind, would be to delete the contents of the INPUT at a position when what you want is a position with an empty value, and create a separate UI element for the (really distinct) function of deleting the whole position from the list—for example, a delete link or button next to each position, as depicted below. Not only would this eliminate ambiguity, it would make the act of deleting a field value both more "findable" and more "intuitive". (What is the new user left to think when there is a button specifically to "Add another item" but no corresponding button to remove one? It would not be unreasonable to assume, at first glance, that you can add but not remove.)
Comment | File | Size | Author |
---|---|---|---|
#7 | unlimitedfield_remove-7.x-0.3.zip | 2.59 KB | shantanu1 |
93447_0.gif | 4.16 KB | TravisCarden |
Comments
Comment #1
TravisCarden CreditAttribution: TravisCarden commentedAdd issue tag.
Comment #2
pgillis CreditAttribution: pgillis commentedI noticed a screen shot, is there a patch that already adds this functionality?
Comment #2.0
pgillis CreditAttribution: pgillis commentedUpdated issue summary.
Comment #3
TravisCarden CreditAttribution: TravisCarden commentedAlas, it's just a Photoshop mockup. Sorry. :)
Comment #4
shantanu1 CreditAttribution: shantanu1 commentedGot any solution?
Comment #5
TravisCarden CreditAttribution: TravisCarden commentedNo, nothing more has come of this. And it seems unlikely at this point that anything will, unless we attack it upstream (where it's still an issue). Let's see if we can get this solved in Core, and then maybe we can backport the fix.
Comment #6
shantanu1 CreditAttribution: shantanu1 commentedYes i am also searching for solution.
Comment #7
shantanu1 CreditAttribution: shantanu1 commentedI got one solution can you can check this also.Please download this module.
Thanks
Shantanu Karmakar
ID:shantanu2683@gmail.com
Comment #8
TravisCarden CreditAttribution: TravisCarden commented@shantanu2683, your solution will have a better chance of getting reviewed if you attach a patch instead of a ZIP file and change the issue status to "needs review".
I see that someone else has contributed a module to address this: Multiple Field Remove Button .
Comment #9
swentel CreditAttribution: swentel commentedDuplicate of #1038316: Allow for deletion of a single value of a multiple value field
Comment #9.0
swentel CreditAttribution: swentel commentedUpdated issue summary.