Files
frameworks_base/core/java/android/app
Evan Rosky b0e388823b Use correct windowingMode when computing override config
The StackWindowController was calculating task bounds with
the WM-side windowingMode instead of the AM-side.
In this case, we are resizing during a windowingMode change
(fullscreen -> freeform). Since the windowingMode isn't sent
to WM-side yet, the smallestScreenWidthDp was set using
the old windowingMode resulting in the wrong resources being
used.

This change makes windowingMode one of the parameters (like
bounds/density) used to adjust the configuration.

Bug: 71028905
Test: ActivityStackTests and WindowConfigurationTests still pass.
      Open playstore maximized, go to an app page, restore window.
      Layout should now be appropriate for the smaller window.
Change-Id: Idcb538a768cd983ab9eac0d61a6dbea3e9dc64a5
2018-04-26 13:14:36 -07:00
..
2018-04-13 10:30:01 -07:00
2017-11-16 22:58:45 -07:00
2018-02-28 19:06:48 -08:00
2017-11-27 18:15:49 -08:00
2017-12-08 00:55:11 +00:00
2017-12-18 11:28:16 -08:00