-
Notifications
You must be signed in to change notification settings - Fork 6.8k
bug(mat-checkbox): Animation issue with Indeterminate state #25289
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
Labels
area: material/checkbox
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 17, 2022
…-checked to indeterminate Fixes that we weren't setting the correct animation class when the checkbox goes from being pre-checked to indeterminate. Fixes angular#25289.
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.
Labels
area: material/checkbox
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Description
When a checkbox is loaded with checked=true & indeterminate=false, the first time it changes to indeterminate=true the animation does not work properly. The checkbox visually goes to "empty/false" and then to the indeterminate state. Any further checked and indeterminate change after works properly with animations.
I've reproduced this on a checkbox-overview-example fork:
https://stackblitz.com/edit/angular-qtmlqq-t7otn9?file=src/app/checkbox-overview-example.ts
Reproduction
Steps to reproduce:
Expected Behavior
Animation between checked and indeterminate state on indeterminate state change true => false. (checked = true)
Actual Behavior
Animation bug: change indeterminate state does not animate properly the first time.
Environment
The text was updated successfully, but these errors were encountered: