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

Yes, that's exactly what I wrote in my previous comment:
> ...the _CSS parser_, a separate _ParseNumber_ and a separate _ParseNumber_ for the cases listed.

That `1.e2` (and `10.`) is just a bug plain and simple - illustrated for non-SVG at [1] - and has nothing to do with "SVG attribute mode" (which I guess you're thinking of) in the WebKit/Blink CSS parser(s).
Also, adding a trailing space after `1.e2` will make that fail as well, indicating it's the same issue there. Not that that is the interesting here though.

[1] https://jsfiddle.net/10aumthz/

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

Received on Thursday, 10 May 2018 21:03:49 UTC