Fixing incorrect mStable insets being set before user setup is complete
Bug: 155349373 Test: Verified on device Change-Id: I8363ca4d24827c90c0a22d3e8e71187ab09c83ac
This commit is contained in:
@@ -1833,10 +1833,11 @@ public class DisplayPolicy {
|
||||
|
||||
if (navBarPosition == NAV_BAR_BOTTOM) {
|
||||
// It's a system nav bar or a portrait screen; nav bar goes on bottom.
|
||||
final int top = cutoutSafeUnrestricted.bottom
|
||||
- getNavigationBarHeight(rotation, uiMode);
|
||||
final int topNavBar = cutoutSafeUnrestricted.bottom
|
||||
- getNavigationBarFrameHeight(rotation, uiMode);
|
||||
final int top = mNavButtonForcedVisible
|
||||
? topNavBar
|
||||
: cutoutSafeUnrestricted.bottom - getNavigationBarHeight(rotation, uiMode);
|
||||
navigationFrame.set(0, topNavBar, displayWidth, displayFrames.mUnrestricted.bottom);
|
||||
displayFrames.mStable.bottom = displayFrames.mStableFullscreen.bottom = top;
|
||||
if (transientNavBarShowing) {
|
||||
|
||||
Reference in New Issue
Block a user