Isn't the difference that the scriptaculous one only gets child nodes from the node you specify, whereas the prototype one gets all in the entire document?
Still, it would be nice to just have the one, and let you pass in the document element if you wanted all of them. Just guessing, really. I haven't looked at the code in question. Greg > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:rails-spinoffs- > [EMAIL PROTECTED] On Behalf Of Jeremy Kitchen > Sent: Monday, April 17, 2006 12:40 PM > To: [email protected] > Subject: Re: [Rails-spinoffs] document.getElementsByClassName (prototype) > andElement.childrenWithClassName (scriptaculous) redundancy? > > On Monday 17 April 2006 11:24, Jeremy Kitchen wrote: > > Is there a reason scriptaculous provides what appears to be a redundant > > function? The reason I'm asking is that it only seems to be used twice > > throughout all of scriptaculous, and it doesn't appear to work properly > > (for some reason it's returning the actual element, rather than an array > > with all of the elements) > > actually, it is working properly, the function that is calling it is > simply > interpreting the results incorrectly :) > > However, there's still that redundancy. I've filed a ticket about this > here: > http://dev.rubyonrails.org/ticket/4766 > > any input would be greatly appreciated :) > > -Jeremy > > -- > Jeremy Kitchen ++ [EMAIL PROTECTED] > > In the beginning was The Word and The Word was Content-type: text/plain > -- The Word of Bob. > > And the lord said unto John; Come forth and receive eternal life. John > came > fifth and won a toaster. _______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
