- From: Boris Dalstein via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 09:49:49 +0000
- To: public-svg-issues@w3.org
Indeed, and also things like `1.0e-42` should be allowed too. This was correct in SVG 1.1, see: https://www.w3.org/TR/SVG11/paths.html#PathDataBNF I believe the idea is that in SVG 2.0, it should delegate the definition of "number" to CSS. There are in fact a few other things that were broken when the grammar was rewritten between 1.1 and 2.0, see: - https://github.com/w3c/svgwg/issues/752 - https://github.com/w3c/svgwg/issues/807 - https://github.com/w3c/svgwg/pull/778 Is there someone on the committee and/or with merge rights that can volunteer to review these changes, integrate them, and close all these related issues? The above PR is a good place to start as it's quite a trivial change: only one line modified. If someone is willing to review and merge PRs, starting with the one above, then I can take the time to volunteer to make other PRs to fix the remaining grammar problems. -- GitHub Notification of comment by dalboris Please view or discuss this issue at https://github.com/w3c/svgwg/issues/926#issuecomment-1822434890 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 09:49:51 UTC