Comments on: Debugging IE6

By: bradt.ca » Preventing IE6 bugs

bradt.ca » Preventing IE6 bugs — Fri, 26 Dec 2008 16:22:25 +0000

[...] This article also has some helpful links about debugging in IE6. [...]

By: Ozan Onay

Ozan Onay — Tue, 19 Aug 2008 13:59:05 +0000

Thanks for the links but looking at this page for the first time in IE6, your divs are all over the place.

I don’t blame you as I don’t support IE6 on my own blog.

I imagine that most of your readers use firefox or at least a recent version of IE, but I thought it was still worth pointing out that your blog breaks on IE6.

By: Jorzi

Jorzi — Thu, 24 Jul 2008 15:08:12 +0000

Why would you do this now? force your users to update or run firefox.

By: Angelo Simeoni

Angelo Simeoni — Fri, 18 Jul 2008 04:10:58 +0000

There are no ‘bad’ browsers. We should, as web designers, rise to the occasion to create sites that break down gracefully in all browsers.

If the needed markup formatting and browser hiccups were more well known, inline-block would destroy the use of floating for most layouts.

http://giantrobots.thoughtbot.com/2008/7/2/how-i-learned-to-stop-worrying-and-love-the-inline-block

By: Vysnu » links for 2008-07-18

Vysnu » links for 2008-07-18 — Fri, 18 Jul 2008 00:29:42 +0000

[...] Debugging IE6 | GregWolejko.com (tags: ie6 debug web development) [...]

By: Fox

Fox — Thu, 17 Jul 2008 14:19:02 +0000

IE 6.0 is a bad browser .

By: Debugging IE6 | WhiteSandsDigital.com

Debugging IE6 | WhiteSandsDigital.com — Thu, 17 Jul 2008 14:11:06 +0000

[...] bunch of helpful tips for all web developers to better handle the dreaded IE6 debugging.read more | digg [...]

By: Rob

Rob — Thu, 17 Jul 2008 13:22:08 +0000

Unfortunately, IE7 is still 10 years behind all other browsers in web standards support and the new IE8 in beta, so far, is only a little better.

By: Samori Gorse

Samori Gorse — Thu, 17 Jul 2008 11:38:53 +0000

When I hear bug and IE6 in the same sentence I think about the poor javascript debugging support it provides.
(Not to mention the unbearable debug messages and wrong line numbers.)

The best solutions known at the moment are Microsoft Script Debugger and Microsoft Script Editor (which comes with Microsoft Office).

They both provides basic but essential features such as callback, breakpoints, step by step execution, etc…