Commit b77d0baa authored by trchen@chromium.org's avatar trchen@chromium.org

Add DisableCompositingQueryAsserts to FrameView::useSlowRepaints

Android build hits this assertion all the time, rendering debug build useless.

This disabler isn't entirely correct, but assuming blitting-based scrolling
won't last long, it should be okay with a FIXME.

BUG=357345

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170626 bbb929c8-8fbe-4397-9dbb-9b2b20218538
parent 73b4ef44
...@@ -1235,6 +1235,10 @@ void FrameView::adjustMediaTypeForPrinting(bool printing) ...@@ -1235,6 +1235,10 @@ void FrameView::adjustMediaTypeForPrinting(bool printing)
bool FrameView::useSlowRepaints(bool considerOverlap) const bool FrameView::useSlowRepaints(bool considerOverlap) const
{ {
// FIXME: It is incorrect to determine blit-scrolling eligibility using dirty compositing state.
// https://code.google.com/p/chromium/issues/detail?id=357345
DisableCompositingQueryAsserts disabler;
if (m_slowRepaintObjectCount > 0) if (m_slowRepaintObjectCount > 0)
return true; return true;
......
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