summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorchaviw <chaviw@google.com>2018-05-30 11:05:44 -0700
committerchaviw <chaviw@google.com>2018-06-05 09:07:42 -0700
commit4ad54910a1282c36ced893c4c2a010b32a30b920 (patch)
tree56feffccc6a724ecc700fdfcc5716599c3a7723f /tools/aapt2/java/JavaClassGenerator.cpp
parente3348a25935099838a917cf4556c4dccc714e0ef (diff)
Notify WM that app is delayed closing due to the possibility of PIP.
WM determines the IME target after it sets up all the app transitions and handles visiblity. In most cases, this is fine since everything is set up properly at once. However, in cases where the app can enter PIP, the transition to close the app is delayed in case the app decides to enter PIP. In this case AM needs to notify WM of this information so it can properly calculate the IME target when the app transitions aren't fully set up. The specific usecase is the following: 1. App with the ability to enter PIP is open with IME 2. Home is pressed. 3. Launcher is brought to the front, previous app is not yet hidden since the close is delayed. 4. IME is recalculated and doesn't see any closing app. IME is targeted to launcher. 5. Prevous app is ready to close. By this point, the IME was already incorrectly targeting launcher, which causes the flicker since IME will get set relative to launcher. Test: Open Chrome with IME. Press home. No flicker. Change-Id: Ie3553b0a01ad567d8b34c3453ad838b88684e79d Fixes: 80352830
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions