Material: docs(animation): provide guidance on overriding/disabling animations for each component

[robertmesserle]

We should provide documentation and code samples to show users how to override or disable animations for each component.

[marcysutton]

@ThomasBurleson let's chat about this one.

[nitin7dc]

+1

[recursionbane]

What is the recommended workflow to resurrect this request?
Ideally, we would have an md-disable-animations tag that would hierarchically disable animations.
Barring this, a per-component document on disabling animations is required for low-bandwidth streams via NoMachine and VNC.

[takotuesday]

:+1:

[ryanohearn]

+1

[agustingimeno]

Automated test would run faster if there is no need to wait for transitions and animations, so +1

[Splaktar]

This is also related to https://github.com/angular/material/issues/864.

[tomasdev]

864 has been fixed. This feature would be particularly useful on e2e tests.

[Splaktar]

864 has been fixed. This feature would be particularly useful on e2e tests.

It was closed by Naomi w/o any explanation, but I don't believe that any kind of consistent "light animation mode" was ever implemented.

We do support disabling Ink Ripples across the application but that doesn't address animations for things like md-checkbox which doesn't use $animate for it's checked/unchecked animations, or dialog opening and closing animations (which seem to cause some extra garbage collection).

You can disable ngAnimate animations, which are used for dialog and many other components, via $animate.enable(false).