You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
In October 2020 Microsoft stops the support under win 7 for IE11 and later on for more current versions, it will be best to update the source code to counter this change since other Frameworks stopped supporting IE11 awhile back.
The text was updated successfully, but these errors were encountered:
As much as I would love to stop supporting IE11 and force users to update, our internal customers (particularly web search) have very stringent support needs and are generally pretty averse to being the forcing function for people to upgrade their browser. So it's a non-starter for Closure to take on this role. We do have internal issues tracking support requirements for legacy browsers, and we do push on them from time to time, and remove support once all stakeholders agree. But right now the discussion is over IE9, not IE11.
IE9 is not supported since March 31, 2017, but a Seperation for IE support can make code support more easily, clients with modern code can strip IE specific code while IE users get dedicated code for them!!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In October 2020 Microsoft stops the support under win 7 for IE11 and later on for more current versions, it will be best to update the source code to counter this change since other Frameworks stopped supporting IE11 awhile back.
The text was updated successfully, but these errors were encountered: