Re: [csswg-drafts] [css-animations-2] Should the initial value for animation-duration be auto? (#6530)

I see that the latest decision is to retain backwards compatibility for `getComputedStyle().animationDuration` (returning `0s` instead of `auto`), which is great :tada:

I just wanted to mention (mostly for people that might run into this on some beta versions of Chrome/Edge) that the original proposal of having `getComputedStyle()` return `auto` for `animation-duration` breaks [CSS-based animations][1] in the [AngularJS (v1.x) framework][2].

> **Note**
> This only affects **[AngularJS v1.x][2]** (i.e. the old, end-of-life series) and _**not**_ the new **[Angular (v2+)][3]**.

##
I think this might also be useful as a data-point for future backwards compatibility considerations.

Although the AngularJS v1.x series is end-of-life, there are many (mainly enterprise) apps still running on one of the old unmaintained versions or using a patched version from a Long-Term Support provider, such as [XLTS.dev][4].

[1]: https://docs.angularjs.org/api/ngAnimate#css-based-animations
[2]: https://angularjs.org/
[3]: https://angular.io/
[4]: https://xlts.dev/angularjs


-- 
GitHub Notification of comment by gkalpak
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6530#issuecomment-1596708831 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 19 June 2023 08:06:19 UTC