RESOLVED DUPLICATE of bug 130627123753
Consider removing flushCompositingStateForThisFrame() from FrameView::paintContents 
https://bugs.webkit.org/show_bug.cgi?id=123753
Summary Consider removing flushCompositingStateForThisFrame() from FrameView::paintCo...
Simon Fraser (smfr)
Reported 2013-11-04 13:54:24 PST
A call to flushCompositingStateForThisFrame() was added to FrameView::paintContents() in http://trac.webkit.org/changeset/46645 to ensure that compositing layers are flushed in sync with painting. However, this model only makes sense in the non layer-backed WK1 code path (where painting is going to the window, and layers are composited separately). If everything is CA-rendered, (iOS, or WK2), then this call is a waste of time. We won't hit this for WK2 though.
Attachments
Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2014-03-21 18:52:17 PDT
Fixing this via 130627. *** This bug has been marked as a duplicate of bug 130627 ***
Note You need to log in before you can comment on or make changes to this bug.