diff options
| author | 2025-03-12 17:06:56 -0700 | |
|---|---|---|
| committer | 2025-03-13 09:33:43 -0700 | |
| commit | 7d18bdd71f060d7a18ba903e48a65feea73d4360 (patch) | |
| tree | 367de307cdaa80f3186ac3a1596e212fac53a63a /libs/androidfw/AssetsProvider.cpp | |
| parent | b08d443d6dc6b7fd1aab8b4dd21de81804462af2 (diff) | |
[PiP2] Find config-at-end activity in AE case
There are cases where an activity is a leaf
in a chain of containers. So whenever we are
retrieving a delay config-at-end activity, we
should not assume it's the direct child of a PiP task change.
More specifically, here, we are dealing with a case of:
Pinned Task > TF (fills the task) > Config-at-End Activity
used by apps such as Whatsapp.
Bug: 402045190
Bug: 402270581
Flag: com.android.wm.shell.enable_pip2
Test: atest SecondaryActivityEnterPipTest
Test: direct enter PiP by back gesture from a Whatsapp call
Test: pinch-resize Whatsapp PiP
Change-Id: Ic51cdac72e7c46ba5c01440a0a6f375b37cc8714
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions