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
There appears to be an odd issue in Chrome and Edge (can't reproduce it in Safari or FF) when the user double-clicks in a parent container of a draggable prior to dragging.
I have put together a simple React app that shows a full-page div containing a simple table with four cells that are each draggables. Dragging of an individual table cell works perfectly initially. The drag action takes a photo of the cell to be dragged and dragging works as expected and the draggable's onDragStart fires as expected:
However, if one double-clicks anywhere in the (light blue) container div prior to initiating the drag action, then dragging itself does take place but with a strange artefact in that the photo seems to be that of all sibling draggables (i.e. all table cells) and astonishingly, no onDragStart fires:
The dragging stays in this state until it is "reset" by single-clicking in the container div again.
There appears to be an odd issue in Chrome and Edge (can't reproduce it in Safari or FF) when the user double-clicks in a parent container of a draggable prior to dragging.
I have put together a simple React app that shows a full-page div containing a simple table with four cells that are each draggables. Dragging of an individual table cell works perfectly initially. The drag action takes a photo of the cell to be dragged and dragging works as expected and the draggable's onDragStart fires as expected:
However, if one double-clicks anywhere in the (light blue) container div prior to initiating the drag action, then dragging itself does take place but with a strange artefact in that the photo seems to be that of all sibling draggables (i.e. all table cells) and astonishingly, no onDragStart fires:
The dragging stays in this state until it is "reset" by single-clicking in the container div again.
I wonder if this is some odd focus issue maybe?
You can find my test app here:
Codesandbox test app
My set up:
macOS 14.7
[email protected]
@atlaskit/[email protected]
Chrome / Edge : latest builds (129)
The text was updated successfully, but these errors were encountered: