Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a3313de3 authored by Graciela Wissen Putri's avatar Graciela Wissen Putri
Browse files

Floating task should not intersect with display insets 

Pip content when stashed have resolved app bounds that intersect with
display insets. Floating tasks should not be affected by display insets.

Flag: EXEMPT bug fix
Bug: 393686220
Test: Stash pip
Change-Id: I99eac528b87386157dff13213973cd07426d925b
parent 7506a12b

services/core/java/com/android/server/wm/TaskFragment.java

+2 −2
Original line number Diff line number Diff line
@@ -24,7 +24,6 @@ import static android.app.WindowConfiguration.ACTIVITY_TYPE_HOME; 
import static android.app.WindowConfiguration.ACTIVITY_TYPE_RECENTS;

import static android.app.WindowConfiguration.ACTIVITY_TYPE_UNDEFINED;

import static android.app.WindowConfiguration.ROTATION_UNDEFINED;

import static android.app.WindowConfiguration.WINDOWING_MODE_FREEFORM;

import static android.app.WindowConfiguration.WINDOWING_MODE_FULLSCREEN;

import static android.app.WindowConfiguration.WINDOWING_MODE_MULTI_WINDOW;

import static android.app.WindowConfiguration.WINDOWING_MODE_PINNED;
@@ -2519,7 +2518,8 @@ class TaskFragment extends WindowContainer<WindowContainer> { 
            inOutConfig.windowConfiguration.setAppBounds(mTmpFullBounds);

            outAppBounds = inOutConfig.windowConfiguration.getAppBounds();



            if (!customContainerPolicy && windowingMode != WINDOWING_MODE_FREEFORM) {

            // Floating tasks shouldn't be restricted by containing app bounds.

            if (!customContainerPolicy && !isFloating(windowingMode)) {

                final Rect containingAppBounds;

                if (insideParentBounds) {

                    containingAppBounds = useOverrideInsetsForConfig