Restore drag position against children, not childNodes - #18
Conversation
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR fixes DOM revert logic in the SortableJS interop so that drag revert operations use element-only indexing (matching SortableJS indices) rather than childNodes, which can be shifted by Blazor-emitted whitespace/comment nodes.
Changes:
- Replaced
event.to.childNodes[...]withevent.to.children[...]when reinserting items duringonUpdaterevert. - Replaced
event.from.childNodes[...]withevent.from.children[...]when reinserting items duringonRemoverevert.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Problem
The DOM-revert logic in
onUpdate/onRemoveresolves the reference node throughchildNodes:childNodesis aNodeListthat includes text and comment nodes, while the indices SortableJS reports count elements only. Any whitespace text node or comment between items — both of which a Blazor render tree can emit around the item template — shifts the reference node and the item is reinserted at the wrong position, leaving the DOM out of step with the .NET model.onSelect/onDeselectin the same file already use.childrenfor exactly this reason, so the two index spaces were mixed within one module.Implementation
Replaced all four
childNodeslookups withchildren(anHTMLCollectionof elements only). Where no non-element nodes exist the two are equivalent, so this is a no-op in the working case and a fix in the rest.Index semantics are otherwise untouched — the existing
oldIndexvsoldDraggableIndexsplit is left as-is.