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 15:00:47 -0400
Message-ID: <CAO8i3idwxkxSCaQVtrpR063JL4eRbVv4QqXcawAZ4ML+gj=MvA@mail.gmail.com>
To: Brian Kardell <bkardell@gmail.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Clint Hill <clint.hill@gmail.com>, Erik Arvidsson <arv@chromium.org>, Rafael Weinstein <rafaelw@google.com>, Ryosuke Niwa <rniwa@webkit.org>, Yuval Sadan <sadan.yuval@gmail.com>, public-webapps <public-webapps@w3.org>
On Tue, Apr 24, 2012 at 2:40 PM, Brian Kardell <bkardell@gmail.com> wrote:

> All that said,  maybe with some time and experience I could learn to
> love it as DOM too... I'm really not trying to be the only one arguing
> endlessly about it, so unless someone backs me up on at least some
> point here I will rest my case :)

I feel the same way. I'm not really sure why we would want to use elements
and attributes to define the templating language. If the purpose is "we can
now parse templates using DOM", then I have to wonder if anyone using
templates is actually asking for that. I know of two use cases that need to
be solved:

1) Templates that cleanly include "</script>".
2) Generating fragments with arbitrary top-level elements.

Are there other use cases that are trying to be solved with <template>?
Received on Tuesday, 24 April 2012 19:01:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:33 UTC