Adding support for all easing types with WAAPI #1830
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattgperry
changed the title
back/circ easings to WAAPI
mattgperry
changed the title
back/circ easings to WAAPI
mattgperry
force-pushed
the
fix/waapi-easing
branch
from
f0a15c2
to
67fe861
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WAAPI doesn't support all the same easing functions as Framer Motion.
In this PR we detect easing functions we can approximate with a
cubic-beziercurve and do so.For those that we can't approximate, we generate keyframes.
In the future for remaining easings it will be possible either to generate
linear()easings in supported browsers (currently none).