Remove opacity variables from :visited pseudo class
#7458
Merged
Conversation
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
tmattio
added a commit
to tmattio/opam-repository
that referenced
this pull request
Apr 9, 2022
CHANGES: ### Fixed - Remove opacity variables from `:visited` pseudo class ([tmattio/opam-tailwindcss#7458](tailwindlabs/tailwindcss#7458)) - Support arbitrary values + calc + theme with quotes ([tmattio/opam-tailwindcss#7462](tailwindlabs/tailwindcss#7462)) - Don't duplicate layer output when scanning content with variants + wildcards ([tmattio/opam-tailwindcss#7478](tailwindlabs/tailwindcss#7478)) - Implement `getClassOrder` instead of `sortClassList` ([tmattio/opam-tailwindcss#7459](tailwindlabs/tailwindcss#7459))
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.
The
:visitedpseudo-class has significant restrictions on what can be done with it for privacy reasons. You can read more about the limitations on the MDN article Privacy and the:visitedselector.Some examples:
var()are discarded (discovered this one via testing):visitedversion of the element/class.:visitedcolor if a color has already been set on the base property.:visitedlink.Tailwind CSS, by default, generates text opacity, border opacity, and background opacity variables that are used when applying the
text-{color},border-{color}, andbg-{color}utilities. This causes the utility to not work at all because the relevant color declaration is being treated as if it wasn't there at all.You can disable those plugins (which aren't necessary given that the color modifier syntax now exists) to work around the issue however it makes more sene for Tailwind CSS to handle this itself if/when it is feasible.
Fixes #7441