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

Commit 0730eb16 authored by Louis Chang's avatar Louis Chang
Browse files

Fix the smallest width not updated while resolving override bounds 

Using the resolved override bounds vs. the current bounds to
check if the TaskFragment has bounds override and updates the
smallest width.

Or the activity in the embedded TaskFragment could be relaunched
next time resolving override configuration due to smallest width
changed.

Bug: 273184670
Test: steps on the bugs
Change-Id: I014decd10d14b8a2f25c8ac6833768cc5f89c624
parent fd59b80a

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

+2 −2
Original line number Diff line number Diff line
@@ -2243,8 +2243,8 @@ class TaskFragment extends WindowContainer<WindowContainer> { 
                    // task, because they should not be affected by insets.

                    inOutConfig.smallestScreenWidthDp = (int) (0.5f

                            + Math.min(mTmpFullBounds.width(), mTmpFullBounds.height()) / density);

                } else if (windowingMode == WINDOWING_MODE_MULTI_WINDOW

                        && isEmbeddedWithBoundsOverride()) {

                } else if (windowingMode == WINDOWING_MODE_MULTI_WINDOW && mIsEmbedded

                        && insideParentBounds && !resolvedBounds.equals(parentBounds)) {

                    // For embedded TFs, the smallest width should be updated. Otherwise, inherit

                    // from the parent task would result in applications loaded wrong resource.

                    inOutConfig.smallestScreenWidthDp =