-
Notifications
You must be signed in to change notification settings - Fork 28
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
sm-dropdown on-change function called on scroll #34
Comments
From what I noticed the on-change is called incorrectly. So there it should be:
Basically with a new selection added, the callback returns n*2 (n is the number of selected items). |
Is this repository followed anymore? |
Greetings Florinmtsc! The on-change attribute is tied directly into the Semantic UI library and is not evaluated by this library. You should check your Semantic UI version and if you are up to date perhaps try to report the issue in the main SUI repository. There are plans to eventually change to using the ngModel directive which would allow you to use the ngChange event. But I don't know when I'll get to that. There are a few other odd issues with smDropdown depending on how you are using it (I've experienced them myself but no one has reported them yet) - and those issues would be addressed in the next version as well. |
Thanks for your response. I'll try to implement the ngModel and create a pull request. Hopefully my time will allow this wish. |
Hello guys,
First, congratulations on the work you have provided and many thanks for the useful functionality you provide. There is some weird behavior with the on-change function callback.
I have the following usage of the sm-dropdown component:
The text was updated successfully, but these errors were encountered: