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

Re: [DOMCore] Attr

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 10 Sep 2010 07:48:51 -0700
Message-ID: <AANLkTimViDStB3qg4Li_0YJf1GeiReBF_2DXLUXDcNg=@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Ojan Vafai <ojan@chromium.org>, Maciej Stachowiak <mjs@apple.com>, Jonas Sicking <jonas@sicking.cc>, Boris Zbarsky <bzbarsky@mit.edu>, "Olli@pettay.fi" <Olli@pettay.fi>, Adrian Bateman <adrianba@microsoft.com>, WebApps WG <public-webapps@w3.org>
On Fri, Sep 10, 2010 at 5:35 AM, Anne van Kesteren <annevk@opera.com> wrote:
> 3) We can drop the concept of Attr being an object altogether. I do not
> think this is doable compatibility-wise, but not having Node.attributes,
> Attr, and just using getAttribute/getAttributeNS/setAttribute/setAttributeNS
> would be very nice complexity-wise.

I know that I've written code that depends on Node.attributes, when I
was just looping through all of the attributes for some reason
(usually because I was transforming the element into something else,
and just wanted to transfer all the irrelevant attributes over).

This code would happen to break with approach #2 as well, but the
relevant code I've written was minor and shouldn't be used by anyone
else, I think.

~TJ
Received on Friday, 10 September 2010 14:49:43 GMT

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