-
Notifications
You must be signed in to change notification settings - Fork 6.8k
<md-autocomplete> needs change or select event on options #5096
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
Comments
This feature would be very wellcome with the "force selection" being tracked in here #3334. In fact, the efect you wish can be done as soon as you garantee the values of the input is one of the options - if the user left the component without selecting one option the input would be cleared. But it's a lot of code to do a simple thing. It could be present in the component out-of-the-box. |
@julianobrasil , thanks for reference, "force selection" will do component more flexible. About your decision for my case: manipulation with input doesn't work, because it isn't see local variable in option. |
I worked this case out with (onSelectionChange) in mdOption just now. Close the issue or this issue can be useful in other use cases? |
Better close. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I need a output event in
<option>
of<md-autocomplete>
when we choose it.I have a use case:
On choose autocomplete's option I need do some side effect with some local template variable (like
opt
in template). This template is working great. But on key interaction it doesn't work.(keyup)
doesn't work. It's need to add output event on option(choose)
,(select)
or(pick)
.The final result I want:
It must work for click and key interaction.
Thanks!
The text was updated successfully, but these errors were encountered: