Ignore IME keydown events in the Rooster iframe bridge - #540
Open
squarepots wants to merge 1 commit into
Open
Conversation
squarepots
force-pushed
the
fix/rooster-ime-keydown-bubbling
branch
from
September 7, 2026 15:18
8c28855 to
b94c46d
Compare
mmso
force-pushed
the
main
branch
10 times, most recently
from
September 11, 2026 16:16
5eb5e79 to
28d81d1
Compare
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.
Return early from the Rooster iframe bridge for keydown events where
isComposingis true orkeyCodeis 229. This keeps IME events out of shortcut handling and cloned event dispatch. Normal keydown behavior remains unchanged.Add contract tests for active composition, the keyCode 229 fallback, and a normal keydown event.
Verification
Focused red/green GitHub Actions run:
git diff --checkpasses.Fixes #539