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

Hello all! have problem with type in md-input (beta.1) #2428

Closed
michael-vasyliv opened this issue Dec 27, 2016 · 1 comment · Fixed by #2431
Closed

Hello all! have problem with type in md-input (beta.1) #2428

michael-vasyliv opened this issue Dec 27, 2016 · 1 comment · Fixed by #2431
Assignees

Comments

@michael-vasyliv
Copy link

Bug, feature request, or proposal:

Bug, can`t set dynamically type for input
http://plnkr.co/edit/aCZljQ4EqtTdYhgbuP5y?p=preview

@devversion devversion self-assigned this Dec 27, 2016
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
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 kara closed this as completed in #2431 Jan 4, 2017
@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

Successfully merging a pull request may close this issue.

2 participants