Can i stop supporting ie6

Fortunately, its numbers are finally dwindling. It claims similarly low portions of browser share in virtually every other country except China. Is it time to make IE7 the new IE6? From a technical perspective, the Kendo UI engineering team must jump through all variety of twisted hack to make sure IE6 works.

Of course, we would all like a toolset that works in every browser ever created- and Kendo UI can be that- but it comes at a cost. Is the cost of IE6 worth it to support to a dwindling ancient browser population? From our perspective, IE6, where it exists, is primarily supporting legacy applications in closed enterprise environments.

At some point, support for IE6 has to end. UI frameworks for the web have been reluctant to take the plunge, but maybe now is the right time. Only now, during the pre-release beta, do we have the opportunity to avoid a long future of IE6 hacks in the Kendo UI code base. All of this has no impact on other supported versions of IE. It just means IE7 becomes our new IE6. This is it! The place we will collect official feedback that will have a major impact on our decision to support IE6 in Kendo UI.

Keep the support? Here are 10 ways you can avoid a crisis. Amazon wins major arbitration against Reliance-Future, but will they comply? Uber sued by US Justice Department for allegedly overcharging people with disability. SEA merchants credit digital platforms for keeping them afloat, but high costs top barrier.

US judge denies Apple's request to delay introduction of external in-app payment links. You agree to receive updates, promotions, and alerts from ZDNet. You may unsubscribe at any time. By signing up, you agree to receive the selected newsletter s which you may unsubscribe from at any time.

You also agree to the Terms of Use and acknowledge the data collection and usage practices outlined in our Privacy Policy.

My Profile Log Out. Join Discussion. Add Your Comment. Programming languages: Why this former favourite is sliding down the rankings Developer.

How to delete your Facebook account for good Social Enterprise. Here are 10 ways you can avoid a crisis CXO. Tech Industry. SEA merchants credit digital platforms for keeping them afloat, but high costs top barrier E-Commerce. US judge denies Apple's request to delay introduction of external in-app payment links Legal. Please review our terms of service to complete your newsletter subscription.

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 letting it degrade certain "unsupported" features gracefully. Just remember, dropping IE6 support will affect someone out there 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 problems, you may give your users a warning about when you will shut down IE6 access. You might also use something like ie6-upgrade-warning to give them some alternatives. Be mindful though, that some corporate users won't have enough permission to download and install a new browser, so being a jerk about "get out there and upgrade you lazy bum!

If you're working on a contract or freelance basis, this is entirely up to you. This contract addendum acts as a notification to clients regarding your limited support of Internet Explorer.

This document is currently at version 1. I have not seen it updated since I found it, but that's really not important since it was the concept and the basic language that I used before tweaking it. Essentially in the form presented on the site it says that you will create a version of the site for IE6 that presents the info that needs presenting, though not necessarily using the approved design.

Also that you reserve the right to feed them motivation to upgrade their browser. Depending on the client and the project, you can just have it say that IE6 will not be supported, that you will deliver support for IE6 as a second-phase deliverable, at extra cost, or offer complete support.

If you choose to support IE6 you can mitigate some of the issues with lack of feature support using the following resources:. And a few resources identifying IE rendering issues you're most likely to encounter, along with their most common fixes:. 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.

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 and expect the web to be broken for them? So the first half of battle is in our favor. For the remainder, we can take a graded-support approach.

It helps to make a grid of "function or aesthetic" x "IE6 effort" and present that to stakeholders. You can often come up with a viable B-level or C-level grade of support for IE6 users that makes sense for your audience and your stakeholders can live with.

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. 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?

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. 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. IE8 has only just overtaken it in Asia. 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 jQuery authors have to worry about making it work.

Everyone else gets to benefit from their work. CSS frameworks are not universally popular, but if you need something to "just work" and you aren't too fussed about including some rather obscure class names in your HTML, they speed up cross-browser development and remove all the guesswork. If you don't want to use a framework, good CSS Reset scripts are available from many places. As much as I believe that people should be discouraged from using IE6 as far as possible, I like just being able to not worry about it.

Instead, I can move on to the next problem or project. For reference, I launched a website around targeting people interested in the world cup 2 months ago. 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. Then inform them of how poor the security of IE 6 is and how much of a cost it is to have designers and developers bend over backwards to get it tow ork on IE6.