GregWolejkoDebugging IE6
Every web developer needs to tackle the IE6 and its various CSS bugs once in a while. Generally it is a dreaded task as IE debugging is one of those really nasty jobs that just sometimes have to be done.
Yet I don’t despise IE6 that much. I don’t like it but the whole process of debugging IE6 CSS issues comes quite natural. Why is that?
It seems that if you work out your on process for it later on your job gets easier. There are however some ground rules that I try to stick to. So far so good, and my system haven’t failed me. All kinds of IE6 bugs come my way and I have been able to squash them quite proficiently.
So how do I do it? What is my magic workflow? Nothing fancy but maybe you’ll find it interesting or even better - helpful:
- IE Web Developer Toolbar - as close as you’ll get t o Firebug on IE
- Browser specific stylesheets - this is essential. No browser specific fixes without that.
- Learn about common IE6 bugs like double margin bug - info on float theory and lots of described IE bugs is covered by Smashing Magazine’s Float Theory article and also in this IE Primer
- Get to know the “hasLayout” issue - mind blowing experience. Every one needs to get to know it.
- Learn my and Bartek’s golden rule of IE6 debugging: “when in doubt use display:inline-block”
This is it. Nothing more to it. Sticking to those few simple rules I managed to greatly reduce my time spent on debugging and I am able to put more time into actual styling. Sounds good for me.
And as always, what about you? Do you have something to add? How do you tackle IE6? Care to share?
Related posts
About this entry
You’re currently reading “ Debugging IE6 ” an entry on GregWolejko.com
- Published:
- 7.16.08 / 8pm
- Category:
- CSS
8 Comments
Jump to comment form | comments rss [?] | trackback uri[?]