Implement SVGGeometryElement

Source/core/rendering/svg/RenderSVGShape.h

Index: Source/core/rendering/svg/RenderSVGShape.h
diff --git a/Source/core/rendering/svg/RenderSVGShape.h b/Source/core/rendering/svg/RenderSVGShape.h
index 4cd4fb7a0ff6482f190aca6cd5f86ed7453f8d97..c3cbdc23101940fdf70a1fa6916fa6d3c01fd0f9 100644
--- a/Source/core/rendering/svg/RenderSVGShape.h
+++ b/Source/core/rendering/svg/RenderSVGShape.h
@@ -37,6 +37,7 @@ namespace WebCore {
 
 class FloatPoint;
 class GraphicsContextStateSaver;
+class PointerEventsHitRules;
 class RenderSVGContainer;
 class RenderSVGPath;
 class RenderSVGResource;
@@ -78,6 +79,8 @@ protected:
     FloatRect m_strokeBoundingBox;
 
 private:
+    friend class SVGGeometryElement;

[krit, 2013/11/09 02:20:18]

The new IDL was designed to avoid things like that. Could you please elaborate
why we still need to "friend class" SVGGeometryElement please?

[rwlbuis, 2013/11/11 16:54:58]

I just did not want to expose nodeAtFloatPointInternal, but I guess it may be
better then adding the friend decl. Maybe I need to rename Internal to Helper or
something?

+
     // Hit-detection separated for the fill and the stroke
     bool fillContains(const FloatPoint&, bool requiresFill = true, const WindRule fillRule = RULE_NONZERO);
     bool strokeContains(const FloatPoint&, bool requiresStroke = true);
@@ -94,6 +97,7 @@ private:
     virtual void addFocusRingRects(Vector<IntRect>&, const LayoutPoint& additionalOffset, const RenderLayerModelObject* paintContainer = 0) OVERRIDE FINAL;
 
     virtual bool nodeAtFloatPoint(const HitTestRequest&, HitTestResult&, const FloatPoint& pointInParent, HitTestAction) OVERRIDE FINAL;
+    bool nodeAtFloatPointInternal(const HitTestRequest&, const FloatPoint&, PointerEventsHitRules);
 
     virtual FloatRect objectBoundingBox() const OVERRIDE FINAL { return m_fillBoundingBox; }
     virtual FloatRect strokeBoundingBox() const OVERRIDE FINAL { return m_strokeBoundingBox; }