[4.1.4] Introduced change that breaks modals as used by Laravel Jetstream

[dakira]

What version of Tailwind CSS are you using?

For example: v4.1.4-4.1.6

What build tool (or framework if it abstracts the build tool) are you using?

vite v6.3.5

What version of Node.js are you using?

v22.15.0

What browser are you using?

Chrome / Firefox

What operating system are you using?

macOS

Reproduction URL

https://play.tailwindcss.com/sM9n2CsDra

This is a sample modal from a fresh install of Laravel Jetstream. If you switch the Tailwind Play to v3.x, you'll see what it should look like.

Describe your issue

When I upgraded my Laravel 12 Jetstream project from TailwindCSS v4.1.3 to v4.1.6 I noticed that none of my modals are working anymore (using the modal component that ships with Jetstream). I narrowed it down to the problem being introduced with tailwindcss/vite@4.1.4.

In the Play above you can see that the inset background of the modal appears above the modal and it doesn't in 4.1.3 or earliert versions. In my packages.json I can actually set tailwindcss@4.1.6 and everything will still work, as long as tailwindcss/vite is < 4.1.4.

[philipp-spiess]

Hey!

It seems the culprit of this seems to be that this exampled relied on the transform class setting any value. You can see that in v3 it computes to an identity matrix (so basically doing nothing but keeping the value set):

When a transform value is set, it will create a stacking-context.

Now in 4.1.4 we landed a bug fix that changes the value of the transform class, if no transformations are applied to be empty. This causes the element to not get put into a stacking context.

Since there are no transformations on this element though, relying on transform to create a stacking context doesn't seem like a good idea. I suggest you add the isolation class to force the creation of a stacking context instead: https://play.tailwindcss.com/jNdDq2SPX0

Given that this appears to be an issue with Laravel Jetstream, I think it might be best if we can fix this upstream.

[dakira]

@philipp-spiess Hey Philipp. Thanks for the help. I'll add the fix upstream as soon as they switch to tailwindcss v4!