On Jun 1, 10:15 am, Dean Edwards <[email protected]> wrote: > On 01/06/2011 00:53, RobG wrote: > > > On May 29, 3:14 pm, Andrew Dodson<[email protected]> wrote: > >> Isn't that what its supposed > >> tohttp://www.w3.org/TR/selectors-api/#nodeselector > > >> <http://www.w3.org/TR/selectors-api/#nodeselector>Whats the difference in > >> Chrome, FF? nodelist is non-live in all of them. > > > The authors of the selector API could have saved a bit of confusion by > > giving their collection a name other than NodeList. In all DOM > > specifications, NodeLists are live. Perhaps the object returned by the > > selector API should have been called a StaticNodeList. > > It was originally called "StaticNodeList".
Snap! > I don't know when it was > changed. I guess the thinking was, that in terms of the methods they > provide, they are identical. The only differences are internal. To me the live/static thing is a bit more than internal. ;-) Since "NodeList" doesn't hint that it's live, having StaticNodeList might have helped in that regard too. Cest la vie. -- Rob -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
