, the
developer would still need to know the edge cases. With an attribute, the
developer just needs to know that they're dealing with SVG or not.
On Sat, Mar 14, 2015 at 6:04 PM, Austin William Wright a...@bzfx.net wrote:
On Thu, Mar 12, 2015 at 4:20 PM, Benjamin Lesh bl...@netflix.com wrote
, Benjamin Lesh bl...@netflix.com
wrote:
What are your thoughts on this idea?
I think it would be more natural (HTML-parser-wise) if we
special-cased SVG elements, similar to how e.g. table elements are
special-cased today. A lot of template-parsing logic is set up so
that things work without
I'd like to propose that the template tag have a namespace= attribute
that allows the user to specify namespaces such as
http://www.w3.org/2000/svg;, so that the document fragment that comes from
`.content` is created properly.
e.g.:
template id=my-svg-template
FWIW: Currently, template tags nested in svg are SVGElement, and not
HTMLTemplate Element. You also need to hide the SVG container or it will be
rendered.
On Mar 12, 2015 8:18 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Mar 12, 2015 at 3:57 PM, Ryosuke Niwa rn...@apple.com wrote:
By
So much of the rest of how SVG/MathML are handled in HTML is seamless by
design. For my part, I disagree slightly with this statement. If you just
drop a circle tag in a div, you're going to get an HTMLUnknownElement.
This is by design and to spec, of course. But it unfortunately means you
can't
