RectIntersection is not working with draggable items inside a scrollable container
See original GitHub issueThe draggable items that are scrolled are not calculating the intersectionRatio
correctly.
Please, see this code sandbox for an example: https://codesandbox.io/s/react-dnd-grid-0ylzl?file=/src/App.js
NOTE: Try dragging the last draggable item into one droppable area.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:16 (4 by maintainers)
Top Results From Across the Web
angular - can't drag items to outside of a scrollable container
I found that you need to clone to outside before scrolling but I have no idea how to do that in angular and...
Read more >overflow-x - CSS: Cascading Style Sheets - MDN Web Docs
The box is not a scroll container, and does not start a new ... If content fits inside the padding box, it looks...
Read more >Drag Overlay - dnd-kit – Documentation
If your draggable item is within a scrollable container, ... If you conditionally render the <DragOverlay> component, drop animations will not work.
Read more >Drag to scroll - HTML DOM
User often uses the mouse to scroll in a scrollable container. In addition to that, some applications also allow user to scroll by...
Read more >Dragging a draggable element out of a scrollable div - GSAP
But sadly I'm facing an issue with Draggable. ... Dragging in a non-scrollable div works flawless. ... The more negative things (issues).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @jeserodz, seems like a legit bug, thanks for the report!
Hi I wonder if there’s an update on this ticket? The branch at #54 seems to have gone stale. I have a workaround with a different collision detector which uses the current active item rather than the
collisionRect
which seems to work for the meantime. Obviously not something we want to keep in our codebase however. Thanks.