Enable resize during relayout fix for all stacks.
Follow-up to ag/1080938/. Brought in now as the scenario occurs quite frequently during unfrozen rotation. Bug: 28559097 Change-Id: I78d116ea61f5737458f22c6743540a66ae804dd0
This commit is contained in:
@@ -1412,12 +1412,7 @@ class WindowStateAnimator {
|
|||||||
// However, this would be unsafe, as the client may be in the middle
|
// However, this would be unsafe, as the client may be in the middle
|
||||||
// of producing a frame at the old size, having just completed layout
|
// of producing a frame at the old size, having just completed layout
|
||||||
// to find the surface size changed underneath it.
|
// to find the surface size changed underneath it.
|
||||||
//
|
if (!w.mRelayoutCalled || w.mInRelayout) {
|
||||||
// TODO: For N we only apply this fix to the pinned workspace. As we
|
|
||||||
// aren't observing known issues here outside of PiP resizing. (Typically
|
|
||||||
// the other windows that use -1 are PopupWindows which aren't likely
|
|
||||||
// to be rendering while we resize).
|
|
||||||
if (!w.inPinnedWorkspace() || (!w.mRelayoutCalled || w.mInRelayout)) {
|
|
||||||
mSurfaceResized = mSurfaceController.setSizeInTransaction(
|
mSurfaceResized = mSurfaceController.setSizeInTransaction(
|
||||||
mTmpSize.width(), mTmpSize.height(), recoveringMemory);
|
mTmpSize.width(), mTmpSize.height(), recoveringMemory);
|
||||||
} else {
|
} else {
|
||||||
|
|||||||
Reference in New Issue
Block a user