diff options
| author | Riddle Hsu <riddlehsu@google.com> | 2018-11-06 17:23:15 +0800 |
|---|---|---|
| committer | Riddle Hsu <riddlehsu@google.com> | 2018-11-06 13:40:36 +0000 |
| commit | 402b440f3222f4a7a41c8917b486681bb4278ed2 (patch) | |
| tree | dbe41b0fc86eef0a7316aec8d28bac719d7fbc05 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 44f74d111f08704cae5a10b6c03db78748419816 (diff) | |
Fix unable to cleanup a removed display
Assume a display supports system decoration and allows reparenting
stacks to another display when the display is removed. If there
exists a standard type finishing activity during removing the
display, the activity will be reparented and found the original
stack is empty, then home is started again on the removed display.
This change combines the condition ActivityDisplay.mRemoved into
ActivityStack.isAttached, and defers the resume during finishing
or reparenting, so the stacks in the removing display won't be
focusable and resumed.
Also keep original z-order of the reparented stacks and reduce
unnecessary resume, visibility update for each reparented stack.
Bug: 119093839
Test: atest ActivityDisplayTests#testNotResumeHomeStackOnRemovingDisplay
Change-Id: I7dea2582ce8bd4aa4a18e1d5d721bfb1d9027c6a
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions