Fix PiP being out of bounds when launched into forced orientation
- Ensure that we use the right bounds when calculating the post-rotation bounds (it should always be the target bounds) - Ensure that we update the controller when the task stack bounds change Bug: 35402420 Test: android.server.cts.ActivityManagerPinnedStackTests Test: #testEnterPipToOtherOrientation Change-Id: Ie0e3fc6a93b4eb6250c60584e80afb029b3c599a
Loading
Please register or sign in to comment