You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, using a prefix seems to break css generation in many ways. I've found many different cases where this breaks. I documented some of them in the reproduction URL above, but they all seem to be caused by the combination of a prefix, @apply, and using arbitrary values. See examples below:
Note: For all of these examples, I'm using the prefix "@", but I've tried other prefixes (like "a") and it breaks in the exact same way.
Reporting this issue on behalf of myself and @isaacchong1
What version of Tailwind CSS are you using?
3.0.24
What build tool (or framework if it abstracts the build tool) are you using?
This bug occurs in the Tailwind CLI, via postcss, on Tailwind Play. I believe this bug happens everywhere.
What version of Node.js are you using?
16.14.0
What browser are you using?
Issue is browser independent, but I'm using: Brave Version 1.36.116 Chromium: 99.0.4844.74 (Official Build) (64-bit)
What operating system are you using?
Pop_OS!
Reproduction URL
https://play.tailwindcss.com/WQ2sVWOAqj?file=css
Describe your issue
As the title says, using a prefix seems to break css generation in many ways. I've found many different cases where this breaks. I documented some of them in the reproduction URL above, but they all seem to be caused by the combination of a prefix,
@apply
, and using arbitrary values. See examples below:Note: For all of these examples, I'm using the prefix "@", but I've tried other prefixes (like "a") and it breaks in the exact same way.
Transition with a single value works:
Result:
Transition with multiple values breaks:
Result: (note that there's no class name anymore)
Multiple box shadows:
Result:
ERROR: Cannot read properties of undefined (reading 'filter')
The text was updated successfully, but these errors were encountered: