docs(rules): name translate and scale in a transition, never transform - #881
Merged
Conversation
Tailwind v4 compiles translate-*/scale-* to the standalone translate and scale properties, so transition-[transform] animates nothing and fails silently. Adds the two sibling traps in the same family: an inline style="transition" beats every class, and re-inserting a keyed node discards its pending transition.
herbert-julio-azion
approved these changes
Aug 12, 2026
isaque-bock-azion
approved these changes
Aug 13, 2026
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
3 participants
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.
What
Tailwind v4 does not compile
translate-*/scale-*to thetransformproperty — it compiles them to the standalonetranslateandscaleproperties. Sotransition-[transform,opacity]names a property those utilities never set, and animates nothing.This fails in the worst possible way: the class compiles, the utility is emitted,
vue-tscand ESLint pass, the element ends up in the right place — and no motion is ever interpolated. Nothing in the toolchain can catch it.Why now
Two components were shipping this exact bug, and finding it took measuring frames rather than watching the screen. The rule adds the two sibling traps in the same family, both equally silent:
style="transition: …"beats everytransition-*class, so a component that sets one discards any transition a consumer puts on that element;It closes with the method: verify motion by sampling the animated property across
requestAnimationFrameand asserting there are interpolated frames. A snap and a 150ms ease are indistinguishable by eye in review.Scope
Shared rules ship separately from code (
.claude/rules/git-workflow.md). This is the rule alone; the two component fixes that motivated it follow in their own PRs and cite it.