- From: fuchsia via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Oct 2017 18:46:30 +0000
- To: public-svg-issues@w3.org
@tabatkins I'm not worried about breakage; it's already broken in practice. What I'm after is consistency and a standard that matches up to browser behaviour. That doesn't, however, mean we need to switch to the CSS parser for pathdata; we can just tweak the existing grammar. If you haven't seen, I've created #346 which fixes a bunch of other issues with the grammar. So if the WG wants, I'll update the PR to drop trailing dots from numbers as well. It's certainly sounding as if the door is open, even if I'm pulling when I should be pushing. But, throwing crazy at the wall, finding some way of using the CSS parser on pathdata would simplify the maintenance of SVG. Pulling apart tokens is one possibility. But maybe the CSS parser needs to grow an entry point for consuming pathdata. Or maybe there's some other way to use CSS syntax. But the current "EBNF" is at it's limit: it's forcing people to write `<number>#` from first principles, including whitespace. It will do for now. But, long term, a more sophisticated grammar would make it easier to extend pathdata without introducing bugs. And CSS is the obvious syntax, if we make it work. -- GitHub Notification of comment by fuchsia Please view or discuss this issue at https://github.com/w3c/svgwg/issues/331#issuecomment-338291469 using your GitHub account
Received on Friday, 20 October 2017 18:46:31 UTC