W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] Use cases for Node.getElementById

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 08 Dec 2008 14:31:53 -0800
Message-ID: <493DA059.90103@sicking.cc>
>> I see the Element interface no more contains methods to handle Attr 
>> nodes: since those are described as not being child nodes of an 
>> Element, in W3C specifications, there will be any other way to handle 
>> attributes as nodes, the 'nature' of Attr nodes is going to change, or 
>> is there a too little use (and/or support) of them, such that the Attr 
>> interface might be quite close to its 'end of life'?
> I'm not sure what to do with attributes. I'd like to drop support for 
> attribute nodes (being moved around, etc), if possible, but keep the 
> .attributes list and be able to use .value etc on each attribute.

Oooh, this is an interesting idea. It'd be great if we could make 
attributes not be nodes but rather some other type of object.

Ideally I'd like for them to not exist at all, and have people just use 
getAttribute(NS) instead. I've never thought that their usefulness 
outweighed their complexity.

/ Jonas
Received on Monday, 8 December 2008 14:31:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:46 UTC