diff options
| author | 2022-10-05 16:51:39 +0000 | |
|---|---|---|
| committer | 2022-10-05 17:08:24 +0000 | |
| commit | d88ee6c69c722d85c133516794481c4c4b410365 (patch) | |
| tree | d5d423db1b925d7b275dcb93af3cacb559f546f1 /libs/androidfw/ResourceTimer.cpp | |
| parent | 576b93c7fe4d4734485f402054d0f1adc33fac15 (diff) | |
Make sure that a recents-launch with remote gets its own transition
If a remote is attached to an activity-launch, it should be its own
transition so that the requester can get the proper transition
lifecycle events (handleRequest). Unfortunately, the current
startActivity API is synchronous, so we don't know if the caller
needs an accurate result or not so normally we have to merge all
launches meaning the remote can get lost.
Fortunately, for recents, we do know that launcher cares about
the transition lifecycle and not the startActivity result. So,
in this case, we can defer the activity start if necessary.
Bug: 250012839
Test: launch app with dialogactivity on top. Swipe to recents.
Change-Id: I715518bf9611b8ad50bbfb5b05dea8002cb5a6e5
Diffstat (limited to 'libs/androidfw/ResourceTimer.cpp')
0 files changed, 0 insertions, 0 deletions