Robin Malfait

Hey! This is done on purpose because we everything is stringified into a CSS string. While unlikely, this also solves an issue where some calculations could result in valid TypeScript...

Hey! This should be fixed by #14561, and will be available in the next alpha release.

Hey! Thanks for the PR. I solved this in another way in #3801 where we weren't properly resetting the `touch-action`. The `touch-action` was only set on elements _outside_ the dialog...

This should be fixed by #3788, and will be available in the next release. You can already try it using: - `npm install @headlessui/react@insiders`.

Hey! Tailwind CSS v4 works with nested CSS internally, and you can write your own CSS as nested CSS. Tailwind also emits nested CSS. That is what you see in...

Hey! Right now we do rely on a specific set of browser versions to ensure that all features in Tailwind CSS v4 work as expected: https://tailwindcss.com/docs/compatibility#browser-support By default in development...

@rrmesquita that seems like a separate issue to me. If you can open a new issue for this that would be awesome 🙏

Hey! What's happening here is that during development, Tailwind CSS itself doesn't super care about the actual values being used as long as the structure is the same. This sort...

Hey! Going to close this issue because the difference between dev and build mode is expected right now. Tailwind CSS relies on nesting internally, and all supported browser should handle...

Hey! I can confirm that I see the bug in Playwright tests, and I can get it to work using an explicit timeout: ```diff // Test case 1 test("show dialog...