I’m Dudley Storey, the author of Pro CSS3 Animation. This is my blog, where I talk about web design and development with , and . To receive more information, including news, updates, and tips, you should follow me on Twitter or add me on Google+.

web developer guide

my books

Book cover of Pro CSS3 AnimationPro CSS3 Animation, Apress, 2013

my other blogs

Massive Head Canon: Intelligent discussion of movies, books, games, and technology.

my projects

A Sass color keyword system for designers. Replaces CSS defaults with improved hues and more memorable, relevant color names.

CSSslidy: an auto-generated #RWD image slider. 3.8K of JS, no JQuery. Drop in images, add a line of CSS. Done.

tipster.ioAutomatically provides local tipping customs and percentages for services anywhere.

Cross-Browser Development: Can You Avoid IE8?


Estimated reading time: 2 minutes, 10 seconds

The reality is that you may well have to deal with the issues mentioned in the previous entry, and more, when trying to make your site work in IE. Many businesses have standardized to “Microsoft only” and use Internet Explorer as their default browser, despite well-known security risks associated with doing so. Even worse, many institutions have built their websites solely to the features of IE, to such a degree that upgrading to a browser that attempts to follow standards – even later versions of IE – breaks the website.

In most cases you can at least attempt to convince the client to upgrade their browser, if they choose to stick with IE: any later version is better than IE6. You may also be able to build an argument for dropping support for certain browsers based on market share statistics.

Please keep in mind that web browser market share numbers are notoriously imprecise: different sites will draw different types of audiences, and thus a different array of browsers. Ultimately, the only way to have any degree of certainty is to look at the server logs for your own website, or to use a tool like Google Analytics. Of course, those techniques only provide information once your website is up and running.

Personally, I refuse to develop for IE6. The browser is now more than a decade old, represents less than 0.3% of visitors to this site, and is not worth the time and associated stress to develop for, at least to me.

However, you may not have that choice… and your client will always expect the site to appear perfectly in whatever browser they use, including IE 7 or 8.

Even if you do convince the client to drop support for earlier versions of IE, you should ideally continue to provide a path for users of the browser to view and use the site. Blocking your website to particular browsers is not the way forward, as a general rule. My personal recommendation is to use ChromeFrame, equivalent to giving IE a brain transplant). If the client is absolutely adamant in her support of IE, or if the audience numbers demand supporting the browser, you should add the extra demanded time to your contracted hours in developing the website. As a very rough heuristic:

  • Supporting IE6 and later increases the development time of a website from 50 ~ 100%, depending on design and features.
  • Supporting IE7 & 8 and ignoring IE6 adds 20 ~ 25% to estimated development time.
  • Supporting IE9 and 10 only and disregarding earlier versions adds only 10% to development schedules, in most cases.
comments powered by Disqus

This site helps millions of visitors while remaining ad-free. For less than the price of a cup of coffee, you can help pay for bandwidth and server costs while encouraging further articles.