Keep task log selection stable while dragging - #71155
Draft
Andrushika wants to merge 3 commits into
Draft
Conversation
Virtualized log rows are unmounted as they leave the viewport. This destroys selection boundaries and makes text selections collapse or drift during scrolling.
Dragging a task log selection past the top or bottom edge can flip or collapse it because the browser resolves the focus against the virtualized spacer instead of a mounted row.
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
1 participant
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.
Why
Dragging a task log selection past the top or bottom edge can flip or collapse it. The browser focus lands on unmounted spacer space while the virtualizer scrolls.
What
Make non-row areas unselectable during a drag. Extend the focus to the nearest mounted row edge on each animation frame so it follows scrolling.
stacked on: #71148
related: #68846
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following the guidelines