We're using the auto_complete plugin to generate Ajax.Autocomplete calls. The way the page works is the user chooses an item from the autocomplete list, which populates the field with the full text of the item, and then clicks an 'Add' button which adds it to a list elsewhere in the page (and a hidden input) and clears out the autocompleting field so the user can add more items.
This works fine in Firefox no matter how the user interacts with the autocomplete box. In both IE6 and IE7, it's fine if the user uses the keyboard to make their selection (i.e., type some characters, arrow down, Enter or Tab). However, if the user uses the mouse to choose an item, it seems fine at first, but gets slower with each selection. The slowdown seems exponential: it is barely noticeable through the first few selections; around the seventh or eighth, it becomes unbearably slow. We see IE consuming 100 of the CPU while waiting for the selection to happen. We put some debugging statements into our code (as we specify an after_update_element option that we thought might be to blame) as well as controls.js to try to narrow down where the slowdown is. All the slowness is before our afterUpdateElement code is called. We put statements into the onClick of Autocompleter.Base and were surprised to find the slowdown doesn't seem to be localized to one call: each line runs very slowly. Having googled around, we haven't found any reference to similar issues. Has anyone seen anything like this? Any thoughts on what might be causing it? Thanks. -john. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
