Dashs method is much much faster for large select boxes- but since we are all building ajax solutions, a large select box *should* be a thing of the past (replaced with autocompleter) I've used it for a dropdown of suburbs on an older non-prototype web app that had an ajax call to load suburbs.
On 3/21/07, David Dashifen Kees <[EMAIL PROTECTED]> wrote: > > > Alternatively, you can also update the contents of the element > containing the select box. I've used that "trick" to try and get around > some of IE's quirkiness with respect to changing the contents of some > elements. For example, wrap the select element in a div and then > replace the contents of the div with a new select element. If you've > observing any events on the select element, though, you'll want to stop > observing them and then start once more when the replacement is > complete. Actually, I'm not sure you explicitly have to stop, but I've > run into situations where you do need to start observation once more > after replacing an element. > > -- Dash -- > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
