But not in the way that the Cheat is off the hook.

I fixed the IE6 CSS problem I ranted about yesterday, and it was perhaps one of the more satisfying solutions I’ve encountered where IE is concerned, because all it required was that I remove a few lines of CSS code that turned out to be unnecessary anyway.

My approach to CSS is one of building a solid page structure and then fine-tuning the details until I have exactly what I want. A side effect of this is that sometimes I leave in unnecessary definitions along the way. If they don’t alter the output in the browsers I test (Firefox always, Safari often, IE7 at least once or twice along the way), then it’s good.

But in this case I had an entire definition that was completely unnecessary. It wasn’t hurting anything in Firefox or Safari, but it was doing all sorts of crazy crap in IE6. Naturally, in such a situation, I blame Microsoft. Read more »

Drat.

As I was assembling the current site redesign, I took extra care to ensure that this time around it would be compatible with IE6, as much as a I detest it. I got rid of all of the 24-bit transparent PNGs, opting instead for minor design alterations that could rely instead upon 8-bit PNGs, non-transparent 24-bit PNGs or JPEGs. I even tested the code for the navbar to ensure that it was properly floated and that the drop-down menus worked.

But then I must have gotten into a fine level of finessing the placement of certain objects or… something. At any rate, I’ve done something in the past few days that, now that I bother to check, apparently breaks the navbar in IE6.

I’ll have to futz some more and try to undo whatever I did (and hope it isn’t something that’s critical to the perfect layout in every other browser out there). In the meantime, my apologies to my one regular IE6 visitor. (You know who you are.) Oh well, at least I have a regular visitor.