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

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

From: Elliott Sprehn <esprehn@gmail.com>
Date: Tue, 26 Jun 2012 13:34:06 -0700
Message-ID: <CAPJYB1iviYJqFJkWQAZOyCKrq3RHXgbm56qzFMCub40k9G=QNw@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Rafael Weinstein <rafaelw@google.com>, Henri Sivonen <hsivonen@iki.fi>, Ian Hickson <ian@hixie.ch>, public-webapps <public-webapps@w3.org>, Simon Pieters <simonp@opera.com>
Hmm, I might be in agreement with Henri then. Having all these parallel
trees in the DOM is getting kind of out of control. Now there's the shadow
DOM trees on every node, and also this nested tree of document fragments
from <template>. There's a lot of simplicity in the DOM design that's lost
from these two changes.

On Tue, Jun 26, 2012 at 1:19 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Tue, Jun 26, 2012 at 1:03 PM, Elliott Sprehn <esprehn@gmail.com> wrote:
> > Silly question but why not specify the template element as if it's
> contents
> > were PCDATA, and the document fragment is the "value". Then this whole
> thing
> > isn't really any different than a <textarea>.
> Because you can't nest <textarea> inside of itself, but we want
> templates to be nestable.
> ~TJ
Received on Tuesday, 26 June 2012 20:34:55 UTC

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