Arbitrary variants adding unwanted prefix #8932
Unanswered
michaeltugby0
asked this question in
Help
Replies: 1 comment 1 reply
-
Just had a look at that PR, and I think what may be happening is that after the first pass, the custom variant gets added to a map. So, on the second pass, it finds the variant in the map, hence it skips the logic to toggle Saying that though, I don't have a good understanding of the code behind tailwind, so my assumption here may be off. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Attempting to upgrade to the latest version of Tailwind, but I'm hitting a little issue with the new arbitrary variants adding prefixes to classes.
For example, if I do
[&>.child]
, if I only use this variant once, it's fine. But, every other time I use that variant in the same class list, it will add an unwanted prefix to the start.Example here.
I'm also aware of a recent bugfix that was done to this here, which is probably related?
Beta Was this translation helpful? Give feedback.
All reactions