- Status changed to Needs work
over 1 year ago 10:37am 1 February 2023 - 🇫🇮Finland lauriii Finland
I've manually tested the changes in the MR and while I agree that this addresses a usability problem with the lack of clear indication for the drag start, it seems to be causing other, potentially more severe problems. Most notably, if we don't show a preview for the indentation, it seems very hard to predict the outcome of the drag. That is solved by the Sortable UX by having the item "duplicated" during dragging; one for showing a preview of the row and one for indicating the user that they are dragging the item:
- 🇺🇸United States bnjmnm Ann Arbor, MI
The parts I had the most difficulty with in the initial implementation would be much easier with the "duplication" approach offered by Sortable as seen in #11. It looks more intuitive than I expected (and may be a pattern I engage with regularly and don't even realize it)
- 🇫🇮Finland lauriii Finland
Linking few related issues here.
There's some interesting information in #1972462-13: Redesign drag and drop interactions, and nested menu items, for all devices → . It seems like based on the UX researcher who looked at Drupals tabledrag back then, the biggest problem was how difficult it was to use on mobile. Based on that, they recommended to look for alternative ways to re-arrange the table to address the issues with mobile. Wondering if that's something we should look into?