- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Nov 2017 22:35:28 +0000
- To: public-svg-issues@w3.org
While I could theoretically do a special-case tokenization on `path()`, like I do for `url()`, I don't see any particularly good reason to do so. (And `url()` is a legacy case that I wish I could remove!) Just wrapping the content in `"` characters, and doing the actual parsing of the pathdata separately, does the same thing without any special-casing at all. If I don't special-case on `path()`, I can't do it at all - allowing pathdata in any place would mean the tokenizer having to be aware of the context in which it is tokenizing, which is a layering violation. (And if I could do that, I'd have a dramatically easier time with `<an+b>` and `<urange>`.) The CSS-ified version of path will look something like `path(M 0 0, H 10)` - path commands separated from the numbers, all numbers separated by whitespace, and the commands themselves separated by commas, all per standard CSS grammar patterns. Like I said, this is a subset of currently valid paths, but is completely friendly to the tokenizer. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/svgwg/issues/331#issuecomment-344422613 using your GitHub account
Received on Tuesday, 14 November 2017 22:35:32 UTC