diff options
| author | 2025-01-15 17:41:21 +0100 | |
|---|---|---|
| committer | 2025-01-20 16:14:18 +0100 | |
| commit | 76ab8a30c4f2d5441380ca37e57e388b6ab24a4d (patch) | |
| tree | 51ba105ebf11faa1b1312e7c5bef2bbafa8fbfa4 /api/coverage/tools | |
| parent | 406336989d7ed25475afbb7a5585ad69c0122349 (diff) | |
Make ContentPicker work with NestedSharedElements
Prior to ag/30638736 we did not have a way to track a parent transition
from within a NestedStl, therefore we could not animate an element based
on a transition of an ancestor. This meant that for sharedElements
across nested STLs we always had to render the element in the highest
ancestor.
With this change we can render sharedElements in any content and
therefore we can bring back and simplify the code to use ContentPickers
as before.
This change needs to make adjustments to how we calculate zIndex for
each content, otherwise for each nestedSTL the zIndex is counted from
0f, therefore the default content picker (HighestZOrder) has mostly
arbitrary results.
Bug: 376659778
Test: Added new unit tests
Flag: com.android.systemui.scene_container
Change-Id: I72966b55f1b6fd53d88b0670f855ff5a3120f2a0
Diffstat (limited to 'api/coverage/tools')
0 files changed, 0 insertions, 0 deletions