![]() ![]() For Internet Explorer 8 and below, the audio and video playback works with Windows Media Player ActiveX component.And they won't get any quicker if nobody is willing to make the move to a newer system. This technique, I've seen used on quite a few sites, and I think works well.īut, I understand that many educational/corporate systems are slow to update their software to support the latest versions of browsers/operating systems. I believe a notice politely informing the user that their browser is outdated and insecure, and with a link to a page offering the user the possible alternatives, and instructions on how to get them set up on their computer. All it takes is to update to a system that is capable of auto-updating to newer versions (like any modern browser). Think of it like an investment, the quicker we stop supporting these old browsers, the quicker the uptake of newer technologies. And the only way people will stop using it, is if it stops working! The only way this problem is going to go away, is if people stop using it. Not to mention you’ll have fewer browsers to test while I understand your position, you're only thinking about the now, not the future.īy continuing to support these old browsers, we become the perpetuators of this very problem. Once you stop worrying about legacy IE versions, your web development will be easier and more cost effective.ĭifferences in supported features between IE10 and IE11 (which you still need to support) are not great, but the benefits are bigger if you drop IE9 and IE8 support. Window Servers are most likely used by power users who use modern alternatives for their browsing or realize the consequences of using legacy browsers.įor further details on browsers supported on Windows Servers and Windows Embedded Operating Systems check this page. IE on Windows Servers 20ĭon’t do anything here. Be aware that Chrome will stop support for Vista in April 2016 so it won’t be a safe alternative anymore. You could use conditional comments and display message recommending Firefox or Opera to them. ![]() ![]() I don’t think this was a reason to fix your site in IE9 either. Windows Vista SP2 lifecycle ended on April 11, 2017, so it was still possible that some of your users used a patched version of this browser in 2016. What about those users which might be using the old but patched IE versions? IE9 users on Windows Vista SP2 If your site breaks in IE10, IE9 or IE8, let it break and force users to look for safer alternatives. From there, they can create an exploit for the unpatched browser.Įven if a relevant number of your users still use legacy IE browsers, do not support them. In this case, the vulnerability found in, say, IE9 on Vista - which was patched this week - may give them insight into the location of the bug in the older IE8. The danger with known, but unpatched vulnerabilities is significant: Cyber criminals regularly parse updates and compare “before” and “after” code to determine what was changed. As Gregg Keizer states in the above article: In fact, it’s highly probable that nine recently fixed vulnerabilities in Internet Explorer also exist in IE7 and IE8, and in IE9 and IE10 on Windows editions ineligible for patching. However, in the case of the old IE versions we need to look at that in context:ĭon’t we encourage risky behaviour by our users if we support insecure browsers? In general it’s thought that if a browser has more than 1% share in your statistics, you should support it in some form. **** only up to version 36 Don’t encourage risky behaviour ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |