Add a document phase for calculating paint properties

third_party/WebKit/Source/core/frame/FrameView.cpp

Index: third_party/WebKit/Source/core/frame/FrameView.cpp
diff --git a/third_party/WebKit/Source/core/frame/FrameView.cpp b/third_party/WebKit/Source/core/frame/FrameView.cpp
index 0ac9a2b83253f07c93b5c44daff1e746881dddc2..d93de04405fa2e0c14f9eb4ef716e6007472d9fc 100644
--- a/third_party/WebKit/Source/core/frame/FrameView.cpp
+++ b/third_party/WebKit/Source/core/frame/FrameView.cpp
@@ -2438,6 +2438,9 @@ void FrameView::updateLifecyclePhasesInternal(LifeCycleUpdateOption phases, cons
 
             updateCompositedSelectionIfNeeded();
 
+            if (RuntimeEnabledFeatures::slimmingPaintV2Enabled())
+                calculatePaintProperties();
+
             if (RuntimeEnabledFeatures::slimmingPaintSynchronizedPaintingEnabled()) {
                 synchronizedPaint(interestRect);
                 if (RuntimeEnabledFeatures::slimmingPaintV2Enabled())
@@ -2455,6 +2458,15 @@ void FrameView::updateLifecyclePhasesInternal(LifeCycleUpdateOption phases, cons
     }
 }
 
+void FrameView::calculatePaintProperties()

[esprehn, 2015/10/01 09:05:07]

recalcPaintProperties would match the verbage we use in other parts of the
engine

(or updatePaintProperties).

+{
+    ASSERT(RuntimeEnabledFeatures::slimmingPaintV2Enabled());
+
+    lifecycle().advanceTo(DocumentLifecycle::InCalcPaintProps);
+    // TODO(pdr): Calculate the paint properties by walking the layout tree.

[esprehn, 2015/10/01 09:00:08]

That design doc is very light on details, how will you track dirty bits, what
invalidates this phase? What avoids walking the entire layout tree?

+    lifecycle().advanceTo(DocumentLifecycle::CalcPaintPropsClean);
+}
+
 void FrameView::synchronizedPaint(const LayoutRect& interestRect)
 {
     ASSERT(RuntimeEnabledFeatures::slimmingPaintSynchronizedPaintingEnabled());