Don't give 'order' semantic errors special treatment

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

Index: third_party/WebKit/Source/core/svg/SVGParsingError.cpp
diff --git a/third_party/WebKit/Source/core/svg/SVGParsingError.cpp b/third_party/WebKit/Source/core/svg/SVGParsingError.cpp
index 189c4131c3975d1a41a0d3f5b66be74cd818454b..d0553150dedcc7ef8cc1c4e7b7ae8f83d1022349 100644
--- a/third_party/WebKit/Source/core/svg/SVGParsingError.cpp
+++ b/third_party/WebKit/Source/core/svg/SVGParsingError.cpp
@@ -44,6 +44,8 @@ std::pair<const char*, const char*> messageForStatus(SVGParseStatus status)
         return std::make_pair("Expected path command, ", ".");
     case SVGParseStatus::NegativeValue:
         return std::make_pair("A negative value is not valid. (", ")");
+    case SVGParseStatus::ZeroValue:
+        return std::make_pair("A value of zero is not valid. (", ")");
     case SVGParseStatus::ParsingFailed:
     default:
         ASSERT_NOT_REACHED();
@@ -56,6 +58,7 @@ bool disableLocus(SVGParseStatus status)
 {
     // Disable locus for semantic errors and generic errors (see TODO below).
     return status == SVGParseStatus::NegativeValue
+        || status == SVGParseStatus::ZeroValue
         || status == SVGParseStatus::ParsingFailed;
 }