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
First of all thank you for maintaining this library!
Description:
On desktop platforms (e.g., macOS and Windows), dragging is disabled if the user holds the mouse button down for too long before starting to move the pointer. This behavior is inconsistent with native drag-and-drop implementations on these platforms and deviates from the same functionality observed on mobile platforms.
Steps to Reproduce:
1. Use the sample app provided by the super_drag_and_drop library.
2. On macOS or Windows:
• Press and hold the left mouse button on a draggable item for more than 1 second.
• Attempt to drag the item after the hold.
3. Observe that dragging does not start, and the drag operation is effectively canceled.
Expected Behavior:
• Dragging should remain enabled regardless of how long the user holds the mouse button, as long as they eventually move the pointer.
• This is the behavior observed in native macOS apps (e.g., Finder, Photos) and Windows apps (e.g., File Explorer).
Actual Behavior:
• Dragging is disabled after a long mouse hold, even though the pointer is eventually moved.
• This issue is not present on mobile platforms, where long presses correctly transition into drag gestures.
Platform Comparison:
1. macOS Native (e.g., Finder):
• Users can hold the mouse indefinitely before initiating a drag by moving the pointer.
2. Windows Native (e.g., File Explorer):
• Dragging is similarly not time-restricted. Holding the mouse button and moving the pointer afterward starts the drag.
Impact:
• This issue disrupts the user experience on desktop platforms, making the library inconsistent with native behaviors and potentially unsuitable for apps requiring accurate drag-and-drop functionality.
I believe that addressing this bug would improve libraries utility for desktop applications. Let me know if additional details or debugging logs are needed to assist in resolving the issue.
The text was updated successfully, but these errors were encountered:
First of all thank you for maintaining this library!
Description:
On desktop platforms (e.g., macOS and Windows), dragging is disabled if the user holds the mouse button down for too long before starting to move the pointer. This behavior is inconsistent with native drag-and-drop implementations on these platforms and deviates from the same functionality observed on mobile platforms.
Steps to Reproduce:
1. Use the sample app provided by the super_drag_and_drop library.
2. On macOS or Windows:
• Press and hold the left mouse button on a draggable item for more than 1 second.
• Attempt to drag the item after the hold.
3. Observe that dragging does not start, and the drag operation is effectively canceled.
Expected Behavior:
• Dragging should remain enabled regardless of how long the user holds the mouse button, as long as they eventually move the pointer.
• This is the behavior observed in native macOS apps (e.g., Finder, Photos) and Windows apps (e.g., File Explorer).
Actual Behavior:
• Dragging is disabled after a long mouse hold, even though the pointer is eventually moved.
• This issue is not present on mobile platforms, where long presses correctly transition into drag gestures.
Platform Comparison:
1. macOS Native (e.g., Finder):
• Users can hold the mouse indefinitely before initiating a drag by moving the pointer.
2. Windows Native (e.g., File Explorer):
• Dragging is similarly not time-restricted. Holding the mouse button and moving the pointer afterward starts the drag.
Impact:
• This issue disrupts the user experience on desktop platforms, making the library inconsistent with native behaviors and potentially unsuitable for apps requiring accurate drag-and-drop functionality.
I believe that addressing this bug would improve libraries utility for desktop applications. Let me know if additional details or debugging logs are needed to assist in resolving the issue.
The text was updated successfully, but these errors were encountered: