The Web is for everyone, not just people with the latest iPhone.

[babycommando]

Tailwind v4 Breaks on IOS <16.4 - we need a proper fallback urgently.

The problems have been reported countless times already and a few brave community members are even trying to propose solutions for it.

Tailwind adoption is churning for serious production deployed projects and definetly deserve some special attention from the core team.

V4 is effectively useless on iOS <16.4 (iphone X and below, ipads as well stuck on old safari versions - probably other older browsers and platforms as well like firefox on some linux installations, etc.), breaking sites entirely for a huge segment of users worldwide. This is very bad for business.

This isn't some minor inconvenience—honestly it’s a complete disaster for accessibility, usability, and developer sanity (if you care about it or just pretend to).

Are we seriously telling people to throw their older gadgets in the bin just to view a website properly? This is not a luxury issue. This is a fundamental failure in progressive enhancement, an awful accessibility policy.

There is no fallback to support minimally the millions of users with older phones and devices.

The Web is for everyone, not just people with the latest iPhone.

[philipp-spiess]

Hey there! Right now the browser support of Tailwind CSS v4 is documented here: https://tailwindcss.com/docs/compatibility It also states that iOS 16.4 is not supported.

We're aware of this being a major blocker for many websites and are thinking about adding a compatibility mode, though.

In the short term, it's still perfectly okay to use Tailwind CSS v3 which does not have the same limitations as Tailwind CSS v4. There's also another thread with potential workarounds posted here: https://v3.tailwindcss.com/docs/browser-support.

[weristwiegott]

@babycommando Man, just use v3. You don’t have to keep everything up to date in your project. v4 isn’t much better than v3 for development.

[babycommando]

hey @weristwiegott sound simple right.. turns out since the entire tailwind ecosystem like Shadcn, Headless, RadixUi and tons of community made components have already entirely migrated to v4, orchestrating that for specific versions quickly became a development hell. Mind boggling right? I could even handle it for my use case, but today I'm here for all the other devs suffering in those components libs's github issues.

And v4's new engine is pretty neat, x100 faster incremental builds - shame to miss that. Went from what a developer ever dreamed to the worst case scenario. Can't have everything in this life, but I hope some support comes out for the old toasters 🤣. Much respect for all helping to find solutions for that tho.

[weristwiegott]

@babycommando I went through that too. I run a SaaS, and some customers reported issues that made me roll back to v3. To be honest, I don’t miss v4 at all. Hopefully, they’ll find a way to fix those issues.

[nongtiny]

This might can be a ideas for you guys if you want to still using the v4.

Rather than compromise on the latest Tailwind CSS v4 features, my team is ensuring a consistent user experience across devices. We've implemented a controlled override process to address compatibility issues on older mobile platforms. By identifying and replacing unsupported CSS properties in our build, we maintain functionality and prepare for the future adoption of newer devices

[babycommando]

@nongtiny Manually patching entire component libraries to keep basic functionality just feels like a bit much, especially when considering using paid ones like Tailwind Plus for UI blocks.

Nice to see the community creative workarounds, but feels like a downgrade from "very fast shipping for the modern web" to "diy survival challenge try not to break everything while losing lots of time".

[Eptagone]

I created a workaround using Lightning CSS here. It's not perfect, but at least it worked for me to fix most colors and borders in Safari 15.