diff options
| author | Evan Rosky <erosky@google.com> | 2018-04-25 12:48:54 -0700 |
|---|---|---|
| committer | Evan Rosky <erosky@google.com> | 2018-04-26 13:14:36 -0700 |
| commit | b0e388823bef00975176a11ba269c29b062ca786 (patch) | |
| tree | 183aee762110c303673eea76d4397e3dd03cb9d7 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | f3015eb0df04089db0fbd756fcdb3d3a5670b180 (diff) | |
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
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions