What is the logic behind v4 not supporting older browsers

[boga001]

Hey guys,

First to congratulate you on the great tool you have provided us. Using tailwind has been a really nice experience and I could not imagine working without it in the future. It is something I will definitely use wherever I can.

I was thinking about v4 and it's support for older browsers related to v3. In my eyes the v4 is not really viable for any of my projects and will have to stick with v3 for a while.

But also what about when you start a new project. You would probably go with v4 and work on it only to find out that you need to downgrade to v3 in order to support a bit older browsers.

[wongjn]

From #14119 (comment):

We only do major versions every few years so we try to always use them as an opportunity to jump on fairly new platform features so that two or three years down the road the framework is already ready for them and we don't feel like we have to pump out a new major version every 12 months.

This was also the case with Tailwind CSS v2.0 where CSS variable support became a requirement to use the framework. A lot of people weren't totally comfortable with them yet, but now in 2024 we'd look like a framework from the stone age if we weren't taking advantage of them.

[boga001]

Thanks for the reply. This explains it. Maybe there should be something clearer regarding the minimum requirements for v4 so that people could understand what they are getting into by using v4 instead of older versions.

I think we can agree that is not really clear as it should be from the start.

[wongjn]

There is a page on minimum supported browser versions at least.