Define contentsProperties on ObjectPaintProperties, for use in paint invalidation.

third_party/WebKit/Source/core/paint/ObjectPaintProperties.h

Index: third_party/WebKit/Source/core/paint/ObjectPaintProperties.h
diff --git a/third_party/WebKit/Source/core/paint/ObjectPaintProperties.h b/third_party/WebKit/Source/core/paint/ObjectPaintProperties.h
index 9c9a1a7ef390ce1af5aa1dff570c137d6ca4184e..05cc6c6e7a1254e1baef57808793f487c9835393 100644
--- a/third_party/WebKit/Source/core/paint/ObjectPaintProperties.h
+++ b/third_party/WebKit/Source/core/paint/ObjectPaintProperties.h
@@ -59,6 +59,7 @@ public:
 
     // The hierarchy of the clip subtree created by a LayoutObject is as follows:
     // [ css clip ]
+    // [ css clip fixed position]
     // |
     // +--- [ overflow clip ]
     const ClipPaintPropertyNode* cssClip() const { return m_cssClip.get(); }
@@ -77,6 +78,9 @@ public:
         PropertyTreeState propertyTreeState;
     };
     const LocalBorderBoxProperties* localBorderBoxProperties() const { return m_localBorderBoxProperties.get(); }
+    // ContentsProperties is the PropertyTreeState state that is the same as in localBorderBoxProperties, except that it is inside
+    // any clips and scrolls caused by this object. This PropertyTreeState is suitable as the destination for paint invalidation.
+    PropertyTreeState contentsProperties() const;

[szager1, 2016/08/31 21:16:19]

Perf nit: I'm not sure it's worth caring about, but this would be more efficient
if it took a PropertyTreeState& argument:

void getContentsProperties(PropertyTreeState&) const;

I would only worry about it if this method is going to be called a lot.

[chrishtr, 2016/09/01 16:56:22]

Done.

 
     void clearPaintOffsetTranslation() { m_paintOffsetTranslation = nullptr; }
     void clearTransform() { m_transform = nullptr; }