Commit 3ea60d80 authored by Pedro Amaral's avatar Pedro Amaral Committed by Commit Bot

Remove isChromeHomeEnabed() logic from ToolbarSceneLayer

Bug: 814528
Change-Id: Ib98362502ec42cfa19de522ee40493d949295bc5
Reviewed-on: https://chromium-review.googlesource.com/1045486
Commit-Queue: Pedro Amaral <amaralp@chromium.org>
Reviewed-by: default avatarMatthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556909}
parent f16dcd5e
...@@ -192,11 +192,7 @@ public class ToolbarSceneLayer extends SceneOverlayLayer implements SceneOverlay ...@@ -192,11 +192,7 @@ public class ToolbarSceneLayer extends SceneOverlayLayer implements SceneOverlay
@Override @Override
public void onSizeChanged( public void onSizeChanged(
float width, float height, float visibleViewportOffsetY, int orientation) { float width, float height, float visibleViewportOffsetY, int orientation) {}
// If Chrome Home is enabled, a size change means the toolbar is now in a different
// location so a render is needed.
if (FeatureUtilities.isChromeHomeEnabled()) mRenderHost.requestRender();
}
@Override @Override
public void getVirtualViews(List<VirtualView> views) {} public void getVirtualViews(List<VirtualView> views) {}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment