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

Re: Element.create(): a proposal for more convenient element creation

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 8 Aug 2011 09:59:05 -0700
Message-ID: <CA+c2ei92vRysuBSA2_rZ2Nny__QR_7Pjykf65gri6BzqX4nUkg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Dominic Cooney <dominicc@google.com>, WebApps WG <public-webapps@w3.org>, Maciej Stachowiak <mjs@apple.com>, Garrett Smith <dhtmlkitchen@gmail.com>, Anne van Kesteren <annevk@opera.com>, Glenn Maynard <glenn@zewt.org>, Aryeh Gregor <ayg@aryeh.name>
On Mon, Aug 8, 2011 at 9:17 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Mon, Aug 8, 2011 at 1:17 AM, Jonas Sicking <jonas@sicking.cc> wrote:
>> Is there a reason to support namespaced attributes at all? They are
>> extremely rare, especially on the web.
>>
>> Ideally I'd like to deprecate them, but I suspect that's not doable.
>> But I see no reason to support them in new APIs.
>
> SVG requires namespaced attributes for xlink, at least.  We're
> planning to get rid of that in SVG2, but for now it would be
> necessary.
>
> We could, of course, just say "Too bad, don't write things that need
> the xlink namespace, and wait for SVG2 to get rid of them".  I don't
> think this would be very bad.

Yup, that's my take on it. It's easy enough for people to write two
lines of code instead of one for now.

/ Jonas
Received on Monday, 8 August 2011 17:00:10 GMT

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