Repository navigation
docs: add animation performance tips to the skills and core README - #315
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
The consumer skills and the core README now give tips for smooth custom keyframes:
opacity,transform,translate,scaleorrotate, because the browser can run them on the compositor.width,topormargin, because they cause a layout and a paint on each frame.will-changefor an entrance, because the browser treats an animated property as ifwill-changealready names it.Sources: MDN Animation performance and frame rate and
will-change.Checklist
nextbranch.!and aBREAKING CHANGE:footer.pnpm format:check, the unit tests andpnpm test:packagepass.