Can't grab a Kanban item for reordering or moving buckets #1815
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1815
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I think this issue may have been introduced with the List view drag & drop reordering, but I can no longer grab a Kanban item to pick it up to drag it anywhere. This affects reordering in Kanban and also moving items between buckets.
Affects both mobile and desktop web.
What version? What device + browser (with version)? Reproducable on try?
Latest version as of this morning.
On desktop (Windows 10), I'm using Brave Version 1.26.74 (Chromium 91.0.4472.124).
On mobile (Android), I'm using Chrome Version 92.0.4515.115.
Reproduced on try.
I wasn't able to reproduce this on either brave desktop in a windows 10 vm nor on a chrome android in your version.
Have you tried long pressing a task card on kanban?
After trying to move cards for a while, it sometimes works. But I'd say about 3/4 of the time it does not.
** time passes **
I think I've figured it out. If my mouse is moving, even slightly, when I click on an item, it will not be "picked up". I have to be absolutely still when clicking in order to move an item.
Summary: "drive-by clickings" do not work. I'm sure they used to, because I never used to have to concentrate on being absolutely still before clicking on an item.
Other than that, I don't know what I was seeing...mobile seems to be working for me now. Maybe it was a caching issue.
Mhhh that might be caused by the delay I put in for mobile - without that you can't really use the board at all on mobile. I'll take a look.
I've just pushed a possible fix in
e3787b9496which only sets the delay when on mobile instead of setting a delay of 0 on desktop. Please test that one to see if it fixes the issue for you (should be ready to test on try in ~20min).I'd consider this solved with the fix, feel free to reopen or ping if you still have issues with it.