diff options
| author | Jorim Jaggi <jjaggi@google.com> | 2018-03-27 18:02:18 +0200 |
|---|---|---|
| committer | android-build-team Robot <android-build-team-robot@google.com> | 2018-03-28 15:30:02 +0000 |
| commit | caca26d9e07ba4f699d7c8ab578f9642059c58cf (patch) | |
| tree | 050d1f56f3ea5e57e8f2f971dd0c349d76ab3db3 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 32c71581857dd05e3829a1fb01d48469b396f2a9 (diff) | |
Fix issue with animations that couldn't be started
If we can't create a remote animation target for some reason
(removed from task, no main window, etc), SurfaceAnimator
called startAnimation but we never invoke the finish callback.
Thus, we need to make sure to also invoke the finish callback
when not using the AppWindowToken as part of the remote animation.
This actually happens if the main intent clears the task, like
Settings. In that case, it removes all sub activities, which then
get added to mClosingApps, which then are part of a transition.
It's questionable why this would need to happen, but we don't have
the risk budget to go down that rabbit hole.
Test: RemoteAnimationControllerTest
Test: Open Settings -> Network -> Wifi, press home, reopen
Settings, repeat 10x
Test: adb shell dumpsys window -a
Fixes: 76438155
Change-Id: Ib528d5c0d3559eb20522799af68ebbfb17b9801b
(cherry picked from commit b8a9cbe4d8f7d2af99e487fe89ca2c42578c6f88)
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions