summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author android-build-team Robot <android-build-team-robot@google.com> 2018-04-30 14:15:27 +0000
committer Android (Google) Code Review <android-gerrit@google.com> 2018-04-30 14:15:27 +0000
commit5685dffd5d76b3f7591ef097dbcbf5a6fec05cc7 (patch)
tree73e8044c388747705f4a46a482d8f1b264009f82
parentbe654b3576d230bdb67086104aa6bde023c7d460 (diff)
parent3e80b60ef76d4514345087e9e3e3838d98307794 (diff)
Merge "PIP: Partial fix to wrong insets during bounds animation" into pi-dev
-rw-r--r--services/core/java/com/android/server/am/ActivityStackSupervisor.java6
1 files changed, 2 insertions, 4 deletions
diff --git a/services/core/java/com/android/server/am/ActivityStackSupervisor.java b/services/core/java/com/android/server/am/ActivityStackSupervisor.java
index e5565dccc70e..b1ca64eaf7a0 100644
--- a/services/core/java/com/android/server/am/ActivityStackSupervisor.java
+++ b/services/core/java/com/android/server/am/ActivityStackSupervisor.java
@@ -2890,10 +2890,8 @@ public class ActivityStackSupervisor extends ConfigurationContainer implements D
try {
ActivityRecord r = stack.topRunningActivityLocked();
Rect insetBounds = null;
- if (tempPinnedTaskBounds != null) {
- // We always use 0,0 as the position for the inset rect because
- // if we are getting insets at all in the pinned stack it must mean
- // we are headed for fullscreen.
+ if (tempPinnedTaskBounds != null && stack.isAnimatingBoundsToFullscreen()) {
+ // Use 0,0 as the position for the inset rect because we are headed for fullscreen.
insetBounds = tempRect;
insetBounds.top = 0;
insetBounds.left = 0;