diff options
| author | Evan Rosky <erosky@google.com> | 2018-12-03 17:40:11 -0800 |
|---|---|---|
| committer | Evan Rosky <erosky@google.com> | 2019-01-07 13:26:48 -0800 |
| commit | 730f6e89fa7558090d92850b0335d2319373c94f (patch) | |
| tree | 3b9a500247628a249cdc7a321caa12a58031f2fc /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 252e8d0447eb64a1429a1198ff71f3785db2d2aa (diff) | |
Add FULLSCREEN policies to task level
When a task is in FULLSCREEN windowing mode, it will
fill its parent subject to some policy constraints.
This is handled at the configuration resolution step
which means that FULLSCREEN now implies matchParentBounds
even if the requestedOverrideBounds is not empty.
If it has an overridden orientation (app requested), and
this orientation doesn't match it's parent, the task will
fill as much of it's parent as it can while maintaining
it's requested orientation and will be centered.
This also sets the *requested* override bounds back to
mLastNonFullscreenBounds when entering freeform mode so
that restore works properly. This happens in tandem with
the mode change. Because this is changing *requested*
bounds, callers are free to manipulate it afterwards.
Bug: 113252962
Test: go/wm-smoke, wmtests, "maximizing" and restoring a
freeform app now properly resizes the task, added
some TaskRecordTests. Also, tested on freeform display.
Change-Id: If0e32d4240a9331dcf18209eaf4718d7ba800c5c
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions