-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Hello all! have problem with type in md-input (beta.1) #2428
Comments
devversion
added a commit
to devversion/material2
that referenced
this issue
Dec 27, 2016
* Developers are currently not able to use property bindings for `required`, `disabled`, `type` and `placeholder`. * This commit ensures that the Angular input setters are in sync with the native input element. * Adds test to ensure that the property bindings work for the native input element (and not for the component instance as before) Fixes angular#2428
devversion
added a commit
to devversion/material2
that referenced
this issue
Dec 27, 2016
* Developers are currently not able to use property bindings for `required`, `disabled`, `type` and `placeholder`. * This commit ensures that the Angular input setters are in sync with the native input element. * Adds test to ensure that the property bindings work for the native input element (and not for the component instance as before) Fixes angular#2428
devversion
added a commit
to devversion/material2
that referenced
this issue
Dec 27, 2016
* Developers are currently not able to use property bindings for `required`, `disabled`, `type` and `placeholder`. * This commit ensures that the Angular input setters are in sync with the native input element. * Adds test to ensure that the property bindings work for the native input element (and not for the component instance as before) Fixes angular#2428
Merged
6 tasks
devversion
added a commit
to devversion/material2
that referenced
this issue
Jan 4, 2017
* Developers are currently not able to use property bindings for `required`, `disabled`, `type` and `placeholder`. * This commit ensures that the Angular input setters are in sync with the native input element. * Adds test to ensure that the property bindings work for the native input element (and not for the component instance as before) Fixes angular#2428
kara
pushed a commit
that referenced
this issue
Jan 4, 2017
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Bug, can`t set dynamically type for input
http://plnkr.co/edit/aCZljQ4EqtTdYhgbuP5y?p=preview
The text was updated successfully, but these errors were encountered: