Repository navigation
CardView: reorder columns by the drop position, not the previous drag move - #36151
Merged
EugeniyKiyashko merged 2 commits intoNov 5, 2026
Conversation
… move onDragMove runs before Sortable updates toIndex, so the neighbor columns stored there could lag one move behind. When the move that reached the new position was the last one before the drop, the column stayed where it was. The drop handler now takes the neighbors from the drop index.
…column The drag status comes from the last drag move, which can still see the old neighbors. A drop between two columns that cannot be reordered is now skipped as it is during the drag.
anna-shakhova
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.