Merge "PIP: Partial fix to wrong insets during bounds animation" into pi-dev
This commit is contained in:
committed by
Android (Google) Code Review
commit
5685dffd5d
@@ -2890,10 +2890,8 @@ public class ActivityStackSupervisor extends ConfigurationContainer implements D
|
|||||||
try {
|
try {
|
||||||
ActivityRecord r = stack.topRunningActivityLocked();
|
ActivityRecord r = stack.topRunningActivityLocked();
|
||||||
Rect insetBounds = null;
|
Rect insetBounds = null;
|
||||||
if (tempPinnedTaskBounds != null) {
|
if (tempPinnedTaskBounds != null && stack.isAnimatingBoundsToFullscreen()) {
|
||||||
// We always use 0,0 as the position for the inset rect because
|
// Use 0,0 as the position for the inset rect because we are headed for fullscreen.
|
||||||
// if we are getting insets at all in the pinned stack it must mean
|
|
||||||
// we are headed for fullscreen.
|
|
||||||
insetBounds = tempRect;
|
insetBounds = tempRect;
|
||||||
insetBounds.top = 0;
|
insetBounds.top = 0;
|
||||||
insetBounds.left = 0;
|
insetBounds.left = 0;
|
||||||
|
|||||||
Reference in New Issue
Block a user