- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 28 Apr 2018 22:00:46 +0000
- To: public-css-archive@w3.org
Given that we already have special parsing rules for the transform attribute (as compared to the property), it seems reasonable to match reality. That said: as it is currently spec'd, browsers are supposed to accept either the CSS or SVG syntax in attributes. I don't think anyone actually implements it, but if we want the too, adding fast & loose whitespace handling isn't going to make it any easier. A decision should therefore consider whether we want to shift the attribute to being more consistent with CSS parsing, or leave the attribute as a purely legacy feature. (It may be worth mentioning that, elsewhere in SVG, we have switched to using CSS parsing rules in many attributes.) -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2623#issuecomment-385208372 using your GitHub account
Received on Saturday, 28 April 2018 22:00:49 UTC