[docs] Bring clarity about the IE 11 support policy: it's partial #25262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliviertassinari
commented
Mar 8, 2021
docs/src/pages/getting-started/supported-platforms/supported-platforms.md
Outdated
Show resolved
Hide resolved
oliviertassinari
changed the title
mbrookes
approved these changes
Mar 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview: https://deploy-preview-25262--material-ui.netlify.app/getting-started/supported-platforms/#browser
This is a follow-up after #25222. Since the last time, we talk about the support policy of IE 11 in #14420, this happened: Next.js issues with IE 11. Iterating on issues with IE 11 has become very painful. Our development environment crash when loaded in IE 11. While the cost of working on IE 11 has increased by a large amount, the value is also continually going down.
It seems that we have reached a point where the opportunity cost for improving the support of IE 11 will very rarely outweigh the value of the alternative problems we can spend time on.
Hence, I'm taking the time to upgrade the documentation to be very transparent about what's the current status of IE 11. Basically, we don't plan to remove IE 11 fixes in v5. We don't really care about fixing new issues either. If the community is doing the legwork on a specific issue, and it only comes with a minor downside for the many, then, sure, we would be happy to accept the patch.