CoordinateParser should handle NumState.invalid first

Source/Paths/CoordinateParser.cs

@@ -274,6 +274,12 @@ public bool TryGetFloat(out float result)
                         break;
                 }
 
+                if (_newState == NumState.invalid)
+                {
+                    result = float.MinValue;
+                    return MarkState(false);
+                }
+
                 if (_newState < _currState)
                 {
                     result = float.Parse(_coords.Substring(Position, i - Position), NumberStyles.Float, CultureInfo.InvariantCulture);
@@ -286,11 +292,6 @@ public bool TryGetFloat(out float result)
                     Position = i;
                 }
 
-                if (_newState == NumState.invalid)
-                {
-                    result = float.MinValue;
-                    return MarkState(false);
-                }
                 _currState = _newState;
                 ++i;
             }

Tests/W3CTestSuite/PassingTests.txt

@@ -279,6 +279,8 @@ __pull_request-551-01.svg
 __pull_request-564-01.svg
 __pull_request-564-02.svg
 __pull_request-575-01.svg
+__pull_request-640-01.svg
+__pull_request-640-02.svg
 __AJ_Digital_Camera.svg
 __Telefunken_FuBK_test_pattern.svg
 __tiger.svg

doc/ReleaseNotes.md

@@ -15,6 +15,7 @@ The release versions are NuGet releases.
 ### Fixes
 * fixed nested svg tags not rendered properly (see [#622](https://github.com/vvvv/SVG/issues/622))
 * added handling of invalid property in parser (see [#632](https://github.com/vvvv/SVG/issues/632))
+* fixed CoordinateParser handling of invalid state (see [PR #640](https://github.com/vvvv/SVG/pull/640))
 
 ## [Version 3.0.84](https://www.nuget.org/packages/Svg/3.0.84)