NOT FOR LANDING: Hack up CSSParser for speed.

third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp

Index: third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp
diff --git a/third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp b/third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp
index cf7095038d1d273068007209f0fe23ba98046f6c..9ab5508be4e6d81a7d8e8e2e796efd49e279930a 100644
--- a/third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp
+++ b/third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp
@@ -138,8 +138,8 @@ bool CSSPropertyParser::parseValue(CSSPropertyID unresolvedProperty, bool import
 CSSValue* CSSPropertyParser::parseSingleValue(
     CSSPropertyID property, const CSSParserTokenRange& range, const CSSParserContext& context)
 {
-    if (hasInvalidNumericValues(range))
-        return nullptr;
+    // if (hasInvalidNumericValues(range))

[esprehn, 2016/04/22 23:30:58]

I think Tab is going to remove this. Doing a scan over the whole token range
looking for numbers is bad. I think this code actually scans it twice too, once
in parseValue and again in parseSingleValue called later. We should probably
clamp or abort inside the tokenizer if this is something we actually want to
enforce.

+    //     return nullptr;
     CSSPropertyParser parser(range, context, nullptr);
     CSSValue* value = parser.parseSingleValue(property);
     if (!value || !parser.m_range.atEnd())