feat: use commas instead of slash for css color opacity modifiers #1514
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
slashes are not supported currently in Gmail, resulting in the entire style attribute or tag being discarded
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.
This PR adds support for Tailwind CSS opacity modifiers like
bg-black/80ortext-white/40in email clients such as Gmail, where forward slashes are not supported currently. In the particular case of Gmail, this results in the entire style attribute or tag being discarded.We use
postcss-color-functional-notationto convert CSS color values containing/to their,-based equivalents:<style> .bg-black\/80 { - background-color: rgb(0 0 1 / 0.8); + background-color: rgba(0, 0, 1, 0.8); } .text-white\/20 { - color: rgb(255 255 254 / 0.2); + color: rgba(255, 255, 254, 0.2); } </style>