-
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
disabled input on mat-checkbox not behaving like with other components #13739
Comments
|
@thomaspink You are correct. However, this is not a native checkbox, it still is an angular-material component and most would expect the angular-material components to behave the same way. In any case |
Fixes the `disabled` property not being coerced like all the other components. Fixes angular#13739.
Fixes the `disabled` property not being coerced like all the other components. Fixes angular#13739.
Fixes the `disabled` property not being coerced like all the other components. Fixes angular#13739.
Fixes the `disabled` property not being coerced like all the other components. Fixes #13739.
Fixes the `disabled` property not being coerced like all the other components. Fixes #13739.
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?
The disabled attribute/input should have the same behavior on all input elements.
What is the current behavior?
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material-checkboxes-hkdft7
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
6.1.10/6.4.7
Is there anything else we should know?
<mat-checkbox disabled>Foo</mat-checkbox>
used to work, not exactly sure when it broke.The text was updated successfully, but these errors were encountered: