diff options
| author | Ming-Shin Lu <lumark@google.com> | 2021-12-01 15:46:19 +0800 |
|---|---|---|
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | 2021-12-15 00:01:47 +0000 |
| commit | b52de33e3b3e2b4863341ff86262e17c97094bc1 (patch) | |
| tree | 74f362b31f12134c170b06f0c8e1fcc5a1dc6659 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | acc288377442012fe94d8003bec0bb99912f920a (diff) | |
Consolidate clearing mImeInsetsFrozenUntilStartInput
As CL[1] that IMMS only invoke updateInputMethodTargetWindow when the
IME input target window changed, that caused somehow we can't clear
mImeInsetsFrozenUntilStartInput in ActivityRecord to make the activity
can receive IME insets correctly like when turning the screen off/on
and then unlocking the non-secure keyguard to back to the same app,
since the IME input target didn't changed.
Making sure IMMS side always invoke updateInputMethodTargetWindow to WM
to clear IME insets frozen state.
[1]: Id8a56c68a06a774ef12ba444fd9a368148ea4539
Fix: 205783849
Test: atest ActivityRecordTests#\
testImeInsetsFrozenFlag_resetWhenReportedToBeImeInputTarget
Merged-In: I796754992911b917a49fcd18f22019c1eecad908
Change-Id: I796754992911b917a49fcd18f22019c1eecad908
(cherry picked from commit 5d580797c11b7b08a9e35b4575db1d957749ea10)
Merged-In:I796754992911b917a49fcd18f22019c1eecad908
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions