Could Tailwind agree to follow Widely Available Baseline? #15817
will-stone
started this conversation in
Ideas
Replies: 0 comments
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,
Congrats on the v4 release! However the browser support, in a professional setting, makes me a bit itchy. Chrome and Safari are March 2023 versions, so that's not so bad as we only have 8 months to go until that vital 2.5 year milestone. However, the supported Firefox version is July 2024 which was only about 7 months ago.
Rather than picking browser versions in order to use certain CSS features, would you be willing to state that TW will only support Widely Available Baseline features? This means you are free to refactor as new CSS features reach that milestone (as it's a rolling target), and the common industry standard can be adhered to by your consumers.
Here's one feature that you're using that won't reach Widely Available until Jan 2027: https://developer.mozilla.org/en-US/docs/Web/CSS/@property
Thanks for all the hard work!
Will.
Beta Was this translation helpful? Give feedback.
All reactions