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
In WordPress 6.5, the list view drag and drop behaviour was updated to introduce the idea of displacing list view items while dragging (implemented in #56625). The current implementation has a couple of wrinkles or subtle visual issues:
When dragging a block from a position to another, the list animates smoothly excepts the block being dragged, you see a quick "jump" to the new position
When dropping the block, the positions are already correct but you still see an unnecessary animation
My hunch is that the best path forward is likely to roll in fixes for these issues as part of the work in resolving #56539 (making the drag chip resemble the list view item). I have an earlier WIP PR exploring this over in #58103 — I'm hoping to either dust off that PR or begin a new one for the WP 6.6 cycle, but don't let that stop anyone, if anyone would like to jump in and explore ideas for this in the meantime.
The text was updated successfully, but these errors were encountered:
Part of #49563 and related to #56539
In WordPress 6.5, the list view drag and drop behaviour was updated to introduce the idea of displacing list view items while dragging (implemented in #56625). The current implementation has a couple of wrinkles or subtle visual issues:
(Kudos @youknowriad for flagging these)
Here is a quick demo of the current state:
2024-03-18.11.06.47.mp4
My hunch is that the best path forward is likely to roll in fixes for these issues as part of the work in resolving #56539 (making the drag chip resemble the list view item). I have an earlier WIP PR exploring this over in #58103 — I'm hoping to either dust off that PR or begin a new one for the WP 6.6 cycle, but don't let that stop anyone, if anyone would like to jump in and explore ideas for this in the meantime.
The text was updated successfully, but these errors were encountered: