diff options
| author | Robert Carr <racarr@google.com> | 2016-01-19 21:24:57 -0800 |
|---|---|---|
| committer | Rob Carr <racarr@google.com> | 2016-01-20 19:18:23 +0000 |
| commit | 7fed68d116f037847f298b7d52f537998c315298 (patch) | |
| tree | 06950dccd35bd4626edf6d19f588d2566beb9422 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | ccc2e0d9df559aa1834b1f721d043f3cb98c1791 (diff) | |
Do not clear exiting flag following explicit remove.
If we begin an exit animation (setting the mExiting flag)
in response to an explicit client remove request, we depend
on mExiting in WindowStateAnimator::finishExit to perform
the final clenaup of the window. If we are transitioning
back in to the app, and it calls removeWindow before the
app transition is ready, we could have handleOpeningApps
clear the mExiting flag leaving this partially disposed window
around due to the above mechanism.
Bug: 26157153
Change-Id: I512fbbd080d423336796284fca490c2c22709180
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions