As more companies migrate to Windows 7, the uptake of Internet Explorer 8 and now Internet Explorer 9 is booming – and it needs just as much careful attention. In fact, if you haven’t got plans in place for IE8 or IE9, it will hold up your move to Windows 7. Anyone considering IE9 should also be aware that it is unsupported on XP.
Web applications have become hugely important to most businesses. They’re closely integrated with critical business processes, and there are far more of them than ever before. This means the move to IE8/ IE9 could cause you and your IT system serious pain if you don’t prepare properly.
Here are some tips based on field experience:
IE9 doesn’t ‘break’ anything
It’s important to state that Internet Explorer 8&9 will not break websites. It’s just that sites specifically developed for IE5, 6 or 7 have a unique way of handling HTML and CSS code, so they may not function as expected when accessed through IE8/IE9.
Poor compliance isn’t just an IE8/IE9 issue A site that does not comply with web standards is just as likely to fail in any browser as it is to fail in IE8/ IE9. If the developer has properly catered for multi-browser usage, there shouldn’t be a problem. If they’re not standards-compliant, IE8/IE9 is just one of their problems.
Know your web app estate
You need to know how many web apps you’ve got and where they are. Do you have the time to ask your in-house developers what apps they’ve built? Do you have the time to fully audit your users and check your in-house web servers including Sharepoint? More to the point, will your users actually respond to the audit? My advice is to get your desktop monitoring agent working for you and get to the detail.
Plan and Test
Your goal is to prove that each of your apps and web sites work and look how they should on IE8/IE9. Create a Test Lab and test your internal and external web-sites. There is software out there to help automate the compatibility status but ensure that you back this with real expertise. Remember your business consumes web apps as well as provides them to others so include your customers and suppliers. Automated testing is not enough. Seeing is believing and you need to look at how the web app displays. You must check for full web app functionality, performance, usability and accessibility.
Buy time, but carefully
You don’t have to move every web app to IE8/IE9 straight away. But alternative serving strategies — or moving some apps and users to other browsers — are only ever a temporary solution. If needed, give users IE6 or IE7 in a slightly different way, such as:
- Virtualised Desktop
Remember though, it’s a sticking plaster – you’re vulnerable and are you supported?
Putting IE8/IE9 in Compatibility View
This is not a silver bullet. Compatibility View will fix most rendering issues but websites will still be subject IE8/IE9’s higher security model and architectural changes. Use it to extend the life of a web app when needed, but don’t make it the ultimate solution. Avoid over-customising IE8/IE9 or you’ll be back where you started. Better to remediate the apps whenever possible.
Don’t forget browser plug-ins
Each plug-in is essentially a full-blown app in itself. Think about things like:
- Adobe Reader
- Map navigation plug-ins
- Specialist apps
- Access to databases
- Business Objects reports…
You’d be surprised how many plug-ins your users can deploy. Try to capture them in the user survey and remember to include these in your desktop strategy!
You may know what you’re doing, but don’t assume everyone else does. Don’t take it for granted that 3rd parties will necessarily remediate for IE8/IE9, especially if they’re a small company. By all means contact them but don’t expect fast turnaround of fixes. Consider substitute apps if a developer is slow to be IE8/IE9-friendly.
Check browser performance
It doesn’t just stop with web app functionality. Performance issues can cause mayhem. Use a tool to assess website performance and plan your datacenter/deployment strategy accordingly.