Hot answers tagged


If ( your site does not make money ){ do what makes you happy } else if ( the cost of supporting IE6 > the money you make from IE6 users ) { stop supporting IE6 } else { keep making money from IE6 users }


It completely depends on your user base. In my line of work we support local councils so we have to maintain IE6 support as their computers are generally out of date and won't be upgraded for some time. If you are developing for a cutting edge audience however, then IE6 support will be less necessary. It is advised to make the website usable in IE6 by ...


Common reasons people avoid browser upgrades: They can't, either because doing so requires admin access (e.g. university networks), or because their hardware and operating system prevents it (or both). They don't know how. Firefox is famous for prompting people to upgrade. Chrome does it in the background. Safari does it through system updates. But earlier ...


The serious answer is to evaluate your users and customers for what they use, and the traffic and usage patterns for MSIE6 in that. You also need to decide how many is enough, can you make your site work "good enough" for IE6, or do things break down functionally for them. You can consider IE conditional comments for cosmetic things. For functionality ...


I agree that your decision obviously should reflect the business realities and audience of your particular website. That said, large companies officially dropping support for IE6 is still significant. It raises the general perception that it is finally OK to leave a 10 year old browser behind. It also adds ammunition to any case you wish to make to the ...


If you're working on a contract or freelance basis, this is entirely up to you. I use a version of the Internet Explorer 6 Contract Adendum by Jonathan Christopher of Monday By Noon. As described by the Author: This contract addendum acts as a notification to clients regarding your (limited) support of Internet Explorer. It is released under a Creative ...


There are actually a number of reasons. Most of them are related to corporations and I think looking at the difference in visitor browsers for corp websites vs personal sites (e.g.,, etc) Large and Medium size Corporations use software that requires a specific browser, usually IE6. Because of this, they create a software constraint ...


Thats a good question, asked hundreds of times... Andy Clark says it best Design for better browsers, then design alternative solutions to handle IE6 bugs Write a remedial IE6 stylesheet to address layout issues Use JavaScript to bootstrap CSS support in IE6 Make your ...


I think this has to be dictated by metrics. If a significant number / percentage of visitors is using older browsers, you should support your visitors. What is "significant" depends on the client. ;-)


For non-personal sites this should only be done if (for some reason) the site will not perform well in the out-of-date browser. Non-personal sites (be they business, governmental etc.) are not typically there to serve an agenda, so if the site works (mostly) in IE 6 (or any outdated) browser, let it be. Your users aren't there to be lectured on their choice ...


I ran into this issue before and the problem was related to the image color mode. If the color mode of the image is CMYK, then IE can not display it properly. The preferred color mode is RGB.


It is really time to get people to upgrade. If you really want to show people there are other options and that they need to move forward. As Google is even removing IE6 support from their products, it is time we all do the same.


I've not seen this answer, so what about piracy? I'd guess that a lot of people use IE6 or older versions of IE because they have pirated systems and they can't do software updates on them.


One answer I don't see very often is expectation management in conjunction with graded support. We have reached a point where, as a generalization, IE6 users are aware their browser is out of date but for various reasons are unable to upgrade. So the question shifts from one of education to a much better one for us - to what degree to these users understand ...


I am a product manager about to spend 40 MD supporting IE6 for a single customer. We sell software into call centers, an unfortunately IE6 is the default platform for many big organizations. My point is it depends, if I was building consumer web software I would have been off IE6 a long time ago, but as long as we have clients using IE6 we have to support ...


The longer we will support this ugly monster the longer it will live, take him off the respirator as he is too old and making our lives miserable


For a long time, I only tested on Chrome/Firefox/Safari/IE/Opera on Windows, but about 2 years ago, I ran into a problem where the client was complaining about a screwed up layout on their Mac. I looked at the site in Adobe Browser Lab using OS X Safari and indeed it was rendering improperly compared to Safari for Windows. Ever since then, I've stopped ...


I personally support it with this on any sites that will let me, seriously, it is still a business requirement with many of my clients. And who am I to argue with the people who pay the (bigger) bills?


It all depends on your target audience. Will the people you are building your site for expect IE6 to work? Will they be put off if it doesn't? I would suggest using customer focused decision making on questions like this rather than technical. Get to know your customers and plan accordingly. That said, statcounter notes that: IE6 Falls Below 5% for ...


Posting using IE6 whilst at work (on my lunch!) I work in central UK government, we are stuck on ie6 for the forseeable future, the reason being our payroll system causes ie7 and ie8 to crash. My only other advice is, if you choose to support ie6, remember to test in it as you are building.


Yes That's right, you can select and copy text right out of an SVG! The SVG does not store the text and letters as shapes, but by their "meaning". Given a good SVG viewer or SVG-capable browser, you can select and copy text as you would in a normal document. Note that this will not work with all SVGs: Since the exact font (the "looks") of a text is often ...


Depends entirely on your site and what it does. A site where you play games or have fun can demand a lot more from its users, just like a game on a computer can demand cutting edge hardware. A bank can't be as scrutinizing, as it's vital their customers can access the service. A site made for people with disabilities can't be as scrutinizing either, ...


When developing a website recently, I looked into stats for my country, Moldova, and decided to not support it. it is still possible to view site in IE6, but with low quality. You can propose IE6 users to install Google Chrome. So they will have an ability to view your site as users of modern browsers do.


For browser that are considered "current" (most recent release of a browser that is still actively supported), we try to ensure that our sites always work. We do not, however, test in browsers that have less than 10% of our traffic (in practice this means testing in latest versions of IE, Firefox and Chrome, we've recently also started testing in Safari on ...


As of Feb 24, 2011, I go with the following page widths: 960px, fixed centered - for non-mobile web visitors if the site isn't for affiliate marketing. I may use either a 10px or 20px margin inside that, but the "white" part of the page is 960px width. 750px, fixed centered - for sales pages (landing pages) for affiliate marketers. This is because we ...


A lot of people will say that it depends on your users and if your users are using IE 6 you need to support it. This is true, but you should stop supporting IE 6 anyway. Build a site that relies heavily on ajax, jquery, javascript, etc.. Load it up in IE 6 and then load it in Chrome. Watch their jaws drop as they see how fast chrome is. Then inform them ...


For reference, I launched a website around targeting people interested in the world cup 2 months ago. Of the 14,000+ visitors I got, exactly 262 of them used IE6. Its entirely possible that in your domain you will not need to support IE6.


Checkout - It can allow you to use modern features that aren't natively supported by IE


There are practical ways around the problem of supporting this decrepit old browser. The two major compatibility headaches are Javascript support and CSS support. Javascript support can be remedied through the use of libraries such as jQuery. This will allow code to work cross-platform (even if it runs a lot more slowly) and means that only one group (the ...

Only top voted, non community-wiki answers of a minimum length are eligible