If your hobbies include Microsoft-bashing, then read on. The company has announced that their new Office Web Applications will officially support IE7, IE8, and Firefox 3.5 on Windows and Safari 4 on Mac. There is no mention of Google Chrome or Opera so, understandably, many fans of those browsers are working themselves into a paranoid anti-trust frenzy.
The Office Web Apps blog states that other browsers may work and users should try them. Browsers won’t be blocked and Microsoft’s goal is to ensure broad compatibility and reach.
This begs the question: why should you, Microsoft, or any other company commit to “official” supported browser lists?
As I discussed in my previous article, web sites and applications should be written for the web — not browsers. We should strive for systems that are device-independent rather than targeting specific OS and browser combinations.
To me, that is a ridiculous solution. Why show the icon if your browser does not support copying? The alert message does not help or provide the keyboard alternatives; it torments the user and suggests Firefox is inferior (is that Microsoft’s intention?)
We currently have five mainstream browsers, numerous offshoots, and multiple versions of Windows, Mac OS, and Linux. It is impossible to test web applications across every combination of OS and browser. Publishing a list of officially supported browsers has simply lead to criticism and suggests other negative connotations:
- Microsoft has not tested several popular browsers during development. Patching a product after release is far more difficult and time-consuming than comprehensive testing during the main development phase.
- Will Office work in later versions of IE, Firefox or Safari? The web application is not due until 2010 — Firefox 4 and Safari 5 could certainly be available.
What would have happened had Microsoft not announced their supported browser list? Very little…
- The Office web applications have not been released and will probably enter a beta phase.
- Opera and Chrome users account for a small percentage of the market.
- Only a proportion of those users would try the applications.
- Few of them should encounter compatibility bugs.
- Only a small percentage would report issues to Microsoft.
Microsoft might receive a handful of support requests, but that information could be invaluable when they attempt to fix compatibility problems.
If you’re developing the next big web application, maximum browser compatibility should be a priority:
- Componentize your code and unit-test in a variety of browsers.
- Test early and test often.
- Do not strive for unrealistic/identical cross-browser functionality.
- Use progressive enhancement to add features when the browser supports it.
Browser support lists are more trouble than they’re worth.
Craig is a freelance UK web consultant who built his first page for IE2.0 in 1995. Since that time he's been advocating standards, accessibility, and best-practice HTML5 techniques. He's created enterprise specifications, websites and online applications for companies and organisations including the UK Parliament, the European Parliament, the Department of Energy & Climate Change, Microsoft, and more. He's written more than 1,000 articles for SitePoint and you can find him @craigbuckler.