Source/WebCore: Don't flush compositing layers within FrameView::willPaintContents()
[WebKit-https.git] / Source / WebCore / ChangeLog
index 6f14548..71518ae 100644 (file)
@@ -1,3 +1,19 @@
+2014-03-21  Simon Fraser  <simon.fraser@apple.com>
+
+        Don't flush compositing layers within FrameView::willPaintContents()
+        https://bugs.webkit.org/show_bug.cgi?id=130627
+        <rdar://problem/16368869>
+
+        Reviewed by Sam Weinig.
+
+        Remove the call to flushCompositingStateForThisFrame() here. We should
+        have always flushed before painting via other mechanisms in WebKit2 and WebKit2.
+        Flushing during painting is actually harmful, since we could be inside
+        a CA commit already, and creating or destroying layers via flushing is bad.
+
+        * page/FrameView.cpp:
+        (WebCore::FrameView::willPaintContents):
+
 2014-03-22  Martin Hodovan  <mhodovan@inf.u-szeged.hu>
 
         ASSERTION FAILED: std::isfinite(num) in WebCore::CSSPrimitiveValue::CSSPrimitiveValue