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
The current (0.6.0) Sortable algorithm requires items to be the same dimensions for correct visual sorting. Otherwise, gaps and overlays occur. The previous algorithm attempted to handle this (for specific vertical orientation), but still had issues (e.g. #9) .
Currently, it's the only thing that seems to be not working for me. Here is how dragging looks for the variable-sized sortables with the flex flex-row items-center gap-1 Tailwind styles for the container.
The logic you see in dnd-kit is similar to what I had before (see the example code at the top of this issue). However, I encountered some issues with it and will rethink the approach. Hopefully the overall improvements to the library I've made since will make this easier to solve :)
Activity
martinpengellyphillips commentedon May 2, 2022
For reference, this was the previous 'vertical' algorithm:
alllex commentedon Sep 23, 2022
Very much looking forward to this!
Currently, it's the only thing that seems to be not working for me. Here is how dragging looks for the variable-sized sortables with the
flex flex-row items-center gap-1Tailwind styles for the container.Screen.Recording.2022-09-24.at.00.45.30.mov
JoleMile commentedon Nov 12, 2022
Same here. Everything else is working great, but this makes things look quite ugly at times.
Haven't looked into this much, but could we steal some logic from here https://master--5fc05e08a4a65d0021ae0bf2.chromatic.com/?path=/story/presets-sortable-vertical--variable-heights maybe?
Would love to see this "fixed" soon.
Thank you for making and maintaining this library.
martinpengellyphillips commentedon Nov 19, 2022
Thanks for the kind words.
The logic you see in dnd-kit is similar to what I had before (see the example code at the top of this issue). However, I encountered some issues with it and will rethink the approach. Hopefully the overall improvements to the library I've made since will make this easier to solve :)
cheechgodx commentedon Jul 20, 2023
Hey. Lib is wonderful, but this issue is the first thing that catches your eye. Has anyone found any solution?