W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: Making <template> play nice with XML and tags-and-text

From: Elliott Sprehn <esprehn@gmail.com>
Date: Tue, 7 Aug 2012 23:45:39 -0700
Message-ID: <CAPJYB1hm5z+VFXauer2JP0fMDbu2XVtmcJN+M_vOt8fXSQ=V6A@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: Adam Barth <w3c@adambarth.com>, Adam Klein <adamk@chromium.org>, WebApps WG <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>, Rafael Weinstein <rafaelw@chromium.org>
On Sun, Aug 5, 2012 at 7:00 AM, Henri Sivonen <hsivonen@iki.fi> wrote:

> On Wed, Jul 18, 2012 at 11:35 PM, Adam Barth <w3c@adambarth.com> wrote:
> > On Wed, Jul 18, 2012 at 11:29 AM, Adam Klein <adamk@chromium.org> wrote:
> >>
> >> On Wed, Jul 18, 2012 at 9:19 AM, Adam Barth <w3c@adambarth.com> wrote:
> >>>
> >>> Inspired by a conversation with hsivonen in #whatwg, I spend some time
> >>> thinking about how we would design <template> for an XML world.  One
> idea I
> >>> had was to put the elements inside the template into a namespace other
> than
> >>> http://www.w3.org/1999/xhtml.
> On the face of things, this seems a lot less scary than the wormhole
> model. I think this merits further exploration! Thank you!
This proposal seems worse than wormhole parsing because the interface of
the template nodes is not HTMLElement, unless we're assuming it's a
different but identical namespace?

For instance it's super weird if <img src="x"> is missing the .src property
because it's not in the HTML namespace, but suddenly when it's cloned for
instantiation it's back in the HTML namespace and has the src property.

- E
Received on Wednesday, 8 August 2012 06:46:26 UTC

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