Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiselect does not trigger the "change" event on the original <select> #75

Open
Unibozu opened this issue Sep 18, 2013 · 1 comment
Open

Comments

@Unibozu
Copy link

Unibozu commented Sep 18, 2013

Hi,

Could not find any information about it on the documentation or the wiki. From what I have seen when using your widget, it does not trigger the change event like most multiselect/combo boxes do.

Which is quite convenient : the underlying JS code does not have to rely on the fact that a jQuery plugin is used to function properly.

In my own code, I used the custom event "multiselectChange" but I think this would be more convenient to be able to bind this native event.

Cheers,
Clement

@yanickrochon
Copy link
Owner

Yes, I am aware of this. This was going to be in the next push.... whenever I can manage to free myself of other projects and finally fixed most, if not all, the currently opened issues!

As for now, you can modify the code quite easily by changing the line 35 of the source code and replacing the value "multiselectChange" to "change". This behavior is from a pre-beta release that slipped through the cracks.

See also #58. Also affects #20.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants