Browsers I rather not support

There has been a little bit of noise about the blog­sphere recently about want­ing to drop browser sup­port for a cer­tain browser this year. So here are the browsers I would like to stop sup­port­ing, why and why I will con­tinue to sup­port them.

Internet Explorer 7

This would of been a great browser if it was released in 2003, instead it was released in 2006. The improve­ments over IE6 were good but not worth wait­ing 5 years for. It still has a num­ber of the IE6 idio­syn­crasies that require work arounds. It is the most pop­u­lar browser is com­mon use today, and likely to remain so for another year, before suc­cumb­ing to IE8. Still you and I will sup­port­ing it for a few years to come.

Google Chrome

A fast, light­weight browser, which I was happy to use while in beta. Since it reached 1.0 release, I have become aware of a few short com­ings. It branched from the web­kit evol­u­tion far too early and has not included recent improve­ments that other web­kit browsers have. For example the prob­lem with border-radius and box-shadow, lack of sup­port for @font-face. In addi­tion the Chrome renders type dif­fer­ently from all other browsers. Still while it has a decent mar­ket share for a new browser and the oppor­tun­ity to improve exists, so it needs to be supported.

Internet Explorer 6

A great browser in 2001, which should of been replaced in 2003 and dis­ap­peared from view by 2006. It has a num­ber of idio­syn­crasies that require work arounds, and you have to spend con­sid­er­able time after get­ting a design to work in IE6 after you had it work­ing in more mod­ern browsers. How­ever, over two years after being replaced it still com­mands around 20% of the IE mar­ket share. This has very little to do with com­puters not being able to sup­port IE7. Less that 5% of all IE6 users are on an OS other than XP.

Unfor­tu­nately IE6’s reign of 5 years cemen­ted it’s pos­i­tion in the cor­por­ate mar­ket and their intranet sys­tems. A large num­ber of cor­por­ate net­works could not upgrade to IE7, because major tools like the fin­ance and human resources sys­tem (in our office) would not work with IE7. These are not quick and dirty loc­ally built tools, but major applic­a­tions built by vendors like Oracle, IBM and the ilk. How­ever, more than 2 years after it’s release, IE7 is now get­ting sup­port from these applic­a­tions and as cor­por­ates upgrade these sys­tem, most are also upgrad­ing their cor­por­ate browser to IE7. Unfor­tu­nately this will take a couple more years, before IE7 or IE8 rule the cor­por­ate sector.

A more dis­turb­ing trend is the net­books and inex­pens­ive laptops that con­nect to the free wifi at work, over 50% of the machines run­ning XP use IE6, com­pared to less than 25% of the XP machines access­ing the reg­u­lar web­site. I do not know if this is because IE6 is the pre­ferred browser for low spec machine run­ning XP or some­thing to do with the large num­ber of Chinese and Korean lan­guage devices.

Still while IE6 is our cor­por­ate browser, I will have to sup­port it, no ques­tions asked. As I will while it remains pop­u­lar in either in the cor­por­ate or low end netbook/laptop sectors.

Internet Explorer for Windows Mobile 6

If you thought sup­port­ing IE6 or the old IE5 was pain­ful, you have never had to sup­port IE for WM5 or WM6. It does not know if is a mobile browser or a full blown browser for the small screen, it loads both screen and mobile pro­file stylesheets, it only sup­ports XHTML-MP which is miss­ing a few key ele­ments from HTML4. JavaS­cript sup­port is inter­est­ing, some scripts work, other do not and some just crash the browser. Unfor­tu­nately it is one of the major mobile browsers and Win­dows Mobile is pop­u­lar in the cor­por­ate sec­tors. Around 10 times more pop­u­lar than the iPhone and Mobile Safari and a lot more than Opera Mobile, my favour­ite small screen browsers.

Browsers I will stop supporting this year

I have already made a decision not to worry about get­ting the new web­site I just launched for work, per­fect in Fire­fox 2 and Safari 2. they accounts for less than 1% of all traffic. So as long as it func­tions cor­rectly that is all I am con­cerned about. Minor defects are accept­able. On the other hand, Fire­fox 2 sup­port will be a con­cern if I every get round to redesign­ing this blog because it accounts for 5% of all traffic. Appar­ently web geeks are twice as likely to stick with Fire­fox 2 than the aver­age Fire­fox user, prob­ably some­thing to do with the trusty web developer tool­bar. Still I will review that later in the year.

I am a little more ruth­less than the Yahoo browser sup­port chart, I have already dropped Win­dows 2000 sup­port. I cur­rently only worry about XP, Vista, OSX 10.4 and 10.5 and Ubuntu as OSes and IE6, IE7, Safari 3, Chrome, Opera 9.5, Fire­fox 2 & 3 as browsers for com­puters. Though I am look­ing at drop­ping Chrome and Fire­fox 2 to func­tional only, while adding IE8 and Opera 10 to sup­por­ted. I also sup­port Mobile Safari, Opera Mobile, Inter­net Explorer for Win­dows Mobile 6 and would sup­port the latest S60 browser if I had access to a test device.

edited 17 Feb­ru­ary 2009 for gram­mat­ical reasons

9 Responses to “Browsers I rather not support”

  1. Nick Hodge Says:

    Nick

    I notice when look­ing at stats on my per­sonal blog that:

    - Fire­fox 2.x has largely been replaced by Fire­fox 3.0.x
    – Fire­fox users are good at accept­ing the updates and stay­ing at the latest version

    - IE6 con­tin­ues to drop (thank goodness)

    - The sooner IE6 is replaced by IE7; or bet­ter yet, IE8, the world will be a bet­ter place™

    - Yes, I’ve taken the pub­lic (ie: at Web­Jam) digs about Win­dows Mobile’s sucky browser rel­at­ive to the com­pet­i­tion. The only way is up!

    Thanks for a bal­anced and prag­matic review.

    Nick

  2. John Faulds Says:

    Appar­ently web geeks are twice as likely to stick with Fire­fox 2 than the aver­age Fire­fox user, prob­ably some­thing to do with the trusty web developer toolbar.

    The web­dev tool­bar works in Fire­fox 3 (at least on Windows).

  3. Nick Says:

    John, I was just try­ing to under­stand why more than 10% of Fire­fox vis­it­ors to this site still used Fire­fox 2, com­pared to less than 5% to my work site dur­ing Novem­ber and December.

    I dis­abled com­pat­ib­il­ity check­ing for my exten­sions when I star­ted using Fire­fox 3 beta a while back and never turned it back on. I remembered Fire­bug and Web Developer Tool­bar kept com­ing up on com­pat­ib­il­ity checks as I swapped between Fire­fox 2, 3 and 3.1beta. So I assumed it was these developer tools that kept some of the Fire­fox vis­it­ors to this site to ver­sion 2.

    Just checked fig­ures for the past few weeks and that dif­fer­ence has almost dis­ap­peared, it is close to 8% for both sites.

    ps the web dev tool­bar now works for Fire­fox 3 and 3.1 beta on the Mac.

  4. Still include IE6 support when creating a Web Application? | Moritz Haarmann's Blog Says:

    […] On the other hand, I guess that most people using really mod­ern WebApps are nev­er­the­less forced to use mod­ern browsers. I don’t know, really not. A short yet true list of cons is presen­ted here as well, and a rather rad­ical point of view presen­ted by nick cowie. […]

  5. moritz Says:

    hey, just found your post and .. I agree with you, almost. I’m afraid that drop­ping Safari sup­port is a) unne­ces­sary, because from my exper­i­ences, it’s not hard to optim­ise.. it works mostly and b) doesn’t take into con­sid­er­a­tion that macs mar­ket share is grow­ing.. and grow­ing. And keep in mind, iphone also uses safari, and it’s avail­able for windows.

    Besides, great post.

  6. Nick Hodge Says:

    For those work­ing on IE; note that IE8b2 has Developer Menu.

    Inter­ested in feed­back; with the IE7 “render switch” — hope­fully this helps you guys out.

    If not, please tell me

    Nick

  7. Nick Says:

    Mor­itz, I am not drop­ping Safari sup­port. I am choos­ing not to sup­port older ver­sions of Safari, before Safari 3 that was released in mid 2007. Safari users like Fire­fox users tend to update to the latest ver­sion fairly quickly. Of the 700+ vis­it­ors to the site in the past couple of months using Safari, only 5 used Safari 2 and 1 used ver­sion 1.32 (the latest ver­sion for 10.3). The work site stats are slightly higher, but not by much.

    The webki/khtml engine used by Safari is also used by the Nokia S60 browsers. The most pop­u­lar mobile browser on the planet and one I do not have a test device for. So I do pay atten­tion in get­ting it right for Safari.

    Nick H, thanks for that, had not really explored IE8b2, other than finally installing a Vista VM on my MBP with IE8b2 for testing.

  8. moritz Says:

    I should some­times read twice to get the ver­sion num­bers right.. my fault :-)

  9. Ben Buchanan Says:

    The browsers on my hit list this year: Fire­fox 2 and IE6.

    FF2 will just get dropped since its share has plummeted (and if you can install FF2 you should be able to upgrade). Get­ting rid of FF2 clears the way for proper use of display:inline-block which is awesome.

    IE6 has too big and per­sist­ent a share to drop it out­right; but I’m mov­ing it to second tier sup­port. Things will be made func­tional, but I’m no longer going to spend large amounts of time mak­ing things per­fect in IE6. A bug that can be eas­ily fixed with a minor visual dif­fer­ence will be fixed that easy/quick way. If an advanced fea­ture breaks IE6, IE6 will get a cleanly degraded ver­sion. Stuff like that.

Affiliates

Google
text advertising by
Powered by Reseller Zoom