Increase specificity of * and ** variants
#14920
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
RobinMalfait
changed the title
* and ** variants* and ** variants
RobinMalfait
force-pushed
the
fix/reduce-specificity-on-children-variant
branch
from
beb1234 to
69732cd
Compare
RobinMalfait
changed the title
* and ** variants* and ** variants
adamwathan
reviewed
Nov 8, 2024
adamwathan
force-pushed
the
fix/reduce-specificity-on-children-variant
branch
from
5aed7dc to
867bb7e
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.
Increase the specificity of the
*and**variants. This will now use:is(…)instead of:where(…).In Tailwind CSS v3 we used
& > *instead of:where(& > *)which means that this isn't a breaking change anymore.This also allows us to use codemod things like
[&>[data-visible]]:flexand[&_[data-visible]]:flexto*:data-visible:flexand**:data-visible:flexrespectively.