W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: template namespace attribute proposal

From: Adam Klein <adamk@chromium.org>
Date: Thu, 12 Mar 2015 12:24:27 -0700
Message-ID: <CAEvLGc+HZfZm_xfbZosDhqM8tbpMh2=nmZ1ddQprfMJE900ePw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Benjamin Lesh <blesh@netflix.com>, WebApps WG <public-webapps@w3.org>
On Thu, Mar 12, 2015 at 11:22 AM, Anne van Kesteren <annevk@annevk.nl>
wrote:

> On Thu, Mar 12, 2015 at 7:16 PM, Adam Klein <adamk@chromium.org> wrote:
> > For clarity, is this significantly different from the below (which works
> > today)?
> >
> > <template id="tmpl">
> >   <svg>
> >     <circle .../>
> >   </svg>
> > </template>
> >
> > Clearly there's an extra step here, in that accessing the SVG elements
> > requires hopping into firstElementChild, but adding new namespace-related
> > features seems unfortunate.
>
> That was going to be my argument, but then I remembered that we went
> out of our way to make <tbody>, <tr>, <td>, etc. work as direct
> children of <template>.
>

Is your thinking that adding special-casing for SVG-"looking" (as in, tag
names appearing in the list of SVG tags but not in the list of HTML tags)
inside <template> has fewer compat risks than a wholesale change of the
HTML parser to recognize SVG-looking tags anywhere?
Received on Thursday, 12 March 2015 19:24:53 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:26 UTC