Open artemisclyde opened 4 years ago
Unfortunatly this will not happen untill we stop using dragula under the hood. It's on the roadmap... but no timeline yet.
Unfortunatly this will not happen untill we stop using dragula under the hood. It's on the roadmap... but no timeline yet.
I'll follow the progress on dropping dragula then. Thanks for the reply!
I'm submitting a ...
Current behavior
Click-and-hold on a draggable element and moving the cursor slightly (1px) starts dragging. This often leads to false dragging when a user only tries to select an element but accidentally moves the cursor by just a pixel.
Expected behavior
A draggable element should have a threshold of either milliseconds or pixels of movement after which dragging is started. This way accidental dragging could be reduced greatly. For comparison, Google Drive now also has a very small but notably helpful threshold for dragging. Before that, only dragging for selected elements was enabled to avoid these accidental draggings, which I also did in our project. A threshold would be a much better UX though.
Please tell us about your environment:
ngx-dnd version: 8.1.0
Angular version: 8.2.14
Browser: [Chrome | Firefox | Safari]
Language: [TypeScript 3.5.3]