summaryrefslogtreecommitdiff
path: root/libs/androidfw/ObbFile.cpp
diff options
context:
space:
mode:
author Evan Rosky <erosky@google.com> 2023-07-06 16:15:31 -0700
committer Evan Rosky <erosky@google.com> 2023-07-07 11:07:18 -0700
commit2874d8877051e56e169708a9634829bf45a35e9b (patch)
treeb000a6815b41114eaea41c51a72129ae76370811 /libs/androidfw/ObbFile.cpp
parent4e5473b67ea8dcc346bd848dfb49086bbb876fa4 (diff)
Add a failsafe to update surface position after activity-level transit
ActivityRecord isn't expected to change independently, however, there is now compat behavior that will enable client-code to trigger changes to an AR's surface outside of any WM-side lifecycles. This already causes glitchy offsets w/ legacy during animation, but w/ shell, the activity could get stuck with the offset if the compat properties were changed during the animation. Until we come-up with a proper solution for this, just "sync up" the surface state when idle so at-least it won't be stuck. It will still have an offset during the animation, but that is the behavior we already had. Bug: 282129721 Test: Use a forced-landscape device (eg. unfolded landscape) and launch an activity which has portrait rotation in manifest but then requests landscape rotation in onResume before animation finishes. Change-Id: I92ee7884687433b12bc2649ade7416abb9953943
Diffstat (limited to 'libs/androidfw/ObbFile.cpp')
0 files changed, 0 insertions, 0 deletions