fix(material-experimental/mdc-button): not disabling animations under noop animations module - #23027

MDC does provide the animations feature target which we could also exclude if animations are disabled. Just wanted to see here why we manually set the transition (just to be on the same page). I'd assume dealing with the animation feature query is rather complicated, increases specificity etc.? If so, that makes sense to me.

The problem is that MDC's mixins are written like:

@mixin mdc-button {
  .mdc-button {
    ...
  }
}

This means that the _mat-animation-noopable class has to be on a higher level in the DOM, whereas we set it on the button itself.

I see, that makes sense. Thanks for the clarification!

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.}