Ensure --spacing-*
variables take precedence over --container-*
variables
#15180
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.
Fixes #15146.
This PR updates the
w-*
,max-w-*
,min-w-*
, andbasis-*
utilities to make sure that--spacing-*
values are preferred over--container-*
values when there is a conflict.Given this theme configuration:
…utilities like
max-w-sm
will use8px
instead of256px
after this change.Users can still be explicit about the value they want to use if they've introduced a naming collision like this by using our variable shorthand like
max-w-(--container-sm)
.