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
refactor: make handleSortableEnd robust to SortableJS and selector variants
Addresses Copilot review feedback on #110 fix:
1. Fall back to event.newIndex when event.newDraggableIndex is absent —
some SortableJS builds / event shims only expose newIndex.
2. Include [data-card-id] in the normalization selector and neighbor
query, symmetrical with the data-card-id fallback already used for
the dragged card's own id. Without this, cards that only expose
data-card-id would silently fall through to (null, null), which the
backend treats as "move to bottom".
Browser-verified: top drop still lands at top when the event only
carries newIndex, and when cards only expose data-card-id.
0 commit comments