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: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 6 Aug 2012 14:37:17 -0700
Message-ID: <CA+c2ei-90c-psY0owSHC6EBJk1HTWa4u7YbzFS04dwLMZX1A5w@mail.gmail.com>
To: Tony Ross <tross@microsoft.com>
Cc: Henri Sivonen <hsivonen@iki.fi>, 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 Mon, Aug 6, 2012 at 11:44 AM, Tony Ross <tross@microsoft.com> wrote:
> From: hsivonen@gmail.com [mailto:hsivonen@gmail.com] On Behalf Of Henri Sivonen
> Sent: Sunday, August 05, 2012 7:00 AM
>> 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!
>
> Just to clarify, is what you find scary about the other model the lack of support for XML, or something more?
>
> I've been under the impression we're trying to shield HTML developers from namespaces, so I'm a little concerned that this new proposal will move us in the opposite direction. Sure I'd like a proposal that works for XML too, but not if it means making the feature confusing for web developers.

I agree.

I feel like this proposal reduces some complexity in the parsing
model, at the cost of increasing complexity in a lot of other parts of
the system.

I'll also note that this doesn't help with things like querySelector
since that usually selects all elements with a certain localName,
independent of namespace. Likewise with getElementsByTagName.

Why is it that we are so much more concerned about the DOM-building
during XML parsing, than we are about DOM-building during HTML
parsing?

I think we for years have been complaining about XML parsing being too
different from HTML parsing in bad ways. HTML5 did some to help the
two move closer together. I'd rather continue on that path than create
more splits again.

I can certainly see being less concerned about introducing complexity
for XML users given that there are a lot fewer of those than HTML
users. Is that the reasoning here?

/ Jonas
Received on Monday, 6 August 2012 21:38:16 GMT

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