Set Ready For Review
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
CSSTokenizer tokenizer(trimmed_value);
const CSSParserToken token = tokenizer.TokenizeSingle();
if (!token.IsEOF() && token.GetType() == kIdentToken) {
const String identifier = token.Value().ToString();
if (EqualIgnoringASCIICase(identifier, "currentcolor")) {
style_color_ = StyleColor::CurrentColor();
return SVGParseStatus::kNoError;
}
}I think we want the `currentcolor` check after L:103 so that the color can be parsed first and then we check these fallback cases.
CSSTokenizer tokenizer(trimmed_value);
const CSSParserToken token = tokenizer.TokenizeSingle();
if (!token.IsEOF() && token.GetType() == kIdentToken) {
const String identifier = token.Value().ToString();
if (EqualIgnoringASCIICase(identifier, "currentcolor")) {
style_color_ = StyleColor::CurrentColor();
return SVGParseStatus::kNoError;
}
}I think we want the `currentcolor` check after L:103 so that the color can be parsed first and then we check these fallback cases.
IMO, it should be placed before parsing the string as color. It would be extra effort that is not needed.