- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Apr 2019 05:52:41 +0000
- To: public-svg-issues@w3.org
dirkschulze has just labeled an issue for https://github.com/w3c/svgwg as "SVG Native": == [svg-native] inner svg, symbol or use elements supported? == SVG OT does not support the `<symbol>` element and I believe that it is a good choice. `<symbol>` creates a new SVG viewport which adds a huge amount of complexity. We should not support it. Same applies to inner `<svg>` element. It should be ignored in SVG Native. The correct implementation of the `<use>` element is essential otherwise it adds a security threat to implementations. Implementations must detect cyclic dependencies, not only between elements but between CSS properties that reference elements (like `clip-path`) as well. Authoring tools use `<use>` primarily in combination with `<symbol>`. If we do not support the one we might consider not using the other. (Though there of course is hand crafted SVG content as well... it is just negligible in comparison to the masses of generated SVGs.) I am fine if we move the discussion about `<use>` to another issue if it is controversial. See https://github.com/w3c/svgwg/issues/671
Received on Tuesday, 16 April 2019 05:52:43 UTC