I have to admit it can be useful though. When FF is displaying my page correctly and IE isn’t then I know my code is right and it’s an IE issue. That can be useful for finding errors. Can’t believe I’m saying that though, what does that say about IE…
JJ, I hear you. I’m ready to put a stake through its virtual heart. But so many corporations have outdated computers with nothing but IE6 on them, it won’t die off very soon. Yesterday, I did a presentation on teaching Web design to kids; the computers in the “lab” all had nothing but IE on them, and a crippled version to boot (school system restrictions, you couldn’t even right-click on anything). My presentation info was all Web-based, and I fought with the browser (and the “smartboard,” which ain’t that smart) the entire period. It was very, very frustrating.
Let’s expand the battle cry from “death to IE6” to “death to IE” period. I don’t care what huzzahs are being sounded for IE8 and the future IE9. I hates it forever, yesss precious.
Won’t have to put up with IE6 for much longer I hope, we’re down to 7% of users and falling. When it gets to around 2% I’m going to stop worrying about it.
yeah sure except it wasn’t really a solution, it was a mistake.
I had a ‘cleaner’ div set to ‘clear both’ to make sure the content div under the nav div cleared the nav div because it was originally floated. IE 6 was giving the cleaner div a 15px height for reasons only known to IE6 since the CSS set it at zero height/padding/margin etc but in the end it didn’t need to be there at all so I whipped it out and hey presto, gap gone.