diff options
| author | Chavi Weingarten <chaviw@google.com> | 2018-05-14 17:32:42 +0000 |
|---|---|---|
| committer | chaviw <chaviw@google.com> | 2018-05-14 11:04:15 -0700 |
| commit | 3a74855bbb160b2e9240c2268c823916af2dea72 (patch) | |
| tree | f9c0f9844bfe30853ec25cca81953e01805aada6 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 82db2614e450f92e373d0018a5b23d80c13511c2 (diff) | |
Prevent IME from targeting home when closing app is still animating
There were a few issues that caused the IME target to get set to home.
1. Home is considered above the other apps since it's getting launched.
However, the visual representation is actually below the closing app.
IME tries to target the highest app, but it's not necessarily the
highest visual app
2. computeIme was called before all apps were set up. This caused the
IME target to get recomputed before adding the closing apps
3. The condition for a WS.isClosing was based on previous versions so
it was incorrect
Test: IME closes on top of current target when going home with IME open
Change-Id: Ia9b0cc913eeb76a4af20f9ac7b667c5a3d1eafc7
Fixes: 78214125
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions