Commit 4bca852a authored by abarth@chromium.org's avatar abarth@chromium.org

RenderLayerScrollableArea shouldn't call updateLayerCompositingState

Conceptually, there's no reason for RenderLayerScrollableArea to call
updateLayerCompositingState and no tests fail when the call is removed.

BUG=343756,336251

Review URL: https://codereview.chromium.org/321283003

git-svn-id: svn://svn.chromium.org/blink/trunk@175937 bbb929c8-8fbe-4397-9dbb-9b2b20218538
parent ff9f9170
...@@ -679,16 +679,6 @@ void RenderLayerScrollableArea::updateAfterLayout() ...@@ -679,16 +679,6 @@ void RenderLayerScrollableArea::updateAfterLayout()
} }
updateScrollableAreaSet(hasScrollableHorizontalOverflow() || hasScrollableVerticalOverflow()); updateScrollableAreaSet(hasScrollableHorizontalOverflow() || hasScrollableVerticalOverflow());
{
// FIXME: We should not be allowing repaint during layout. crbug.com/336251
AllowPaintInvalidationScope scoper(box().view()->frameView());
// FIXME: Remove incremental compositing updates after fixing the chicken/egg issues
// https://code.google.com/p/chromium/issues/detail?id=343756
DisableCompositingQueryAsserts disabler;
box().view()->compositor()->updateLayerCompositingState(box().layer());
}
} }
bool RenderLayerScrollableArea::hasHorizontalOverflow() const bool RenderLayerScrollableArea::hasHorizontalOverflow() const
......
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