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

md-select should emulate select behavior with [value] and (change) #2459

Closed
mbellezi opened this issue Dec 29, 2016 · 4 comments
Closed

md-select should emulate select behavior with [value] and (change) #2459

mbellezi opened this issue Dec 29, 2016 · 4 comments

Comments

@mbellezi
Copy link

mbellezi commented Dec 29, 2016

Bug, feature request, or proposal:

feature request

What is the expected behavior?

md-select should support the property [value] for change it's value and the event (change) when a new value is selected. This way, it can be used as a direct replacement in code using select.

What is the current behavior?

It does not implements the property [value] and the event (change)

@crisbeto
Copy link
Member

The change event will be added with #2458.

@kara
Copy link
Contributor

kara commented Dec 29, 2016

@mbellezi It's also worth noting that it's already compatible with both Angular core forms modules. Using formControl or ngModel to track value and changes will already work.

Closing as a dupe of #2248

@kara kara closed this as completed Dec 29, 2016
@mbellezi
Copy link
Author

mbellezi commented Dec 29, 2016

In a regular situation, I agree. But, when you are using the component to build composed components which will use the formControl or ngModel itself, this is very useful.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants