You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
For library maintainers that allow users to opt-in to animations, there is a gap in support - currently $animateCss is only available in ngAnimate. It would be useful to have a matching API in Angular itself with a $animateCss service, similar to how $animate is handled. The only way to detect if the user has $animateCss is to do a try-catch with fetching via $injector and swallow the exception, and fall back to $animate usage in that case.
The text was updated successfully, but these errors were encountered:
So you're saying to have a shell service in core for $animateCss? It only just sets classes and styles in the same way that the actual $animateCss service ngAnimate does just without any triggered animations.
A core version of `$animateCss` can now be injected when
ngAnimate is not present. This core version doesn't trigger any
animations in any way. All that it does is apply the provided from
and/or to styles as well as the addClass and removeClass values.
The motivation for this feature is to allow for directives to activate
animations automatically when ngAnimate is included without the need to
use `$animate`.
Closesangular#12509
For library maintainers that allow users to opt-in to animations, there is a gap in support - currently
$animateCss
is only available in ngAnimate. It would be useful to have a matching API in Angular itself with a$animateCss
service, similar to how$animate
is handled. The only way to detect if the user has $animateCss is to do a try-catch with fetching via$injector
and swallow the exception, and fall back to $animate usage in that case.The text was updated successfully, but these errors were encountered: