You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => Search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Sorry, we will not be able to answer every support request. Please consider other venues for support requests
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]
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: