W3C home > Mailing lists > Public > public-webapi@w3.org > March 2007

Proposal in regards to dom node selector utilities

From: Daniel Aquino <mr.danielaquino@gmail.com>
Date: Wed, 28 Mar 2007 19:20:03 -0400
Message-ID: <66f0f93e0703281620uf2a65b7w46bb771e02190014@mail.gmail.com>
To: public-webapi@w3.org
i see now that fx3 will support getElementsByClassName (gebcn) and if you
ask me there is way to many functions that do the same thing ...
getElementBy<whatever>... well a while back i was writing a simple dom
parser and instantly thought why not something that could take a list of
attributes to match against... well i rolled out a prototype and with some
help of others it works very well now and i called it ...
getElementsByAttributes... i really believe this one function can whipe out
all others... here is my current implimentation...

Also I know about the specification for getElementsBySelector ... but I
believe my method offers some things that are missing from that spec... Like
supplying your own test function and testing by hasChildNodes would
literally execute the method and test the result.

Could someone get back to me and let me know what they think about this ?

Received on Saturday, 31 March 2007 13:37:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:23 UTC