Unprefix -webkit-clip-path

third_party/WebKit/Source/core/layout/svg/SVGLayoutSupport.cpp

Index: third_party/WebKit/Source/core/layout/svg/SVGLayoutSupport.cpp
diff --git a/third_party/WebKit/Source/core/layout/svg/SVGLayoutSupport.cpp b/third_party/WebKit/Source/core/layout/svg/SVGLayoutSupport.cpp
index 83d67c8c83eef93361ca0caa9fc487fe5c5805a7..dbc2c1f9700055e5e610295e06c2b052a2398409 100644
--- a/third_party/WebKit/Source/core/layout/svg/SVGLayoutSupport.cpp
+++ b/third_party/WebKit/Source/core/layout/svg/SVGLayoutSupport.cpp
@@ -370,16 +370,18 @@ bool SVGLayoutSupport::hasFilterResource(const LayoutObject& object)
 
 bool SVGLayoutSupport::pointInClippingArea(const LayoutObject& object, const FloatPoint& point)
 {
-    // We just take clippers into account to determine if a point is on the node. The Specification may
-    // change later and we also need to check maskers.
+    ClipPathOperation* clipPathOperation = object.styleRef().clipPath();
+    if (!clipPathOperation)
+        return true;
+    if (clipPathOperation->type() == ClipPathOperation::SHAPE) {

[chrishtr, 2016/09/09 02:04:46]

Why this new code to support SHAPE? Is this to implement
the additional feature mentioned in the CL description?
if so, why add a new feature while unprefixing?

[fs, 2016/09/09 08:28:10]

No, this is actually what falls out by starting to use ClipPathOperation
(ComputedStyle::clipPath). This was broken before because we didn't consider
'-webkit-clip-path' here although we painted it. Considering it's literally only
four additional lines (and two would be needed to avoid supporting it) it felt a
bit silly to leave it out. In contrast, the painting side of things (this is
hit-testing code) are nicely shareable, so just constitutes plugging in
ClipPathClipper, for a net reduction in code. No such luck for hit-testing
though...

[fs, 2016/09/09 08:31:35]

I should probably mention that "Support for nesting a <clipPath> with a
<basic-shape>..." as mentioned in the description is also one of those things
that are trivially supported by sharing code - although technically landing that
separately essentially mean that paint and hit-test code-paths have to diverge
in some way. (Or be very ugly/require additional code.)

[fs, 2016/09/09 16:26:42]

I've split out <basic-shape> support for 'clip-path' to
https://codereview.chromium.org/2322343003 - I'll update this CL to be based on
that as soon as I've shuttled home.

[fs, 2016/09/09 20:12:16]

Done.

+        ShapeClipPathOperation& clipPath = toShapeClipPathOperation(*clipPathOperation);
+        return clipPath.path(object.objectBoundingBox()).contains(point);
+    }
+    DCHECK_EQ(clipPathOperation->type(), ClipPathOperation::REFERENCE);
     SVGResources* resources = SVGResourcesCache::cachedResourcesForLayoutObject(&object);
-    if (!resources)
+    if (!resources || !resources->clipper())
         return true;
-
-    if (LayoutSVGResourceClipper* clipper = resources->clipper())
-        return clipper->hitTestClipContent(object.objectBoundingBox(), point);
-
-    return true;
+    return resources->clipper()->hitTestClipContent(object.objectBoundingBox(), point);
 }
 
 bool SVGLayoutSupport::transformToUserSpaceAndCheckClipping(const LayoutObject& object, const AffineTransform& localTransform, const FloatPoint& pointInParent, FloatPoint& localPoint)
@@ -435,7 +437,7 @@ bool SVGLayoutSupport::willIsolateBlendingDescendantsForStyle(const ComputedStyl
     const SVGComputedStyle& svgStyle = style.svgStyle();
 
     return style.hasIsolation() || style.opacity() < 1 || style.hasBlendMode()
-        || style.hasFilter() || svgStyle.hasMasker() || svgStyle.hasClipper();
+        || style.hasFilter() || svgStyle.hasMasker() || style.clipPath();
 }
 
 bool SVGLayoutSupport::willIsolateBlendingDescendantsForObject(const LayoutObject* object)