Slashdot Mirror


Is Internet Explorer 6/7 Support Required Now?

k33l0r writes "Following Google's announcement ending support for Internet Explorer 6, I find myself wondering whether we (Web developers) really need to continue providing support for IE6 and IE7. Especially when creating Web sites intended for technical audiences, wouldn't it be best to end support for obsoleted browsers? Would this not provide additional incentives to upgrade? Recently I and my colleagues had to decide whether it was worth our time to try to support anything before IE8, and in the end we decided to redirect any IE6/7 user-agent to a separate page explaining that the site is not accessible with IE 6 or 7. This was easy once we saw from our analytics that fewer than 5% of visitors to the site were using IE at all. Have you had to make a choice like this? If so, what was your decision and what was the reasoning behind it?"

34 of 512 comments (clear)

  1. Why redirect them? by arndawg · · Score: 5, Insightful

    You could just let IE6 "try its best". And use a big red notice bar at the top with a link explaining it.

    1. Re:Why redirect them? by brentonboy · · Score: 5, Insightful

      Agreed. This is why browser sniffing is bad. Just design it to be standards compliant, and let the browsers that can't follow the standards fail, hopefully gracefully. Blocking IE6 users completely is just pointless.

    2. Re:Why redirect them? by OverZealous.com · · Score: 3, Informative

      For basic websites, I highly recommend Universal IE6 CSS.

      I've decided that I will never design a website that supports IE6, but instead will only server up this rudimentary (if nice-looking) style sheet. As long as your website is standards-based, compliant, and content-oriented, this CSS file works great. You do, however, have to include some of those annoying <!-- [if lt IE 7]>...<![endif]--> tags.

      For web apps, which are more complex, then I use a browser sniff and redirect IE6 users away. I don't care how "bad" or "evil" it is. It's better, to me, for users to know why a page doesn't work, than see a partially loaded page or pile of garbage.

    3. Re:Why redirect them? by Nitewing98 · · Score: 3, Informative

      I agree. If you apply standards that all browsers should support, you'll also be friendly to other browsers like Firefox, Safari, Konqueror, Opera, etc. There's no reason to have to build separate pages and do redirects (or detect browser in PHP and cough up different page code). The whole point of HTML is that it should render in any browser (which includes Lynx, too). As a Mac user, I'm glad to see the web lose its Microsoft-centric view of the world. Firefox (which owes it's history to Netscape) finally put a dent in Microsoft's armor so others could succeed too.

      --

      Nitewing '98

      Everything works...in theory.

    4. Re:Why redirect them? by flimflammer · · Score: 3, Insightful

      It's fairly easy to put a top aligned red warning message that says "Please not: This site is not designed with support for Internet Explorer versions 6 and 7, and may contain errors when viewed."

      Blocking people from viewing your page because they're using a browser you don't agree with really rubs people the wrong way. It shouldn't be your job to force someone to upgrade. More often than not, they will just not bother viewing your page and look elsewhere.

    5. Re:Why redirect them? by purpledinoz · · Score: 4, Funny

      Who still uses IE6? Google should just insult the IE6 users into upgrading: "You are using Internet Explorer 6. This indicates that you are a giant douche. If you no longer want to be a giant douche, please upgrade your browser."

    6. Re:Why redirect them? by Jedi+Alec · · Score: 5, Insightful

      It's even worse than pointless. I'm typing this on IE8, but it identifies itself as 6 to appease some of the dreadful apps used on the intranet. So even though the browser should be perfectly capable of rendering the site, filtering based on browser version will lose yet another set of potential eyeballs.

      --

      People replying to my sig annoy me. That's why I change it all the time.
    7. Re:Why redirect them? by pstorry · · Score: 3, Insightful

      Who says that the problem is the organisations running IE6?

      Most of them would move off it to IE7 if they could. Really they would. It's not much more (or less) difficult than any other large application - test it, package it, drop it to machines. That's an established and controlled cycle.

      The problem is not that they don't want to. The problem is that the enterprise software segment has been very shortsighted.

      SAP, PeopleSoft, Seibel. ERP, Human Resources, CRM systems.

      Things that organisations put in which are strategic, in a way which deserves block capitals that I'm not quite willing to put it in. But trust me, these things are signed off at board level and cost a truckload of money, so there's a management investment in getting them working at all costs - otherwise they'd have to admit that they were wrong!

      And once in, they become very hard to remove. Stuff like PeopleSoft is often tied to processes like leave booking, expense claims and payroll, for example.

      Upgrading these systems is not a trivial task. It's one that, even if it's a simple and smooth process, has huge risks. Risks that run towards lost days of business, inability to produce corporate accounts, or handle staffing changes and expense claims. So these systems are upgraded at a glacial pace, with the process being rigorously controlled and methodically run.

      Guess which systems a company buys that would require IE6?

      I'm sure that they all have versions out now that support IE7 and higher. But the companies running these systems are often one or two versions behind, and have real incentives to avoid change. Incentives that don't even factor in the client web browser's name and version.

      And don't forget that these systems are not cheap. The upgrade software bill will be huge, before you even start any work. Another reason to delay, especially once management remembers how expensive and painful it was tweaking and customising these systems to match their organisation's workflows and requirements. Do that again? At huge cost? Barely two years after we last suffered through that? NO WAY!

      And so this is how it starts. You can then add the fact that developers then have a standard platform of just one browser, and you soon find any in-house development is tested on just one browser. Which compounds the problem.

      It started with enterprise software. It's continued by in-house developers. It has nothing to do with the merits of the client in any way.

      And good luck not dealing with such organisations. This, sadly, is the state of pretty much all large organisations...

      I'm not defending them, by the way. I'm just trying to help you understand why large organisations are stuck in this rut.

    8. Re:Why redirect them? by GameboyRMH · · Score: 4, Interesting

      I (primarily) developed and currently support an international business site that gets 18% IE6 visitors. Cutting off IE6 visitors would make a tangible difference in the millions of dollars - the competiton is stiff and finding a nonfunctional website would cause the customer to go directly to someone else. IE6 support was basically an afterthought - I didn't go out of my way to support it but I made sure the site's still usable, even if it doesn't look quite right. I did have to make some changes to the code vs. not testing with IE6 at all, but I didn't have to do any dirty hacks, change the site's appearance or sacrifice any features in the process.

      So let's say it took me 10% longer to make sure the site's still accessible with IE6, which cost the company somewhere between "peanuts" and "precisely dick" and didn't affect any other users. Would cutting off almost 1 in 5 users be a good business decision?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  2. Depends on who you cater to by ResQuad · · Score: 5, Insightful

    Depends on your clients. If you're talking about a mostly technical crowd? No, probably don't need IE6. If you're talking about a site for corporate users, yea, you need IE6. There are many major companies out there still running IE6 on XP. It sucks, they should all switch to Firefox (Or Chrome, or Opera, or anything but IE), but unfortunately most don't have a choice in the matter. Oh and if you're trying to sell people something, then most likely yet again.

    Of course it all depends on what your usage stats/analytic say. Personally, I've not supported IE6 for a long time, but then on most of my sites Firefox is more than 50% of the market.

  3. Not needed by BhaKi · · Score: 5, Insightful

    Actually, no browser should be explicitly/directly supported. Only standards need to be supported. The browsers and their makers should be forced to comply.

    --
    The largest prime factor of my UID is 263267.
    1. Re:Not needed by mwvdlee · · Score: 5, Insightful

      And you'll tell your visitors to browse your site with the W3C Validator?

      I'm sorry to inform you that most people that might browse your site exist in a realm called "reality", you should visit it some time.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    2. Re:Not needed by headLITE · · Score: 4, Funny

      Actually, that might work.

    3. Re:Not needed by Eivind · · Score: 4, Insightful

      Agreed. But it's still a good thing to code to the standard, because it's also real that a site is easier to maintain the less browser-spesific hacks it employs.

      It also matters what kinda functionality is lost in older browsers. If the site don't work at all with IE6, and 10% of the visitors use that, then that's definitely bad. If (to take a random example) border-radius isn't supported by IE-6, so those 10% visiting with that browser, get square corners rather than rounded ones, that may well be acceptable. (especially since supporting round corners in ie-6 means using fugly badly-maintainable hacks)

    4. Re:Not needed by weicco · · Score: 3, Insightful

      Yes, that and my personal opinion is that web sites should have less (X)HTML/CSS/Javascript masturbation. I don't care about the fancy outlook. Content is everything.

      --
      You don't know what you don't know.
  4. IE6 outdated. by Tukz · · Score: 4, Informative

    We're a web company, making different kind of websites for different kind of people. Which means we make anything from small "Mr and Mrs Smith My Pink Pony" kind of sites, to web shops with 5k+ transactions per day.

    We recently (within the last year or so) put a note on our contracts, stating we don't support IE6 anymore, unless the customer is actually paying extra for making the appropiate changes. It was just too much a hassle to manage all the hacks and workarounds all the time.

    So basically, we state we only support the latest generation of browsers, included IE7 since the migration to IE8 isn't complete yet. A lot of people still on IE7.
    And IE7 isn't TOO bad, the work arounds is mainly CSS, the rest is worked out by MooTools, Prototype, etc.

    --
    - Don't do what I do, it's probably not healthy nor safe. -
  5. Corporations. by jedrek · · Score: 3, Interesting

    That's what it comes down to: corporations. There are still too many 10,000+ employee corporations out there that run Windows XP with the Flash 7 plug-in and IE6. You have to support that or there is no client.

  6. I'm posting this from IE6. HELP! by mykos · · Score: 4, Interesting

    My employer hasn't switched from IE6. Does anyone have tips on how to convince them to move to IE8? We have exactly zero software which requires IE6; in fact, some of our software doesn't work properly with it.

  7. Re:Easy Answer by Fri13 · · Score: 3, Insightful

    How well does page support standards and is it designed that blind people can run it trough voice syntetisator or Lynx to read it with the "blind keyboard".

    I would not like that any page is designed for specific browser at all. Was it FF, Opera, Safari, IE etc.

  8. Measure it... by dacut · · Score: 3, Interesting

    ... as you've done. What percentage of those IE users are still running IE6/7? Then ask yourself, "Am I willing to lose X% of my visitors to save Y% of coding effort?"

    For any typical website which depends on traffic for revenue, I'd say you'd have to be nuts to cut support for IE 6/7; thats about 35% of the visitors to your site. The fact that only 5% (and not 62%) of your visitors use IE at all, however, indicates that you're not running a typical site (or there's an error in your metrics collection).

  9. Standards Compliant by jadin · · Score: 4, Interesting

    I (attempt) to keep my websites standards compliant. If it works in your browser, great. If not, not my problem. I'm not jumping through hoops to help support companies actively ignoring agreed upon standards.

    However, I'm also not financially dependent on my websites...

  10. Re:sometimes users don't control their machines by soundguy · · Score: 3, Insightful

    If "security was tight", IE would not be allowed at all.

    --
    Nothing worthwhile ever happens before noon
  11. Re:No more support by Rizz · · Score: 3, Insightful

    I should have clarified. My sites are all now built for HTML5 and every attempt is made to stay standards-compliant.

    While users with older browsers are redirected, the entire site (short of the few pages with directions) use those standards and are still visible selects the ``I know my browser was made in the 1800s but I still want to see your site'' link.

    It's code and pages that I wrote one and just copy into new sites. *That's* what I wish more people would do. We could all gently urge those who either don't know or don't care and perhaps make the web a better place, one user at a time.

  12. Wish we could :-/ by SplatMan_DK · · Score: 5, Insightful

    Get rid if IE6? Boy I wish we could. But we can't.

    Our 4-man startup software company targets medium sized corporate customers (250-2500 seats) and they are still using lots of old computers with IE6. There are many reasons but a few of the most noticable ones are:

    1.) a ton of old Line-of-Business applications still uses IE6 for presentation.
    2.) a surprisingly large amount of corporate software uses embedded IE6 components in their GUI.

    Most of these corporations have installed newer browsers on their machines (some of them even installed non-MS browsers) but IE6 is still there - under the surface - because critical business applications are still depending on it.

    All those Line-of-Business applications are extremely hard to remove. They often solve critical business needs so nobody wants to throw them away. They work and "do the things they were built to do". And since they just work there is no budget to replace them with somerhing else. The people who created them have left the company years ago so nobody really knows exactly how and why they are implemented.

    But everbody knows this about their old LOB apps: they neeed IE6, they still work as intended, nobody can tell how to make an alternate solution, and there is no budget to analyze or re-implement them (and why would anybody want to - right?).

    I imagine this is quite common for many corporations around the world and not just in my region.

    - Jesper
       

    --
    My security clearance is so high I have to kill myself if I remember I have it...
    1. Re:Wish we could :-/ by david.given · · Score: 3, Interesting

      I've been on the other end of this: I got sent out to work with a Korean customer on-site. They wouldn't allow our machine to be connected to their LAN without installing some security software (name and shame: Waterwall).

      The installation goes halfway through and fails obscurely. Three hours of debugging later they finally realise that I have IE8, but Waterwall only works on IE6 or IE7.

      So I try to install IE7. I can't, because IE8 is installed. I try to uninstall IE8. I can't, because our sysadmin is, like, competent, and had set up the laptop with a DVD image with IE8 slipstreamed into it.

      I eventually had to borrow an XP disk from the customer and reinstall Windows. Then I installed Microsoft Security Essentials and removed the virus that was on their XP disk.

      The real joke? Waterwall blocks web access, enforces encryption on USB keys and recordable media, etc. (It's intended to stop 'information leakage'.) The internet? Wide open. ssh worked fine...

  13. Re:Yes and No by mwvdlee · · Score: 5, Insightful

    My stats indicate more visitor use IE6 than Opera (all versions combined) or Safari (all versions combined).

    If IE6 is dead, then so are both Opera and Safari.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  14. Hell no! by Hurricane78 · · Score: 5, Interesting

    Remember: The only thing you can achieve by supporting those “browsers”, is to be an enabler. Basically the only reason those people still use IE, is because they can. And the only reason they still can, is because you still code for IE 6/7. And the only reason you do that, is because people still use them.
    Do you see the circular logic here?
    Someone has to break the cycle. And you can bet your ass that it won’t be the users. It’s your job. It’s mine. After all we’re the experts for a reason.
    Don’t be an ass. Be nice. Don’t push them. Pull them. Coming from IE6 to a full-featured modern browser with HTML5-enabled sites, is freakn’ great! It’s like opening the box of your shiny new electronics device (or whatever you like) and playing with it all day long. Get that feeling across! And you will see them getting dragged in in the euphoria, switching in the blink of an eye.
    People don’t change anything if they think they don’t have to. It’s called efficiency. But sometimes it’s bad. E.g. when there is a lack of information.

    So if you think that they should switch, then just code close to the standards. If they want to use their site, it takes them five minutes to install a recent browser, and they know it for years.

    Still supporting IE 6/7 is similar to acting like those EA managers, who would never dare to do something innovative, edgy, fresh or even slightly offending, to get a target group as big as possible... and then ending up with a shitty target group because the result of your work is bland, average, plastic-fantastic, non-innovative, boring shit that nobody hates but that also nobody loves.

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  15. Re:I'm posting this from IE6. HELP! by Hurricane78 · · Score: 3, Interesting

    I’ll be an example to you:

    I left my well-payed day-job because my boss (who was a very powerful player on the net) wouldn’t let go of IE6. (I had to write webapps for that piece of shit.)

    I’m happy and would I have the choice, I’d do the exact same thing again. Just earlier. ^^

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  16. It's our fault, just as much... by Bunzinator · · Score: 3, Interesting

    ... as it is that of the browser vendors. As web developers, we NEVER should have coded to anything but the W3C standards. Browsers would have been forced to fall in line, and this fascinating banter would never have been necessary. While I have always tried to just code to the standards, I can understand the position other are in, with their PHBs squeezing them to do stupid things.

    Though it'd never happen, I'd like to see W3C monitor all web content, and have the power to issue DNS deregistration notices to all non-compliant sites.

    Dear Sir,

    we have determined that you site, www.microsoft.com, is not compliant with the W3C 'xhtml1-transitional' standard it claims to implement. You are advised that you have 14 days in which to make the aforesaid site fully compliant. Failure to do so will result in the immediate suspension of your Domain Name registration, until such time your compliance is proven.

    Have a pleasant day.

  17. Re:Easy Answer by Bert64 · · Score: 3, Informative

    Standards compliant pages support lynx pretty well, lynx will simply ignore things it doesn't support and render the alt-tags instead of images etc. So long as you chose sensible names for the alt tags the textual page content is perfectly viewable. I use lynx quite often and find it great for getting to information quickly on well designed sites, without being distracted by any of the fancy graphics.
    IE6 doesn't degrade gracefully, it doesn't ignore unsupported features like lynx does, it tries to render them and botches the job totally.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  18. Re:sometimes users don't control their machines by QuestorTapes · · Score: 3, Insightful

    What's tight at these locations is compliance auditing more than security.

    In many environments, these compliance requirements have the force of law, and it can be a long up-hill battles to change a poor, "hack" compliance regulation, such as "Use Internet Explorer 6 with these settings and patches", to an effective one (use a browser that supports the following security...).

    Since the ostensible purpose of compliance is security, many people mix the two concepts.

  19. Re:I'm posting this from IE6. HELP! by oneandoneis2 · · Score: 3, Insightful

    When I worked at a job that not only used IE6, but used a heavily-locked-down IE6 that wouldn't even let me change the homepage.. I ran Portable Firefox from a USB drive and stopped caring.

    --
    So.. it has come to this
  20. Depends on Demographic by seangw · · Score: 3, Insightful

    As a web developer, I hate supporting IE6. It lacks so many things that make the web a better place today (poor CSS support, no PNGs -- yes there are fixes).

    I've found it depends on your target demographic. If you are looking at business people, IE6 is still in the ballgame. Offices are still lagging behind in their conversion to modern browsers. This is probably because the IT staff just doesn't care.

    In talking with user groups, I've heard people say (frequently) that they prefer Firefox or Chrome at home, but at work aren't allowed to install those browsers -- so they are forced to use IE6 during work hours.

  21. Re:Easy Answer by sjames · · Score: 3, Informative

    Lynx isn't obsolete, it's last stable release was July 5th 2009. It is still in active development.

    IE6 has a zillion quirks in it such that the easiest approach is often to have one website for IE6 and another for everything else.