Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Remove IE9/IE10 support and other legacy browser #829
I was just looking over the Edge release history. Microsoft has already released 3 major (public) versions of the new browser. And since IE11 hasn't been updated in 3 years, I vote we drop support for it entirely.
For further evidence that retaining IE11 support is a bad idea, I point to Microsoft's IE End of Support article, which claims IE11 will stick around and remain supported for the lifetime of the OS on which it is installed. IE11 ships with Windows 10, which itself has a support lifetime lasting until at least October 2020.
We cannot hold ourselves back for the next 4 years because IE11. It's time to drop this piece of crap like the ... piece of crap it is!
Besides, if anyone really wants to use melonJS on IE11, they can just use an older version of melonJS...
On iOS, Opera Mini does have an option called "Turbo Mode" which just changes the server-side rendering into a GUI for iOS WebKit. See: https://dev.opera.com/blog/opera-mini-8-for-ios/#turbo-mode So it has the same feature footprint as the native Mobile Safari.
This was referenced
Dec 18, 2016
referenced this issue
Feb 13, 2017
I can lend a hand with this. I presume we'd want unit tests running at least on Chrome and Firefox to make sure we didn't get regressions; #890 adds Chrome execution, Firefox would be easy too.
Probably a good place to start would be to add code coverage reports and check what places that use obsolete code are not under test, start with tests, proceed with replacement.
that would be great, help is always appreciated/awesome :)
Probably they could be added in this test unit :
i'm not sure though about the browser and browser version to use, as regression are more likely to happen WHEN using a polyfill ?