Use attribute selector instead of class to avoid prefixing the wrong class #17
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.
This PR swaps any usage of
.lead
in our default CSS for[class~="lead"]
to avoid a unexpected output when generating the responsive variants of theprose
class.Currently, Tailwind always adds the responsive prefix (
sm:
for example) to the last class in a selector, and only that class. That means that before this PR, we were getting output like this:Notice how the second selector is incorrect, it should be
.sm\:prose .lead
for the plugin to behave the way people expect.Tailwind's behavior is justifiable and makes more sense in a lot of circumstances, which means this is a hard problem to solve at its very root.
This solution is sort of a temporary-but-maybe-permanent workaround until we decide if there's a good way to solve this in Tailwind itself.