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

Remove IE11 compatibility code and target feature #2571

Merged
merged 6 commits into from
Oct 15, 2020
Merged

Conversation

adamwathan
Copy link
Member

This PR (targeting v2.0) drops any deliberate compatibility with IE11. Anyone who still needs IE11 support can use v1.x, which is still awesome (and the only version that even exists currently! 😋 )

This includes:

  • Removing the target feature, which was always semi-experimental and never documented
  • Removing fallback colors, which drastically reduces CSS file size (now we just ship the rgba values, no fallback duplicate declaration in hex)
  • Removing the IE11-compatible versions of the transform/rotate/scale/skew/translate utilities

In a future PR I'll be updating our preflight styles to remove IE 10/11 fixes.

@SjorsO
Copy link
Contributor

SjorsO commented Oct 15, 2020

A lot of the projects I work on need IE11 support because our customer's customers need it. That won't change any time soon. Being stuck on Tailwind 1.0 will be a bummer when there's already a version 2.0 (and later 3.0, 4.0, 5.0...). I think most companies using Tailwind for B2B software are in the same boat.

@adamwathan
Copy link
Member Author

What's wrong with Tailwind 1.0 for you currently that will push you to need 2.0?

@adamwathan adamwathan merged commit 1c8c078 into master Oct 15, 2020
@adamwathan adamwathan deleted the drop-ie11 branch October 15, 2020 19:21
@SjorsO
Copy link
Contributor

SjorsO commented Oct 15, 2020

What's wrong with Tailwind 1.0 for you currently that will push you to need 2.0?

I don't necessarily need 2.0, 1.0 already works great. I'm just worried that being a major version behind is going to be a hassle, because it usually is. I can't really think of any specific problems, but being behind a major version is never a good thing.

I think I'd much rather be on the latest version, but have some core plugins disabled.

@javascriptjedi
Copy link

I was eager to use the blocklist capability in the latest purgecss which isn't available in 1.9.x. My organization is not dropping IE11 for about another year.

@javascriptjedi
Copy link

There is the workaround provided here at least https://tailwindcss.com/docs/controlling-file-size#setting-up-purge-css-manually.

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

Successfully merging this pull request may close these issues.

3 participants