Menu Search
Jump to the content X X

Today, too many websites are still inaccessible. In our new book Inclusive Design Patterns, we explore how to craft flexible front-end design patterns and make future-proof and accessible interfaces without extra effort. Hardcover, 312 pages. Get the book now →

Old Browsers Are Holding Back The Web

Because of how far certain Web technologies like HTML5 and CSS3 have brought us, many would say that—from a Web platform perspective—the future is now. Sounds like a cliché, I know. At the very least, it feels like the future is starting to bubble up to the surface… but it’s just not quite there yet.

When we use new DOM features, HTML5 APIs and the latest in CSS3, the possibilities that open up are astounding. These new technologies help us easily build Web applications with less reliance on hacks, plugins, images, and bloated scripts. This makes life easier not only for Web developers (for both building and maintaining these projects) but also for the end user who gets a faster and stronger overall experience.

But there is a huge road block preventing our “future” from truly becoming the now. What is this roadblock? It’s old browsers. Let’s delve into this topic a little bit so we can see why this is a problem and what we can do to help it.

Internet Explorer’s Usage Share Link

According to StatCounter estimates1, even with the recent mobile explosion, desktop usage still trumps mobile by a large margin. 90% of internet activity worldwide occurs on the desktop. Granted, some reports have mobile shares higher than the current 10% shown by StatCounter. Whatever the case is, the fact remains that a lot of people are accessing our websites and Web apps by using a desktop browser.

Which desktop browsers? Well, let’s look at StatCounter’s usage share for desktop browsers for May 20122, with a specific focus on Internet Explorer:

Stats for desktop browsers in May 20123

As shown above—to the joy of developers everywhere—worldwide stats for versions of Internet Explorer prior to IE8 are very low. IE6 is so low that it’s not even showing up in some of StatCounter’s charts anymore. If you find similar stats for your own projects, then, depending on the overall traffic numbers, you may be able to drop support for IE6 and IE7 and start using a number of features that those browsers don’t support. But what about IE8 and IE9?

As you can see from the image and link above, worldwide usage for IE8 and IE9 is just about 30%, combined. But that might not be the full story. Compare those numbers to the ones taken from two other websites.

First, Net Applications, from April of this year4:

Net Applications browser stats5

Their stats show a whopping 38% of users still on IE6-8, with more than two thirds of those on IE8. In addition, IE9 holds another 16% share. That’s more than 50% of users on IE6-9.

Now look at StatOwl’s April 2012 report6:

StatOwl browser stats7
Large preview8.

Like Net Applications, StatOwl places IE8’s and IE9’s shares significantly higher than StatCounter’s—this time about 20% for each. Combined with the 8% on IE6 and IE7, that’s almost 50% on IE.

The debate about why these different browser usage stats are showing higher numbers for IE6-9 is something that’s been in industry news of late. These details are certainly beyond the scope of this article, but you can check out the links below for more info:

Why Does This Discussion Include IE9? Link

IE9 is a huge step forward from previous versions of Internet Explorer. But it’s over a year old, and does not auto-update like other popular browsers do.

Thus, although IE9 is a much more stable and feature-rich browser, it’s already starting to show its age. With each passing month, browsers like Chrome and Firefox continue to roll out new features automatically, and IE9 gets closer to becoming obsolete.

Why Is The Old Browser Problem Such A Big Deal? Link

Some people might be thinking “What’s the big deal? Use progressive enhancement and you’ll just give old browsers a lesser experience and the users won’t know what they’re missing11”. This might be true with certain CSS3 and HTML5 features for which it’s easy to provide fallbacks and even some lightweight polyfills. But other more complex features are not that simple.

Let’s first take a look at IE8. To give you an idea of how many features IE8 lacks, here’s a list of what you gain as a developer when you stop supporting IE8:

  • Media Queries
  • opacity (without IE filters)
  • border-radius
  • box-shadow
  • RGBA, HSL/HSLA colors
  • HTML5 elements (that don’t need the html5shiv)
  • Data URLs
  • getElementsByClassName
  • CSS Transforms
  • <canvas>
  • Cross­origin Resource Sharing
  • Lots of CSS3 selectors (:nth-child(), :target, :enabled, etc)
  • matchesSelector
  • Navigation Timing API (performance.timing)
  • Multiple backgrounds
  • background-clip, background-origin, background-size
  • Real HTML5 Video/Audio with no messy fallbacks
  • WOFF Fonts
  • SVG images, inline SVG, SVG in CSS backgrounds
  • Geolocation
  • Server ­Sent Events

Also, this list doesn’t take into consideration the number of bugs and performance problems that occur in IE8. So when you consider all of the features above, along with bugs and performance issues, a high number of users still on IE8 becomes a major roadblock to progress on the Web.

Of course, this is not to say that support for these features is perfect in new browsers. Many of these features are still in flux in the spec. But a very high percentage of in-use browsers outside of IE8 have pretty good support for everything listed above.

What About IE9? Link

The problem, however, doesn’t end with IE8. As mentioned, IE9 is likewise starting to fall behind the other browsers. Here’s a list of the features you gain if you don’t have to support IE9:

  • text-shadow
  • Linear and Radial Gradients
  • CSS Transitions
  • Keyframe Animations
  • Web Sockets
  • 3D Transforms
  • flexbox layout
  • Multiple Columns
  • The <datalist> element
  • SVG Filters
  • Application Cache
  • pushState, replaceState
  • indexedDB
  • ECMAScript 5 Strict Mode
  • FileReader API
  • requestAnimationFrame
  • The async attribute for <script> elements
  • Many HTML5 form features
  • Native form validation
  • The <progress> element
  • Web Workers
  • XMLHttpRequestLevel 2
  • Typed Arrays
  • matchMedia
  • Blob URLs

As you can see from the two lists above, the old browser problem is a significant one. These new features (although still in progress) have the potential to help designers and developers innovate and push the Web forward in amazing ways.

Is IE[x] The New IE6? Link

The notion that “IE[x] is the new IE6” has been discussed12 before13, but it deserves more attention here. As of writing this, IE9 (the latest stable version of Internet Explorer), cannot be installed on Windows XP14 and, according to StatCounter15, about 31% of desktop internet usage is on that operating system.

Since a large number of IE8 users are essentially “trapped” in XP, there is no hope that those users are going to upgrade to a newer version of Internet Explorer unless they upgrade their OS.

For your own projects, I hope the stats for older browsers are much better. After all, the only stats that really matter are your own16. Also, the worldwide stats showing high numbers for IE6-8 are probably a little skewed by some densely populated geographic areas17. Nonetheless, usage stats for IE6-9 are still a factor for many projects and may thus be holding back a lot of developers (due to client or corporate pressure) from using many new features.

The point here is that if the usage stats for browsers like IE8 and IE9 linger for anywhere nearly as long as IE6 did, then those of us who are building websites and Web apps for a larger and more diverse audience could be in for a long wait (before using dozens of new features).

Usage stats for IE6–9 are still a factor for many projects and may thus be holding back a lot of developers.

Microsoft Provides A Glimmer Of Hope—Or Do They? Link

One positive development in this area is the recent announcement by Microsoft that XP, Vista, and Windows 7 users will be automatically upgraded to the latest version of Internet Explorer available for their operating system.

Unfortunately, while this news is better than nothing, it is not the ideal solution. A similar announcement18 was made back in 2008 regarding a so-called “auto-update” from IE6 to IE7. That 2008 update would only take place if a system was set to auto-approve Update Rollup packages. But a default setting in XP prevents this from happening—so this barely made a ripple in the IE6 problem at that time (as seen from the fact that IE6 usage was at 23% in January of 2009)19.

Similarly, this time around, users will be upgraded to a newer version of Internet Explorer only if they have turned on automatic updating via Windows Update. Also, the auto-update began in January and only for users in certain geographic regions. So again, although this is certainly good news, it’s not the ideal solution.

What Real Options Are There For Users Of Older Browsers? Link

Aside from people that are on systems that, for security or compatibility reasons, cannot upgrade their browsers, everyone that is using IE8 (or lower) has one of two options to help alleviate this problem—even if they’re on Windows XP. They are:

  • Don’t use Internet Explorer20; unlike IE9, all the latest versions of the other major browsers (Chrome, Firefox, Safari, and Opera) will run on Windows XP or later.
  • Install Chrome Frame; it’s easy to install and it makes IE function like Google Chrome.

With those two options there is no excuse for the high numbers of users still on older versions of Internet Explorer. Theoretically, everyone who is not on a locked-down system can upgrade to a non-IE browser or install Chrome Frame. This would likely bring the usage shares for older browsers down to a bare minimum, and would allow developers to bring even more of the latest technologies into common use.

A Note on Tracking IE with Chrome Frame Link

Some of the users still on old versions of Internet Explorer could have Chrome Frame installed, but in the browser usage stats referred to earlier in this post, those are still counted as Internet Explorer. It would be good to see Chrome Frame stats reflected in those applications.

Google Analytics, however, does include “IE with Chrome Frame” as a separate browser, and developers can check out the Chrome Frame developer documentation for info on how to detect Chrome Frame usage.

What Else Can We Do To Help? Link

If you have any friends or colleagues using an older version of Internet Explorer (or any old browser), help them upgrade to the latest version of Chrome, Firefox, Safari, or Opera. You might even want to show them a CSS3-rich or HTML5-rich website in a modern browser and compare it to IE8.

In other words, prove to them that their browser is an out-of-date, unstable, slow piece of software. You might even have a little fun21 trying to show them why non-IE browsers are better.

Display a Message to Users on Old Browsers Link

Another thing you can do is display a message to users if they’re visiting your website in an older browser like IE8. Don’t assume this is too intrusive. A couple of years ago, YouTube started phasing out support for many older browsers22. The message shown below is now displayed to users visiting the website with IE6:

YouTube's message for IE6 users

You could display a subtle yet noticeable message to encourage users to install Chrome Frame and make sure to include the necessary code23 that will enable Chrome Frame on pages that are being viewed with it. [However, also provide an option to close the message bar so that users who are stuck in a locked-down system (and have to use your website) can actually use it. —Editorial]

Tomorrow: A Message For Non-Developers Link

Most people reading this article are probably thinking “Yeah, that’s all fine and good, but you’re preaching to the choir, dude.” Many developers already know a lot of this stuff. And we also know that developers and designers are not the ones using older browsers like IE8 for everyday browsing. In fact, you’d be hard-pressed to find a Web developer that uses IE9.

That’s why tomorrow Smashing Magazine will be publishing a special post (the article is published now24) that will be targeted towards users who are not designers or developers, and who are not very tech savvy. We encourage everyone to share that article with as many people as possible so we can do everything we can to get the usage stats for old browsers as low as possible.


Footnotes Link

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
  20. 20
  21. 21
  22. 22
  23. 23
  24. 24

↑ Back to top Tweet itShare on Facebook


Louis Lazaris is a freelance web developer and author based in Toronto, Canada. He blogs about front-end code on Impressive Webs and curates Web Tools Weekly, a weekly newsletter for front-end developers.

  1. 1

    There is one more problem: Some companies i know are still on XP and IE7 is installed on theirs machine and nobody has admin permission so they can’t install another browser. So i think we have at least another year or two before we get rid of IE7 for good :(

    • 2

      Louis Lazaris

      July 9, 2012 7:22 pm

      True. But from what I understand, they can install Chrome Frame without admin privileges.

      • 3

        Thats true, but like most of us, you are assuming that those people would have the skills and savvy to know how to go about installing chrome in that manner. Also, the majority of those companies don’t allow individual desktops but push from a master image.

      • 4

        no you can’t, at least I can’t. Im a software engineer, btw. But in my work laptop I dont have any type of access. Ive tried to install the chrome frame but no luck. It sucks

        • 5

          Louis Lazaris

          July 10, 2012 12:41 am

          Then it must be different on a case by case basis, because Paul Irish told me that you don’t need admin privileges to install it.

          • 6

            No you can’t always do that. At at&t they had their systems locked down to XP/IE6 and I couldn’t install chrome frame.

          • 7

            Federico Brigante

            July 10, 2012 2:12 am

            I believe that Chrome Frame does not require admin privilege, however, admins can still whitelist applications so you won’t even be able to launch a “portable” version of your browser.

          • 8

            Tried installing Chrome Frame on work machines with no luck. Funny enough Chrome installs with no issues.

      • 9

        It’s true that corporate policies often do not allow users to upgrade their browsers, but the intended use is the internal intranet. Obviously, staff are browsing the web when maybe they shouldn’t (public sector, *cough*), but this should not be such an issue for us.

        Maybe we should start a corporate campaign to encourage organisations to at least install chrome frame?

        I think the article is a great idea, and will plaster it over Facebook (probably the biggest IE population).

      • 10

        The 40+ years old backoffice lady wont install anything^^
        The greed of Microsoft is just too huge. They sell the modern Browser ONLY with their latest OS and thats a shame.

      • 11

        Mark Thomson

        July 10, 2012 1:08 pm

        You can install Chrome as a full browser with out privileged on most locked down systems.

    • 12

      Just an FYI, depending on how exactly permissions are set, you may be able to install Chrome without an admin. Other programs can do this also (VLC Portable). So, you can try that.

    • 13

      The note about some companies still installing Windows XP is still a big issue. I work for a large state agency, and I couldn’t believe the amount of user internally that are still on IE 7 and 8. Nothing can be done to fix this, so it prevents us from using the great new toys html5 and css3 bring.

      Someone please make IE7 & 8 die so we can move on.

    • 14

      I think what you mean is that they have integrated their internal system with IE7. I worked with huge companies that still were locked with that few months a go.. (Can’t remember the name of the framework… anybody help me out here)

  2. 15

    Well said, my friend. Well said.

  3. 16

    Denny Dzulkarnaen

    July 9, 2012 5:40 pm

    Remember the time when flash based websites would present you with a download link to the flash plugin if flash wasn’t installed in your system, and you couldn’t progress any further until you have it installed? Let’s do the same with Chrome Frame.

    • 17

      OMG Please NO. That sucked

    • 18

      Lets think about it. Would you install a Software called “Chrome Frame” on your PC, if you are not a developer or internet known guy?

      In the daily news you hear about viruses, trojans and all the “the internet is evil” things. there must be a better solution

  4. 19

    While its very easy to agree theoretically … the harsh reality is that many clients (the one paying agencies) are still forced by their Enterprise IT department to use certain browsers – mostly IE in its older forms.

    It’s nearly impossible to convince a client that their browser is the extreme minority. They pay the bills – and they want it to work in their browser. period.

  5. 20

    I totally agree with most of the points in this article. Older versions of IE seems to be the biggest pain in my ass. I decided to take a stand a while back and not accept or seek any gigs that require IE8 (or prior) support. I don’t want my efforts to contribute toward “enabling” the problem to continue. IE9 is a huge leap forward but of course there’s more work to be done. It’s obvious MS is finally paying attention, and i’m excited to see what IE10 might offer. It seems that being knocked off the top will keep you honest, grounded, and humbled.

    I hope that a good chunk of this will be resolved once support for XP expires, and those people either upgrade or move on to another platform, but we can contribute to moving this along too. The more we freelancers and businesses continue to “support” or “enable” issues like these, the longer our nightmares live on.

  6. 21

    I wish someone would just develop a virus/trojan that installs Chrome Frame in the background :)

    • 22

      That would only encourge people to continue to use IE.

      • 23

        What do I care what their browser looks like ? As long as they’re actually using Chrome, I’m perfectly fine with their IE6 :). Thats what Chrome Frame was developed for!

    • 24

      That’s the best idea I’ve heard in a long time.

      Hopefully you’ve just sparked the idea in someone capable.

  7. 25

    While I agree with Greg, its the IT departments job to make sure they are doing everything they can to increase security and to decrease the chance of CPI theft and corruption. Keeping users on outdated software, especially IE, is a severe oversight and a failure to the companies infrastructure. More often than not, it comes down to the IT department not wanting to deal with the older culture of the company which comes with any major software update. It’s usually laziness.

    On a developers stand point, So much time and money is wasted on dealing with CSS/JS bugs that always arise in IE7/8. If we as developers could spend more time moving forward instead of working backwards, the web would be a much different place today.

    • 26

      A little late to the party her but…

      Having worked for the MOD, I can safely say it’s not always or even usually laziness on the part of the IT department. At my time of leaving there in 2008, they were just beginning to bring in Windows XP on users workstations, after a very lengthy review process making sure that all software & security was going to play nice with it. Luckily, they skipped straight to IE7, but I know for a fact that where I was, they haven’t been able to move forward from that. And it’s not for lack of enthusiasm on the part of the IT guys, their hands are just tied. It’s the same the world over for any large entity, it’s a time consuming and costly process.

      I think people who surf the web in their lunch breaks still deserve a fairly decent experience, so saying we’ll just drop support seems very unfair to them, it is after all not their fault.

      It’s all very well us developers saying we want to use the latest tech. and ‘stuff you’ if you can’t view our sites properly, but what’s the point in producing sites that only half the people visiting are able to see properly (depending on your target audience of course..). I’d love to just be using HTML 5 and css3 without any fall-backs or hacks, but it’s not the world we live in, we just have to deal with it. Perhaps we all need to learn a little more patience? Food for thought..

  8. 27

    YouTube should impose ie7-ie8-ie9 to be unsupported. It’ll obligate most older browser users to upgrade.

  9. 29

    Henrique Alves

    July 9, 2012 6:24 pm

    Great topic Louis!

    If you think globally the problem is bigger. I’m wondering if part of the problem is also because part of the population just can’t afford to buy a new pc/laptop/gadget every six months?

    For example Brazil has more than 50 million of internet users and most of them still using an old computer/laptop running windows XP.

    Anyway this is not a simple issue to solve and IMO Microsoft should do a bit more for move the web forward.


  10. 30

    If *everyone* simply stopped developing and/or taking into account the old browsers, then the stubborn hangers-on will give up and update their browsers once all the sites they visit don’t look/function correctly anymore (I hope!) and if not.. if think it’s time to adopt a ‘screw you’ attitude towards them! ; )

  11. 31

    We as developers are sort of guilty since we’re still developing and implementing cool stuff trying to compensate old browsers (ie only), what i generally do it’s i make them look ok, not amazing, and kind of implement a little bit of what you see on ( firefox, chrome) using jquery that being because if we keep trying to compensate and making your site look stunning on ie that will encourage then not to move forward getting a new browser (that’s why i said we spoiled them), i think that google do a terrific job letting them know that they can have a better browser /faster and with more features, also what we can do is start doing alerts with javascript / or another mild approach on our own projects or sites to let them know that there is life out there.

    I know that somehow where are doing that the clients want and they ask you for (ie support) and we can no say NO! right? but letting them know. This is how the sites behaves on modern browsers and this is IE and letting them know that is what, sometimes we miss or completely forget. So we can start educating clients, honestly how long it’s going to take for them downloading chrome the most 5 – 10 mins or as an alternative installing chrome frame, witch is great and they keep using the same crap that the are use to which i think that’s the main problem that some old folks just know that if the want to go to internet just push the E on the bottom and that’s all that they ever need.

  12. 32

    jamie paterson

    July 9, 2012 5:42 pm

    I use a little gracefull degredation – just a little. If they want a better view they will have to upgrade, simple as that. I see many sites when testing in IE7 that look completely different almost devoid of colour and style – that works for me too. Let’s keep moving forward…

  13. 33

    Kevinjohn Gallagher

    July 9, 2012 5:45 pm

    Aside from the fact that you are, as you say, “Preaching to the Choir”; we also must realise why the average person or organisation simply won’t care about any of this.

    To use your own argument:

    “Here’s a list of what you gain as a developer when you stop supporting IE8:
    – Media Queries
    – opacity (without IE filters)
    – border-radius
    – box-shadow
    – RGBA, HSL/HSLA colors”

    – Media Queries are rarely used for desktop sites to the point that it’s almost non-existent.
    – Opacity works fine on IE8, it just requires different code, in the same way that webkit browsers require different code than opera and firefox.
    – border radius and box-shadow. If this is what we consider to be “holding back the web”, by not allowing shadows on things, then lets turn the lights off and go home. It’s a nice to have. It’s simply not going to convince anyone that there’s anything wrong.
    – RGBA colours. you mean i have to use normal/been-around-for-years and still work fine hex colours? Oh the humanity !! Call Bob Geldof, lets set up a fundraiser!! Quickly, everyone upgrade, so we can output the same colour but written a different way.


    If we want people to upgrade their browsers, and we do, then we need to give them a good reason!!

    There needs to be a carrot and a stick. The positive for people and organisations has to be more than superficial, (there needs to be a net benefit for any change to be considered an upgrade) and as an industry our constant claiming that HTML5/CSS3/super-kittens are going to save the web and that everyone must upgrade to the latest nightly isn’t going to do it.

    We need to be able to show people that there is a real benefit to THEM, not a benefit to US because we get to write cooler or slightly less code, and that needs to be tailored against OUR expectation that a 1 year old browser (IE9) is close to obsolete. People in the real world can’t keep up with that rate of change, even with “auto-updates”.

    Constantly bashing IE, even when accurate, just comes across as childish and having a sneering superiority complex. “oh, you’re using THAT. ha. WE people in the know use something new and cooler.”.

    Changing from one piece of software to another requires a great deal of investment. Time, money, support, resistance to change, testing, deployment, loss in productivity. Thats not just in organisations or big business, but for each and every user, on every change in software. The hope is that the net gain is worth it. If we want people to undertake that for us, our argument can’t have “text-shadow” anywhere near it. We have to start talking in the language that USERS understand.

    Respectfully, we all need to come up with a better argument.

    • 34

      Louis Lazaris

      July 9, 2012 10:04 pm

      Kevinjohn, thanks for your comment. The thrust of this post was not just about the fluffy new CSS3 stuff; it’s the APIs and other big features that hold us back, really. The CSS3 stuff is just adding to that. You said:

      We need to be able to show people that there is a real benefit to THEM, not a benefit to US because we get to write cooler or slightly less code

      This article was for developers, tomorrow’s article will address those issues. :)

      • 35

        Looking forward to that article!

        Furthermore, I think that it’s also about convincing corporate managers. My guess is that most outdated machines can be found at large companies that don’t want to spend money on testing and rolling out new software for all work stations. You’ll often hear: “Why? The current software does it’s job, doesn’t it?”

        You’ll only convince these people when you prove that updating browsers can actually save money. The amount of reasons for that can be vast, but there need to be some kind of proof.

    • 36

      It’s true, a feature list doesn’t convince users or managers.

      We could link to some incredible demo collections like …

      … and indicate that the experience for these incredible experiences in IE8 is close to nonexistent.

      Or we could try to tell a story about adding a attachment to your email, or uploading a photo to a website. In older browsers you need to deal with the pesky “Choose File” dialog, navigating your folders in a tiny window; but in newer browsers you can just drag and drop all files into a big target dropzone and the browser does the rest.

      Now, that’s a very feature based upgrade, and speed is another huge difference. And comparing modern day IE and Chrome to IE8 is just a huge stark difference, but I don’t think many folks think differently than the linear version numbers would suggest small improvements.

    • 37

      I’ve grown tired of all the fancy tricks in the webpages and wish a lot of that stuff designers find so wonderful could just be turned off. Lightboxes… hate them, hover over menus, I just want to click to pop them up, too many times I slid my pointer and accidentally selected something there and lot a huge comment. Slideouts…I’m trying to read the story…go away. Jquery… on a slower computer, it times out and you get a blank page…. can’t you just render the page on the server and send me the result? Excessive javascript… can freeze a slower computer and make it impossible to even scroll.

      Pretty much… I want the content and not all the flare… things that designers find crucial…I plain find annoying

  14. 38

    Newer versions of IE will always become the next IE6, untill IE gets auto-update.
    Personally, I completely ignore ie6 now, but still try to make websites look as nice as they can be, in ie7 (and up).
    I’m not a big fan including a lot of javascript libraries to make stuff work in lower IE versions, so the only script I use for that is mediaqueries.js.
    I wish we could simply ignore IE all together, but I think it’s our job to to make the web look nice for everyone.

  15. 39

    It’s more than a browser issue. Many small businesses and PC owners invested in XP, which can no longer update past already-outdated browser versions. The investment to get a new OS can be prohibitive, so they’re hanging in there as long as they can.

    • 40

      Louis Lazaris

      July 9, 2012 7:21 pm

      That’s only true for IE. Any XP users can upgrade to the newest version of a different browser, or they can install Chrome Frame.

      • 41

        Hemender Jha

        July 11, 2012 8:05 am

        I am fully satisfied with Louis Lazaris. I have window xp in my pc and I upgrade my browser time to time. I have not face any problem in it even yet.

  16. 42

    Nicholas C. Zakas

    July 9, 2012 6:44 pm

    I think it’s unfair to say that old browsers are holding back the web. That would imply that old browsers represent the majority, which you have already shown is not true. The real problem is the development mindset. Just because older browsers are around doesn’t mean you don’t get to use new features, it just means you need to think a little bit more carefully about how to implement things.

    No one is holding you back from using newer features that the now-majority of users can experience. This is exactly what progressive enhancement is all about. There are plenty of resources out there with guidance on how to build beautiful, useful web experiences that don’t leave older browsers hanging.

    The web development community as a whole needs to stop blaming old browsers and start thinking differently about how we’re doing things. As long as there are new browsers, there will always be old browsers. Instead of waiting for that situation to change, we can get a head start by changing the way that we think about web development.

    • 43

      Louis Lazaris

      July 9, 2012 7:18 pm

      Good points, Nicholas.

      Here’s the way I look at it, though:

      Old browsers don’t have to be in the majority to disrupt your workflow or prevent you from using certain new features. I don’t think anyone can say that they’re supporting IE8 and they’re using all the features listed in this article. Thus, to me, that amounts to holding back the web.

      Also, if you (or any developer) could choose not to have to support IE8, would you do it? I’m not saying that’s a realistic choice for everyone, but hypothetically speaking, if you had the choice, which would you prefer? Obviously, everyone would rather not support IE8. So if that’s the case, then it’s true: old browsers are holding back the web, because they’re disrupting our workflow and our ability to confidently use many new features.

      And on the progressive enhancement point: Yes, of course, I think all good developers do that. However, some features are just impossible to use if you have to support 20-30% of users on IE8. You either end up polyfilling (which causes big performance and maintenance problems) or else you avoid certain features altogether. As I mention in the article, progressive enhancement works for stuff like CSS3, but not so much for some of the new APIs.

      Anyhow, I agree with your point about the mindset of developers, we definitely have to just get down to solving problems, which I think we’ve done reasonably well now for over a decade.

      • 44

        Stefan Morris

        July 9, 2012 9:37 pm

        Most developers I know already have this mindset, however the problem is the additional overhead required to develop the same site in IE. I my opinion, that is the biggest issue. And it’s not a ‘laziness’ thing – developers I know would rather spend their time moving forward on their projects rather than trying to figure out why something does not work in IE.

  17. 45

    Shashikant Arya

    July 9, 2012 8:02 pm

    World’s first IE7 “tax”

    Online retailer Kogan has instituted the world’s first Internet Explorer 7 tax. When customers make a purchase from the e-commerce store using IE7, they’ll be charged an additional 6.8% “tax” on their purchase to offset the additional cost of supporting IE7. To avoid the surcharge, shoppers need only switch to Chrome, Firefox, Opera, or Safari to make their purchase. Imagine how much tax would be for IE 6?

    • 46

      I would fire the developers, and hire a couple that knew how to code. I seriously don’t understand the big deal supporting IE7 & 8. If you have trouble coding for older browsers and modern browsers, you don’t know what you are doing. If I dropped support for IE6 and 7, I would loose millions a month.

      • 47

        Jaffer Haider

        July 10, 2012 12:21 pm

        I completely agree. Unless you’re doing something really cutting edge, it’s not a big deal to support IE7 and 8; every web developer should be well versed with techniques for supporting them. Also, Microsoft makes it really easy to test on older versions of IE with tools like SuperPreview … man I wish we had tools like these back in the early 2000s.

    • 48

      I believe this was a joke/marketing stunt :> Buyers didn’t actually have to pay it in the end.

  18. 49

    We should create a world movement, to get rid of ie7-8, so I can use that 20% of the time I spend fixing issues for ie to do something else. This will also increase productivity on companies like the one I work for, who are launching products every week, it is really a PITA.

  19. 50

    I wrote about IE and modern browsers on my own blog not too long ago. A central point I think is sometimes missed is the incentive for the browser makers. Microsoft doesn’t make money off of Internet Explorer, it makes money off of the OS. They simply don’t have a strong drive to make an awesome browser.

    The problem, as you’ve said, really is the OS. IE7 is dying off pretty fast, but we’ll be stuck with IE8 for a while.

    The real issue isn’t with the end-users; it’s with the clients. We need to create incentives for our clients to stop requiring websites to look and even perform the same in all browsers. If we would track our dev hours on a per-browser basis so our clients could quantify what IE[x] actually costs, they’ll make decisions that benefit their bottom line (and our web).

    • 51

      Dan Henderson

      July 10, 2012 1:26 am

      I like it. Add an IE tax to any quote and see them quickly turnaround and say supporting IE so strictly may not be a priority if it saves them money.

  20. 52

    Old browsers aren’t real problem, new browsers and new web developer expectations are. Some tutorials are pushing the limits of World Wide Web far beyond the standard user demand. Users don’t really need RGBA colors, opacity without filters, animations made through CSS instead of JavaScript… these are pure technical problems and it’s the job of web developer to calmly deal with them. Annoying or attacking the users of old or unpopular browsers is not a solution. It’s spam. Nothing more.

    As I see last thirteen years: Browsers are getting better and better and web developers are whinning more and more… it’s insane. When dealing with the old and the new, the old is the base, and the new is investment, never vice versa. Remember Postel’s law? “Be conservative in what you do, be liberal in what you accept from others.”

    Even I sometimes use Internet Explorer 7. That browser does match my humble needs. It’s my personal choice. When I see broken website in it, I blame lazy author, not my browser. All I want is to read some article or buy some stuff, maybe post a comment — do I really need one of those five new browsers to do that? Am I holding back the web? Are my demands too old or too marginal? I don’t think so.


↑ Back to top