diff options
| author | 2024-06-11 14:15:50 -0700 | |
|---|---|---|
| committer | 2024-06-11 14:25:59 -0700 | |
| commit | 4e9fc478fb393622ac06d69d20865595bf4c8d39 (patch) | |
| tree | 526d7248ecb04e42571aba3001541b2cd63937ac /libs/androidfw/FileStream.cpp | |
| parent | 45ba476dcf731e1a3b984a6a47a37ac7d71e8688 (diff) | |
Cleanup alpha animation type after use
When entering PiP from Overview, or from legacy non-auto-enter cases, an
alpha animation is used by PipTransition. When that occurs, we tend to
clear the alpha animation type in
PipTaskOrganizer#onEndOfSwipePipToHomeTransition, which is actually not
triggered in those cases.
In turn, when a bounds animation is expected for auto entering PiP,
PipTransition#augmentRequest would think it's still in alpha animation
mode and forms the WindowContainerTransaction for bounds change,
therefore, flickers at the of auto-enter-pip animation.
Fixing this by following the same contract as in PipAnimationController,
the alpha animation type is treated as a one-shot, we reset it back to
bounds whenever it's processed.
Video: http://recall/-/aaaaaabFQoRHlzixHdtY/f3UO3cLPf5E9aNouQibRio
Bug: 341944518
Test: Enter PiP from Overview, then enter PiP again from landscape to
portrait mode. See also the video
Change-Id: I3445b7770ef3a07e4acf6a5464b08a6e27829ca5
Diffstat (limited to 'libs/androidfw/FileStream.cpp')
0 files changed, 0 insertions, 0 deletions