diff options
author | Riddle Hsu <riddlehsu@google.com> | 2020-05-27 23:15:39 +0800 |
---|---|---|
committer | Riddle Hsu <riddlehsu@google.com> | 2020-06-01 13:26:13 +0800 |
commit | 0c1b0d1af3279be1d41435edc1330acea3f67cb8 (patch) | |
tree | f9cb41226fa30a0a72080a19dac054ade54decf6 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
parent | edcb2c38f4a06fbc4fe786e3a5f441d0ef69b55c (diff) |
Do not set orientation to requested configuration
This restores the original behavior that non-top fullscreen windowing
mode activity with fixed orientation can inherit the orientation from
parent. And non-fullscreen windowing mode still resolves orientation
individually as before.
Assume an activity uses fixed portrait orientation, and starts another
activity in different process with fixed landscape orientation. Without
this change, the process of background activity will receive config
with portrait orientation but screenWidthDp > screenHeightDp because
only the requested orientation is overridden and other fields are from
parent configuration.
Currently there is a preload mechanism to make recents (home) activity
update to latest configuration in background to speed up next start.
The inconsistent configuration will cause preload to be triggered
unexpectedly. Then the UI may show in wrong state or even slow down
the gesture navigation by the unnecessary configuration change.
Note a legacy behavior that if the top is a non-occluding activity,
the activities visible behind will show in the same orientation even
fixed orientation is requested.
Bug: 156891776
Test: atest AppWindowTokenTests#testRespectTopFullscreenOrientation
Change-Id: I4ea394ccd18054410e8e15df8edbe782c26d9ccd
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions