Original select not updated in real time?

[brunobg]

It seems that the original is not updated immediately when there is a change in the multiselect (does it happen only when the form is submitted?). This breaks a script that watches the original select for .change(). Is there a workaround? I though about a callback for multiselectChange, but I couldn't find a method that forces the update of the old select.... Any tips?

yanickrochon commented 11 years ago

The original element is modified real time, but there is no original "change" event. In the early dev of the widget, I had to bind to a change event too (as you can see in the demo page where the debug output changes as they happen, and toggling the original element shows the original selected values) and since I was triggering this from the widget, using custom ui parameter, it is using a namespace event called "multiselectChange"

However, after a quite short thought on the subject, I recognize the need that it should be a normal "change" event instead, triggered directly on the element to have a seemless behaviour. I'll update that later (and leave the original custom event in place with a deprecation notice).

... with the new jQuery convention, it should be named "multiselectchange" anyhow, but that will have to be documented as a release upgrade.

• © Githubissues.
• Githubissues is a development platform for aggregating issues.

[yanickrochon]

The original element is modified real time, but there is no original "change" event. In the early dev of the widget, I had to bind to a change event too (as you can see in the demo page where the debug output changes as they happen, and toggling the original element shows the original selected values) and since I was triggering this from the widget, using custom ui parameter, it is using a namespace event called "multiselectChange"

However, after a quite short thought on the subject, I recognize the need that it should be a normal "change" event instead, triggered directly on the element to have a seemless behaviour. I'll update that later (and leave the original custom event in place with a deprecation notice).

... with the new jQuery convention, it should be named "multiselectchange" anyhow, but that will have to be documented as a release upgrade.