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.
In order to determine the correct length of time to play a CSS-transition-based animation, animator.js attempts to parse the value of the transition-duration property of the element's computed style to a float value. However, it fails to account for cases where multiple transitions are specified. For example: transition-duration: 0.2s, 0.5s, 1s. Only the first value is parsed, which may be shorter than one or more than the others.
The result will be that the animation finishes before the transition is completed. If some action, such a DOM removal, is scheduled to take place after, it will result in the animation being cut off before it is completed.
The text was updated successfully, but these errors were encountered:
In case multiple durations are specified like so:
transition-duration: 0.5s, 3000ms;
transition-property: left, height;
The animator will pick the longest duration.
Fixesangular#2373
In order to determine the correct length of time to play a CSS-transition-based animation, animator.js attempts to parse the value of the transition-duration property of the element's computed style to a float value. However, it fails to account for cases where multiple transitions are specified. For example:
transition-duration: 0.2s, 0.5s, 1s
. Only the first value is parsed, which may be shorter than one or more than the others.The result will be that the animation finishes before the transition is completed. If some action, such a DOM removal, is scheduled to take place after, it will result in the animation being cut off before it is completed.
The text was updated successfully, but these errors were encountered: