- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Aug 2016 21:07:00 +0000
- To: public-svg-issues@w3.org
Where you define a new ability has little relation on whether or not it's added. As well, `vector-effect` is already overloaded to the point of meaninglessness - it's just a grab-bag of "things vaguely related to manipulating vectors" (which is a decent description of the rest of SVG, too, thus "meaningless"). Not to mention that stacking unrelated things like that makes it *much* more difficult to navigate the cascade. Insofar as this is just an SVG attribute, there's no cascade and so that's irrelevant, but when you're applying it via CSS, two independent rules can want to operate on distinct things that are grouped under `vector-effect`, and only one of them is allowed to win. Separating out the distinct effects allows them to work together without having to be super-explicit with your coordination. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/svgwg/issues/235#issuecomment-239929389 using your GitHub account
Received on Monday, 15 August 2016 21:07:06 UTC