Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v4] Pseudo selector scale doesn't work on Firefox #13577

Closed
coolemur opened this issue Apr 25, 2024 · 3 comments
Closed

[v4] Pseudo selector scale doesn't work on Firefox #13577

coolemur opened this issue Apr 25, 2024 · 3 comments

Comments

@coolemur
Copy link

What version of Tailwind CSS are you using?

v4.0.0-alpha.14

What browser are you using?

For example: Firefox

What operating system are you using?

macOS

Reproduction URL

https://play.tailwindcss.com/9oZbag3cwc

Describe your issue

Pseudo element scale doesn't work in Firefox browser, while it works in other browsers

To reproduce, check hover effect and compare it in Chrome vs Firefox

@RobinMalfait
Copy link
Contributor

Hey!

This is an expected issue and by design. We use the new @property CSS feature which isn't available in Firefox yet. It will be once we release v4.

Right now, you can either use another browser or use Firefox Nightly (which does have @property support).

@HiggsWRX
Copy link

HiggsWRX commented Apr 26, 2024

Hey!

This is an expected issue and by design. We use the new @property CSS feature which isn't available in Firefox yet. It will be once we release v4.

Right now, you can either use another browser or use Firefox Nightly (which does have @property support).

Hey @RobinMalfait , would you mind clearing up something for me?

You say that firefox (not nightly) will have @property support when Tailwind v4 releases. But this means a lot of the features of TWv4 will not work for a lot of people since not everyone updates their browser that regularly.

Will this be polyfilled?

Will the firefox team themselves polyfill it to achieve backwards compatibility?

How will that work? It confuses me a bit because there's dozens of issues opened here because of the same thing, the team provides no fallbacks because "it will be available when TWv4 releases" and only says that a fallback/polyfill is "under consideration". How can that be?

@coolemur
Copy link
Author

coolemur commented Apr 26, 2024

Yeah.... "just use other browser" suggestion was very interesting indeed. And then issue closed instantly like this is solved...

Imagine service: "Your car aint working? Just buy new one".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants