This repository was archived by the owner on Feb 25, 2025. It is now read-only.
Reland: [web] Ensure handled key event is not propagated to IME #47099
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.
This PR relands #46829, which got reverted in #47086 because of flutter/flutter#136857.
There are no changes in the PR compared to the reverted one. The issue are missing
keyup
events in the integration test, which triggers assertion inKeyboardBindings
and which should be fixed by flutter/flutter#136874.Changes:
RawKeyboard
event handler is invoked fromKeyboardBinding
event handler. This is to prevent race condition because both handlers now run in capture phase andKeyboardBinding
needs to process the event first.Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.