Likewise for complex values like clip-path and filter this can have the overhead of number -> string conversion.
This PR adds support for the linear() easing function. So when an easing isn't supported by WAAPI, we generate a linear() easing function instead of pre-generating keyframes.
Currently, when a WAAPI animation is defined with an easing function:
Or an easing name not supported by WAAPI:
Then Motion will pre-generate keyframes for this animation and run it with
linear
easing.This can have poor performance characteristics: https://issues.chromium.org/issues/41491098
Likewise for complex values like
clip-path
andfilter
this can have the overhead of number -> string conversion.This PR adds support for the
linear()
easing function. So when an easing isn't supported by WAAPI, we generate alinear()
easing function instead of pre-generating keyframes.