diff options
| author | 2024-03-08 10:53:27 -0800 | |
|---|---|---|
| committer | 2024-03-21 08:18:02 +0000 | |
| commit | 5ee002d95ba131e343d8b3c32fae8bd9b530edda (patch) | |
| tree | 80c91943a20a0fe388f32066010c7113da5d2338 /libs/androidfw/ZipFileRO.cpp | |
| parent | 8365273c0b5e015c0d79af0fb9d0ef32e6c5d3d6 (diff) | |
Use opening window with largest screen area during ActivityTransition
When determining the endState while starting an ActivityTransition animation, we were taking the first app in the set of opening apps without a parent in the same transition. This left us with incorrect endState bounds when PIP was active and we were launching a fullscreen activity behind it, as we took the bounds of the PIP window instead of the fullscreen bounds. This change simply tweaks the behavior so we grab the app with the largest screenspace bounds as the endState.
Bug: 323294573
Test: Manually verified endState bounds via logging during both PIP and non-PIP activity launch
Flag: NONE
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:7a13c84d41d6d94b20e880f5868edfcb823b9dfe)
Merged-In: I719c9f04c811dc973d1fc2db095794e1ada164f7
Change-Id: I719c9f04c811dc973d1fc2db095794e1ada164f7
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.
Diffstat (limited to 'libs/androidfw/ZipFileRO.cpp')
0 files changed, 0 insertions, 0 deletions