SVG animateMotion paths that only cause offsets are no longer ignored

third_party/WebKit/Source/core/svg/SVGAnimateMotionElement.cpp

Index: third_party/WebKit/Source/core/svg/SVGAnimateMotionElement.cpp
diff --git a/third_party/WebKit/Source/core/svg/SVGAnimateMotionElement.cpp b/third_party/WebKit/Source/core/svg/SVGAnimateMotionElement.cpp
index bbd4503917039afa145ae4895cbb7616053e24cc..5567447cdd2660747e08ec7e7d44d4ea17c41d90 100644
--- a/third_party/WebKit/Source/core/svg/SVGAnimateMotionElement.cpp
+++ b/third_party/WebKit/Source/core/svg/SVGAnimateMotionElement.cpp
@@ -253,12 +253,11 @@ void SVGAnimateMotionElement::calculateAnimatedValue(float percentage, unsigned
     float positionOnPath = m_animationPath.length() * percentage;
     FloatPoint position;
     float angle;
-    bool ok = m_animationPath.pointAndNormalAtLength(positionOnPath, position, angle);
-    if (!ok)
-        return;
+    m_animationPath.pointAndNormalAtLength(positionOnPath, position, angle);
 
     // Handle accumulate="sum".
     if (isAccumulated() && repeatCount) {
+        bool ok;
         FloatPoint positionAtEndOfDuration = m_animationPath.pointAtLength(m_animationPath.length(), ok);

[pdr., 2015/10/30 00:52:05]

pointAtLength just calls pointAndNormalAtLength internally. Does this need to be
updated to handle the "M 100 100 L 100 100" case too?

[Eric Willigers, 2015/11/20 07:49:53]

Updated.

animateMotion-still.html now tests this case when time is 2s,3s
(repeatCount==1).

         if (ok)
             position.move(positionAtEndOfDuration.x() * repeatCount, positionAtEndOfDuration.y() * repeatCount);