-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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-input input text is not grayed-out when disabled #1884
Comments
Will likely be obsolete by |
very similar issue using reactive forms. using this form code the md-input is not disabled. Adding the disabled keyword, angular forms generates a warning. form = new FormGroup({ |
The same is happening with
I receive this warning:
However, initializing a |
fixed by #2513 |
I am using 2.0.0-beta.8 and I still have this problem |
@pantonis It appears to be working correctly, did you install a theme? https://material.angular.io/guide/theming |
No nothing. I have to call enable(), disable() to make it work |
I think the disabled styles live in the theme css, so that's probably why it doesn't look right. |
?? :) |
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. |
Bug, feature request, or proposal:
Bug
What is the expected behavior?
When the md-input is disabled, the input text should be grayed-out. The expected behavior is documented in Google design here:
https://material.google.com/components/text-fields.html#text-fields-labels
What is the current behavior?
Input text is not grayed-out.
What are the steps to reproduce?
Please refer to this plunk: http://plnkr.co/edit/fzZY5ASZ2vQlhOci8z9P
Note that the input text is the same intensity, whether or not it's disabled.
The underline, however, does correctly change to a dotted line when disabled.
What is the use-case or motivation for changing an existing behavior?
User can't tell whether the input is disabled or not.
Which versions of Angular, Material, OS, browsers are affected?
Angular 2.1.0
Material 2.0.0-alpha.10
Linux
Chrome
Is there anything else we should know?
No.
The text was updated successfully, but these errors were encountered: