-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undo/Redo history disappears on Japanese keyboard #130881
Comments
Hi @toshiaki-h. Thanks for filing this issue. I am able to reproduce this issue on the latest
flutter doctor -v
|
Hi @dam-ease. Thank you for confirming the reproduction. |
This appears to be specific to Android (which is not desktop), and probably is somewhere in the vicinity of text input or the Android embedder. (Desktop Triage) |
This change adds a feature to `UndoHistory` that allows the user to modify the value being pushed onto the undo stack. This is used by the framework to ignore the composing region when pushing history entries to the Undo stack on Android. This is so an undo does not trigger an input connection restart by the Android TextInputPlugin, which occurs when the framework changes the composing region. This is also the native platform behavior observed in Google Keep app on Android, where doing an undo during composing reverts to the previous state but with composing inactive and a subsequent redo does not bring back the composing region. Fixes #130881 Partial fix for #134398
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
This change adds a feature to `UndoHistory` that allows the user to modify the value being pushed onto the undo stack. This is used by the framework to ignore the composing region when pushing history entries to the Undo stack on Android. This is so an undo does not trigger an input connection restart by the Android TextInputPlugin, which occurs when the framework changes the composing region. This is also the native platform behavior observed in Google Keep app on Android, where doing an undo during composing reverts to the previous state but with composing inactive and a subsequent redo does not bring back the composing region. Fixes flutter#130881 Partial fix for flutter#134398
Is there an existing issue for this?
Steps to reproduce
2022
on Japanese keyboard.Expected results
Undo/Redo works correctly when using a Japanese keyboard.
In this case, Redo can be tapped.
Actual results
The Redo button is enabled for a moment, but becomes disable immediately.
Code sample
Code sample
Screenshots or Video
Screenshots / Video demonstration
screen-20230719-211736.2.mp4
Logs
Logs
[Paste your logs here]
Flutter Doctor output
Doctor output
The text was updated successfully, but these errors were encountered: