[SPv2] Associate effect property nodes for SVG paint chunks

third_party/WebKit/Source/core/layout/LayoutObject.h

Index: third_party/WebKit/Source/core/layout/LayoutObject.h
diff --git a/third_party/WebKit/Source/core/layout/LayoutObject.h b/third_party/WebKit/Source/core/layout/LayoutObject.h
index 467bf0a4bba259a9c091936a4b7708924da44523..7541a82e21c39478c2b6bad1bc5c2a294696f45f 100644
--- a/third_party/WebKit/Source/core/layout/LayoutObject.h
+++ b/third_party/WebKit/Source/core/layout/LayoutObject.h
@@ -648,7 +648,11 @@ class CORE_EXPORT LayoutObject : public ImageResourceObserver,
     return !isSVG() || (isSVGContainer() && !isSVGHiddenContainer()) ||
            isSVGShape() || isSVGImage() || isSVGText();
   }
-  virtual bool hasNonIsolatedBlendingDescendants() const { return false; }
+  virtual bool hasNonIsolatedBlendingDescendants() const {

[trchen, 2016/12/14 01:36:55]

Why not just remove the thing and make it part of LayoutSVGModelObject interface
you might ask?

It is because LayoutSVGRoot is LayoutBoxModelObject, not LayoutSVGModelObject.
There is a FIXME on line 603.

IMO our layout object type system is not designed well to handle things crossing
flow type boundary. LayoutSVGRoot is an inline-flow to its parent (inline
replaced), but contains SVG-flow. Likewise, LayoutSVGBlock is a SVG-flow to its
parent, but contains block-flow. Ideally this really should be solved with
properly designed diamond inheritance...

+    // SVG only. For non-SVG objects, query PaintLayer instead.
+    NOTREACHED();
+    return false;
+  }
   enum DescendantIsolationState {
     DescendantIsolationRequired,
     DescendantIsolationNeedsUpdate,