Adding performant transitions rule to linter #708
Merged
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.
Using transition values that affect non-compositing rendering in the browser causes performance issues. For example, consider this div that moves 15px to the right on hover:
This transition requires the browser to do a re-layout, calculating the position of all elements. This transition would be much better suited to a transform, such as:
Using performant transitions makes animations run at 60fps and look smooth across browsers.
Rule Details
Rule ID:
performant-transitionsThis rule is aimed at creating performant web animations. As such, it warns when
transition,-webkit-transition,-ms-transition, andtransition-propertyare used with values other thantransformandopacity.The following patterns are considered warnings:
The following patterns are considered okay and do not cause warnings: