Unresponsive script problem

Hi,

Just wanted to add my two bits worth. I'm running into the same problem as well.

Multiselect causes javascript to lock up with a nodereference field if there are about 1000 potentially selectable nodes. Either a lock up, or it just takes too long to be practical.

Experienced this on Firefox 1.5.0.13pre, and Epiphany 2.14.1.1, both on Ubuntu 6.06.

If I comment out line 110 in multiselect.module, like so:

// drupal_add_js($path . '/multiselect.js');

the error/warning box doesn't trigger, but neither does the multiselect widget work properly (obviously).

I looked in multiselect.js, but didn't see anything obvious.

One thing I can suggest is that maybe javascript just falls over in general when manipulating that many items, and it's not necessarily the logic in multiselect.js.

I have written a code to load the list of existing email id list in asp.net page using Ajax autocomplete control. It works fine on local machine but it dosent work on server.
it shows me error :

"Warning: unresponsive script / A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete."

Please tell me what is the problem?

ravindrapatil, please file a new bug under the Ajax Checklist module, not under Multi select.

has anyone found a solution to this script problem?

The problem is something like this: This widget keeps two lists, one of selected and one of unselected items. On page load, the items are all in the selected list, and the ones that aren't actually selected are moved (one at a time with javascript) to the unselected list. This initialization is what takes so much time. Probably it should be that the lists are properly populated server-side. I'll start working on this and post a patch when I've got something.

Testers much appreciated ;)

I have run into the same problem. Please let me know if there is anything that can be tested.

I expect a significant increase in performance with the beta. Please let me know how it works for you.

Thanks very much masipila. I'll get your patch uploaded soon.

Regarding your comment on sorting, are you interested in sorting the list of selected nodes?
Specifically, I want the order on the right to be induced by the person using the form. So if you want A,B,C or C,B,A you can order them that way. Unfortunately, there isn't yet an easy tool to do this, apart from adding them in the order you want them to be ordered. I do not plan to have the list of selected nodes be ordered in any way besides the order they are selected on the form, unless I can be convinced that this will be useful to more people than it is detrimental. I do have plans to include a simple "move up" and "move down" button to make it easier to reorganize the selected list.

If there were a way to sort the selected entries, how do you think it should work? I would very much like to avoid putting functionality into javascript unless it also exists server side. It's my intention to make this module completely functional (though probably quite cumbersome) with javascript disabled. If you come up with something would you open a new feature request ticket?

Thanks for the input masipila, and the patch.

Im going to resolve this, as I'm convinced that the issue of "unreponsive script" messages occured based on the sorting being done client side with javascript. Sicne that's no longer the case. I'll be resolving this. (your other issue regarding sorting and internationalization exist elsewhere masiplia)