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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 26 Apr 2012 11:25:56 -0700
Message-ID: <CAAWBYDBJeDESL88KoGTswbWwcCJqKAtxrstPwcGq77ZgVthAVQ@mail.gmail.com>
To: Brian Kardell <bkardell@gmail.com>
Cc: Clint Hill <clint.hill@gmail.com>, public-webapps@w3.org, Ojan Vafai <ojan@chromium.org>, Dimitri Glazkov <dglazkov@chromium.org>, Kornel Lesiński <kornel@geekhood.net>
On Thu, Apr 26, 2012 at 10:38 AM, Brian Kardell <bkardell@gmail.com> wrote:
> Since <template> is a very specialized thing then (inert, boundaries
> and all that), and what some people are referring to as templating
> (that is, string based stuff that may or may not represent DOM, but is
> almost certainly not "pure DOM") is not the intent (IE, we should use
> <script> for the cases discussed instead)... Does it make sense for
> the API to potentially reflect that and the draft to note it?  For
> example... could it either not have an innerHTML property or could
> that innerHTML return (empty string) or something?

Noting it might be useful, but shutting off .innerHTML doesn't make
sense.  It's still a DOM element, and contains HTML.

~TJ
Received on Thursday, 26 April 2012 18:26:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT