Release bugfix for keyboard input handling#10
Merged
eyuelberga merged 2 commits intomainfrom Dec 26, 2025
Merged
Conversation
Merge main to develop
Switch to beforeinput-based input handling with a safe keydown fallback to improve cross-platform compatibility. #7
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.
Closes #7
📝 Description
Fixes inconsistent keyboard input handling across environments by selecting the appropriate input event strategy at runtime.
⛳️ Current behavior (updates)
Input handling relies on a single event type, which can lead to incorrect behavior on some browsers and input methods.
🚀 New behavior
Uses
beforeinputwhen available and falls back tokeydownotherwise, ensuring consistent behavior across platforms.💣 Is this a breaking change (Yes/No):
No
📝 Additional Information
No public API changes or new dependencies.