Feature Request: animation callbacks

[adamdport]

Bug, feature request, or proposal:

Feature Request

What is the expected behavior?

I have some way of being notified when material animations (such as opening/closing expansion panels) have finished

What is the current behavior?

There is no way to know when animations have completed

What is the use-case or motivation for changing an existing behavior?

Opening a connected CDK overlay (eg. a tour walkthrough) before the animation has completed can result in incorrect positioning of the overlay

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

5.0.0

Is there anything else we should know?

[mackelito]

This would be a great addition! Would be nice to be able to delay routing and so until animations are done :)

[seabass223]

As of Material ^5.1.1, I found
var EXPANSION_PANEL_ANIMATION_TIMING = '225ms cubic-bezier(0.4,0.0,0.2,1)'; in material-expansion.umd.js
until callbacks are supported, I can do a setTimeout for 225, which is a bit dirty, but gets the job done until callbacks.

[mackelito]

Found this ticket after several years and still longing for it :D

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.