-
Notifications
You must be signed in to change notification settings - Fork 24.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
Animations: consider dropping CssKeyframesDriver in favor of WebAnimationsDriver #44520
Comments
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
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. |
This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This should decrease the bundle size, since most of the code was non-tree-shakable. Closes angular#44520.
This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This should decrease the bundle size, since most of the code was non-tree-shakable. Closes angular#44520.
This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This should decrease the bundle size, since most of the code was non-tree-shakable. Closes angular#44520.
This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This results in ~7KB decrease of the animations package bundle size, since most of the code was non-tree-shakable. Closes angular#44520.
This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This results in ~7KB decrease of the animations package bundle size, since most of the code was non-tree-shakable. Closes angular#44520.
…ar#44903) This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This results in ~7KB decrease of the animations package bundle size, since most of the code was non-tree-shakable. Closes angular#44520.
… (#44919) This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This results in ~7KB decrease of the animations package bundle size, since most of the code was non-tree-shakable. Closes #44520. PR Close #44919
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. |
…ar#44903) This commit removes CSS keyframes-based code that was used to support animations in old browsers. With IE11 deprecation, all supported browsers have native WebAnimations support, so the old code can be removed. This results in ~7KB decrease of the animations package bundle size, since most of the code was non-tree-shakable. Closes angular#44520. PR Close angular#44903
Which @angular/* package(s) are relevant/releated to the feature request?
animations
Description
Currently we have 2 implementations of the animations driver:
We select which one to use in this code based on the presence of the
animate
function in an element's prototype (see here). Since IE is no longer supported, theanimate
function should be available in all supported browsers, so it looks like we can drop theCssKeyframesDriver
in favor ofWebAnimationsDriver
.The biggest benefit that we'd have is less code in app bundles, the way those classes are referenced is non-tree-shakable (see here): both classes would be retained in an app bundle when the
BrowserAnimationsModule
is used. That'd probably save a few KB.If we decide to do that, it'd be great to implement and land the tooling to measure the bundle size and retained symbols first, see #44437. In this case we'd be able to measure the impact of this change.
The text was updated successfully, but these errors were encountered: