I actually tried this, and it doesn't seem to matter. I know that's strange. And it bugs the heck out of me, as to why that would be the case, but if the DOM was complex enough to start out, it doesn't seem to matter. I tried updating the contents to be empty, and I still got the little skip.
Also, I realize the reflector script is pretty wasteful, and I probably will just do the reflections in a image program. The reason I put it in, was because the interface will be maintained by people who might find creating the reflections a bit outside their realm. Also, even if I take out the reflection, it still worries me to know the script has this limit imposed on it. If in the future the contents grow to something more substantial, I could just end up with the same problem again. Thanks for the suggestions. On 1/11/07, Ian <[EMAIL PROTECTED]> wrote: > > If the problem is that when you have complex DOM contained in the li, > why wouldn't you clear all the DOM information THEN removeChild / > style.left the UL? People will likely notice part of the step change, > but it may not be quite as noticeable. > > Just a thought. > > - Ian > M9 Corp > http://www.m9corp.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
