Internet Explorer can [censored] my [censored].

Seriously.

I spent two hours last night poring over the WordPress template files and the stylesheet for the theme I’m building, searching for some error that would explain why IE was rendering the page improperly.

Exhibit A (Firefox):
Exhibit A - Firefox

Exhibit B (Internet Exploder):
Exhibit B - Suck it, IE

See that grey border on the right? It’s supposed to be a solid line from top to bottom, but IE was pushing it to the right partway down, and rendering it twice at the bottom of the page.

After much frustration, I realized that there must be something “special” about the content of one or more entries on the page. Through trial and error, I managed to isolate the problem to a single entry: a movie review for Dungeons & Dragons: Wrath of the Dragon God. I tried removing any unusual formatting (image float, footnotes) without success. Finally, after hacking the entry to pieces, I removed a couple of lines where italic text wrapped from one line to the next. Voila, no more rendering problem. It didn’t make any sense, but there it was: italics.

So I searched for “internet explorer italics bug” in Google and I came up with this entry at PositionIsEverything.net. Seems IE doesn’t respect element sizing very consistently. The author provides several good examples as well as a couple of ways to work around the problem. I tried the “overflow: visible” method, which seemed to work until I put the rest of the contect back in the entry, at which point the entire middle section of the page got bumped down below the sidebars in IE (but not in Firefox).

This morning, I set the width of the rogue element to 95% and voila… all better. Well, except for a little “extra” padding on the right, but that doesn’t actually affect the rendering of the border.

I’m not finished working on the new theme, but this particular bug as been fixed. IE can still [censored] my [censored].

7 thoughts on “Internet Explorer can [censored] my [censored].”

  1. Dude, I wouldn’t worry much about it. With IE7 in beta form, and the IE developers working on such CSS bugs, I would just worry about browsers that matter and then look back at IE once they release a final version of IE7. Just my $0.02.

  2. If they fix IE, which browser will be the focus of my righteous indignation?

    IE7 will only fix CSS problems if people actually upgrade their browsers once it’s released. I work for a company that switched from Windows 3.1 to Windows 95 in 1997, then to Windows 2000 in 2004, so I’m aware of how slowly new technology can be adopted in some cases. Granted, we’re using IE6 now, but it wasn’t all that long ago when we switched from 5.5.

    I just don’t want to wind up having to plaster a “Best if viewed with…” disclaimer on my site.

  3. It’s a proven fact that TNR isn’t good for extended periods of on-line reading.

    Hm… Proven, though I can’t find anything on-line to back up that statement. Oh, well. 🙂

  4. It’s a proven fact that TNR isn’t good for extended periods of on-line reading.

    I’m using TNR in the new theme, but only for section headings and such. The main body text is going to be sans-serif, most likely good ol’ Arial. I’ve almost finished the layout and styling of the new theme, so you’ll be able to see for yourself whether I’m trying to give people migraines. 😉

Leave a Reply to KJToo Cancel reply

Your email address will not be published. Required fields are marked *