Often the reason given is that the corporate sector is tied to it through intranets and other applications that rely on it.
So, why not release IE6 as a single-site browser (SSB), like Mozilla's Prism for example?
- Corporates can run their intranets via the IE6 SSB
- The general-use browser can then be updated to the latest version (IE8), which has to make security easier for their IT department
- Microsoft can then officially drop support for IE6, and only need to support the SSB in its corporate environment
- The rest of us can breathe a sigh of relief as we watch IE6 usage fall rapidly!
It seems like a simple solution to me, but perhaps it's not that simple. Otherwise Microsoft would have done it already. Yes?
Its enteriely possible to make your own single site browser with the help of the MSHTML component and Visual Basic. I have done so to make help documentation in a project a lot easier.
ReplyDeleteHowever to upgrade the browser, I guess you would still need to have IE6 somewhere in the machine as a standalone component to prevent a new IE overriding the IE6 components... I doubt all system admins will have the perseverance to maintain such a project when they already have a simple, already there solution.
I think the people who have changed have changed, the ones who havent probably wont, but in the end when XP comes to its end of life and Microsoft dosent support it, that is the only time when we will see the true end of life to IE6.
Finally, is it really that much effort to make a web based app HTML complaint?
Internet Explorer 8 is very good because it is as stable as Opera. I hate the previous versions of IE like IE6 because it hangs frequently. *
ReplyDeleteInternet Explorer 8 have been my most used browser this year, it is definitely stable and fast loading too. "
ReplyDelete