Align path number parsing with CSS Numbers. Fixes #331

[dirkschulze]

No description provided.

[AmeliaBR]

This looks like the fix to #335, not #331. Otherwise, looks good to me, but I'm not sure how to amend the PR so the correct issue gets fixed when it is merged.

[dirkschulze]

@AmeliaBR It is both actually. #331 is related to paths as well. (All other occurrences reference CSS Number already.)

[AmeliaBR]

Ok. Our resolution from last June was:

Use CSS numbers, allow UAs to implement SVG 1.1 numbers but strongly discourage to use them

So I guess this takes care of the first half of that, by making parsing match CSS. Do you want to add a paragraph regarding the second part? Possible wording:

The SVG 1 path grammar was defined in a way that allowed a trailing decimal point without any decimal digits (like 23. ). SVG 2 harmonizes number parsing with CSS, and makes this invalid. However, user agents may continue to accept numbers with trailing decimal points when parsing is unambiguous. Authors and authoring tools must not use this number format.

[dirkschulze]

@AmeliaBR Updated PR

[AmeliaBR]

Thanks for the clarification & the reference entry.