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
I assume the { after h-4 and mx-4 is somehow not considered a (possible) boundary anymore. I think this is likely a bug, as many template languages use { and } as delimiters in some way, so the possibility of a boundary should be taken into account.
The text was updated successfully, but these errors were encountered:
Yep this is indeed a regression will provide a fix soon. Small note: in Tailwind Play this will not work even after the fix because we only look at the class attribute without "running" your code. But in your real projects it will be fixed with the incoming PR.
What version of Tailwind CSS are you using?
v4.0.11
Reproduction
With the new extractor (#16306) the class
h-4
andmx-4
is not picked up anymore when using the following Twig template content:(See https://play.tailwindcss.com/w3SazyVehg for the example on Tailwind Play and the generated CSS)
I assume the
{
afterh-4
andmx-4
is somehow not considered a (possible) boundary anymore. I think this is likely a bug, as many template languages use{
and}
as delimiters in some way, so the possibility of a boundary should be taken into account.The text was updated successfully, but these errors were encountered: