- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Dec 2019 21:26:00 +0000
- To: public-svg-issues@w3.org
> I will say however I doubt there are very many svgs that wrote their code that way. It likely won't break many of them. I was unaware it was a thing until the I hit the w3c test and checked the BNF. While *humans* don't generally write their pathdata all scrunched up like that, machine-generated SVGs or SVGs passed thru optimizers often remove extraneous whitespace and such. > Can we add a new path grammar that isn't a breaking change, to keep the old one in place? I'm not sure how we'd do that; I guess a keyword at the start of the pathdata that's not possible in valid old syntax? I'd really like to invent a pathdata syntax that's friendly to CSS parsing (so `path()` in CSS can take values without quoting); maybe we can align those. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/svgwg/issues/755#issuecomment-565614157 using your GitHub account
Received on Friday, 13 December 2019 21:26:01 UTC