[Webkit-unassigned] [Bug 89733] Figure out why FrameView.cpp's ASSERT(!needsLayout()) is firing in chromium & chromium's DRT

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 23 17:40:37 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=89733





--- Comment #7 from James Robinson <jamesr at chromium.org>  2012-10-23 17:41:41 PST ---
We run layout() and then iterate through our composited layers and paint various ones.  We assume that layout is still up-to-date since we don't run any other tasks after calling layout() and we don't do anything other than GraphicsLayerClient::paint..() calls.  Various bits of RenderObject implementations incorrectly mark themselves or the FrameView as needing layout either during the layout() call or during paint, leading to this assertion.  The fix is to figure out who's issuing the spurious setNeedsLayout() calls and killing them.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list