Awesome, glad I wasn't just cracking up. It took me a while to figure out I only got undefined coming back when it was unattached, but I hadn't traced it through the internal code. Seems there's no need now. Here's hoping savetheclocktower fixes it for all 4 methods- it's definitely useful if you want to wrap things up in small functions like I do, meaning you dont have direct access to the child dom elements. I've patched my code for now to just use childNodes[1].childNodes[0] to get to where i want- i dont know if down(2) will work.
Gareth On Dec 22, 2007 9:59 PM, kangax <[EMAIL PROTECTED]> wrote: > > hmm... > > Last commit http://dev.rubyonrails.org/changeset/8448 actually > fixed .down issue as it now uses .select instead of .findElements, but > up/prev/next still suffer from this... > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
