W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [webcomponents] HTML Parsing and the <template> element

From: Scott González <scott.gonzalez@gmail.com>
Date: Tue, 24 Apr 2012 17:51:57 -0400
Message-ID: <CAO8i3idwDMVzDPB5Uj-xPukE0SuyoV_qzXy0KQuA=esQ-CutbA@mail.gmail.com>
To: Erik Arvidsson <arv@chromium.org>
Cc: Brian Kardell <bkardell@gmail.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Clint Hill <clint.hill@gmail.com>, Rafael Weinstein <rafaelw@google.com>, Ryosuke Niwa <rniwa@webkit.org>, Yuval Sadan <sadan.yuval@gmail.com>, public-webapps <public-webapps@w3.org>
Yes, the fact that they both work with <script> is why I didn't list them.
If it weren't for #2, I would suspect that there wouldn't be any proposal
for <template> other than solving the </script> problem. As much as <script
type="text/whatever"> is a hack, it's really pretty clean. I could be
wrong, but I don't think there is any group of developers who are actually
upset about the semantics of using <script>.

2012/4/24 Erik Arvidsson <arv@chromium.org>

> On Tue, Apr 24, 2012 at 12:00, Scott González <scott.gonzalez@gmail.com>
> wrote:
> > Are there other use cases that are trying to be solved with <template>?
> 3. Inert. You don't want to fetch resources at unresolved URLs.
> <img src="/images/${user}.png">
> 4. Selectors should not match content of the template
> both of these works fine with <script type="text/x-this-is-a-hack">
> --
> erik
Received on Tuesday, 24 April 2012 21:52:26 UTC

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