The IE Temptation: Phasing Out Internet Explorer 6 Support
By Chris Cardinal on July 10th, 2008
Internet Explorer 7 represented a step forward for “mainstream” browsing. Microsoft worked to fix a lot of the epic fails in CSS implementation that IE 6 had brought upon itself and those around it. There are a few departures from the standards and further from how Firefox handles things, but they’re farther and fewer in between and don’t impact us *too* much on a day-to-day.
Still, instead of developing for Firefox and Internet Explorer, we’re developing for FF, IE6 *and* IE7. Cheers. Add to the fact that IE6 has some serious flaws including its lack of transparent PNG support without getting all hacky, different JavaScript implementations and limitations on what you can do with AJAX calls, et cetera, and it becomes a significant burden to develop for. It doesn’t help that you can only have one version of IE installed on a Windows-machine, or the other, without, again, getting terribly hacky. Just watch your workflow take a hit there.
Tagged with: 37signals, firefox, ie6, ie7, internet explorer, microsoft, mozilla, web standards, wordpress
Posted in: Design, Development