diff options
| author | Hongwei Wang <hwwang@google.com> | 2020-05-27 11:31:40 -0700 |
|---|---|---|
| committer | Hongwei Wang <hwwang@google.com> | 2020-05-27 14:25:20 -0700 |
| commit | 95c307f8adbb8f9c261ae8b5d44dcc78808b6c94 (patch) | |
| tree | 6bae782f9f8ede2297a396164a771b3c4d00e01d /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 86f8ef1aa8a31bff4b42b728779b5cd7cbcba326 (diff) | |
No onMultiWindowModeChanged callback from split to PiP
When entering PiP from split-screen, there should be exact one
onPictureInPictureModeChanged callback with zero
onMultiWindowModeChanged since the multi-window mode is not changed.
When the stack is nested, we reparent the to-be-pinned stack to the
display area and later on set the stack windowing mode onto
ActivityRecord, which ends up WINDOWING_MODE_FULLSCREEN in this case.
Therefore, the windowing mode changes from split-screen-secondary to
fullscreen and then pinned. And client receives
onMultiWindowModeChanged(false), onPictureInPictureModeChanged(true),
onMultiWindowModeChanged(true) in sequence.
Fixes this by setting the windowing mode prior to re-parenting within
RootWindowContainer#moveActivityToPinnedStack
Bug: 157172491
Test: manually enter PiP from split screen and verifies lifecycle
Change-Id: Idf57235349ed6b78db96a632af9665b6e39edb78
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions