summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorKazuki Takise <takise@google.com>2020-07-03 12:41:49 +0900
committerKazuki Takise <takise@google.com>2020-07-03 12:43:39 +0900
commit7b20e7f188aea56b532de79b1497c55285e85595 (patch)
tree3f51043fc069c70171b6d144f7355516059be2b4 /tools/aapt2/java/JavaClassGenerator.cpp
parentfa6332bb98133caeb4e04de544091a7e41ebb599 (diff)
Atomically apply windowing mode and display windowing mode
We currently call super.setWindowingMode() and super.setDisplayWindowingMode() in DisplayContent#setWindowingMode(), and super.setWindowingMode() calls onConfigurationChanged, which can end up triggerring rotation update logic. As some code assumes windowing mode and display windowing mode always match, they should be atomically updated. The concrete problem we are facing is that windowing mode change for the default dipslay triggers rotation incorrectly. Bug: 159751214 Test: go/wm-smoke Test: atest DisplayContentTests Change-Id: Icca1673d8bf649f6cb17bceed8cd0d533d76fabd
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions