add keypress global signal to fix keyboard vs cursor select priority in lists#962
Merged
aquaductape merged 1 commit intomainfrom Jan 13, 2026
Conversation
peterchinman
approved these changes
Jan 13, 2026
peterchinman
approved these changes
Jan 13, 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.
Bug where mouse move over triggered via dom element programmatically scrolling under cursor or user moves cursor selects active item from list.
https://github.com/user-attachments/assets/89a3a58c-de89-4999-bc56-cd935ee14df1
Adding a global signal,
isKeypressActive, when keypress is held is used to guard against setting active item via mouse handlers.