-
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
fix(material-experimental/mdc-progress-spinner): fix noop animation #21359
fix(material-experimental/mdc-progress-spinner): fix noop animation #21359
Conversation
@include mdc-circular-progress-core-styles($query: animation); | ||
} | ||
|
||
// Render the indeterminate spinner as a complete circle when animations are off | ||
._mat-animation-noopable .mdc-circular-progress__indeterminate-container circle { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can target ._mat-animation-noopable .mdc-circular-progress__determinate-circle
directly. The specificity shouldn't matter since you're using !important
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was hoping so, but they apply the styles directly to the element dynamically so there's no way to override it via CSS unless we use !important
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant that changing the selector to the one I mentioned would reduce the specificity, but it won't matter if we keep the !important
.
…orking Seems like a regression from angular#21359. We can't use `:not` to apply the animation styles, because MDC's mixins target `.mdc-progress-spinner`, rather than `&`. These changes use the same manual approach as other components to disable the animations.
…ion not working Seems like a regression from angular#21359. We can't use `:not` to apply the animation styles, because MDC's mixins target `.mdc-progress-spinner`, rather than `&`. These changes use the same manual approach as other components to disable the animations.
…ion not working (#21391) Seems like a regression from #21359. We can't use `:not` to apply the animation styles, because MDC's mixins target `.mdc-progress-spinner`, rather than `&`. These changes use the same manual approach as other components to disable the animations. (cherry picked from commit 37a9c4e)
…ion not working (angular#21391) Seems like a regression from angular#21359. We can't use `:not` to apply the animation styles, because MDC's mixins target `.mdc-progress-spinner`, rather than `&`. These changes use the same manual approach as other components to disable the animations.
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. |
Animations were still being shown because the selector
:not(._mat-animation-noopable)
by itself matched plenty of parent elements. This specifies the right parent element that should be checked.Also, this forces the spinner to be a complete circle when there are no animations, rather than some odd looking broken spinner shape