summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorMing-Shin Lu <lumark@google.com>2021-11-12 13:44:34 +0800
committerMing-Shin Lu <lumark@google.com>2021-11-29 15:28:53 +0000
commit355c04e0a778cada3db55c6c3a0e059b2add49e9 (patch)
treed1db945b19c97612998d8ee172b8ad8258eafa2d /tools/aapt2/java/JavaClassGenerator_test.cpp
parentf1650d861b81d449b689985199961e652a2fc657 (diff)
Remote mCurClientInKeyguard dependency in IMMS
The above field introduced from CL[1] for quick-fixing unexpected back icon indicator shows up when the lockscreen is shown. However, from IMMS points of view, seems IMMS is not necessary to be the decision maker to tell systemUI whether the IME is behind keyguard or not. SystemUI can properly leverage WindowInsets APIs to know the IME insets state when the keyguard requests IME visible. so that in other non-keyguard cases should be enough to deliver the IME visiblity/active information without setting "vis=0" for the special cases. [1]: I0de01ec29cb544e902305b0f9d9fb94a73835e7b Fix: 202218289 Test: manual as steps: 1) Set passcode for lockscreen to require IME. 2) Try to unlock screen 3) See if the back key icon altered when the IME shows up on the lockscreen Test: atest NavigationBarTest#\ testSetImeWindowStatusWhenKeyguardLockingAndImeInsetsChange (cherry picked from commit 1e5c277f7bb63b125e77ea3ef76cf58071d6ef86) Merged-In: I24c511d068ab371d6984201327a561322fc26bd8 Change-Id: I24c511d068ab371d6984201327a561322fc26bd8
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions