diff options
| author | 2024-11-07 11:14:26 +0000 | |
|---|---|---|
| committer | 2024-11-11 10:34:50 +0000 | |
| commit | 6ec6fb19e59ac7c893e6308ef32e1803caa2ab7e (patch) | |
| tree | 2e27b0c8a66af029f2e47452bea2be12ff776796 /libs/androidfw/AssetsProvider.cpp | |
| parent | 95f5091d51a955726e3b18b6ff48f6cf87782bfd (diff) | |
Avoid handling the back key event, when IME is currently hiding
When there was an ongoing hide animation (without predictive back enabled), and another swipe back happened, the second event went to the InputMethodService, where it was consumed.
This was caused by the fact, that the IME is only notified that it will be hidden at the end of the hide animation.
However, the second back event should go to the app.
This CL fixes this behaviour and doesn't dispatch the back key event to the IME, if there is an ongoing hide animation or predictive back animation in progress.
Bug: 375986921
Test: Manual, i.e. verifying that quick double back swipes are handled correctly (including after an interrupted IME hide animation)
Flag: android.view.inputmethod.refactor_insets_controller
Change-Id: Ic22f76b4708c4e5f090824d1d46833a97b19b49f
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions