Re: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers)

> Blink seems to use SkParse::FindScalars ...

No, it uses the CSS parser, a separate ParseNumber and a separate ParseNumber for the cases listed. (SkParse::FindScalars is some disabled functionality in Skia.) I'd suspect that the CSS parser fast path has a bug... (try for instance adding a space at the end of the attribute.)

That parenthesis aside though, I think Blink would be more interested in siding with Gecko here. (Hoping that the fastpath can be fixed.)

AFAICT, WebKit consciously changed to the stricter rules in https://trac.webkit.org/changeset/26540/webkit (and it's not unlikely that the remaining leniency shares the same underlying cause with Blink.)

-- 
GitHub Notification of comment by fsoder
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/331#issuecomment-388151834 using your GitHub account

Received on Thursday, 10 May 2018 18:59:14 UTC