The bug basically is when you put a comment in the middle of a CSS attribute. I’ve only tested this with backgrounds, but I’m guessing it will “work” (the bug, that is) if used in the middle of any mutli-value CSS property.
background: #FFF /* #EEF */ url(background.jpg) 50% 0 no-repeat;
IE 5.5 outputs no background image, though it does get the background color right. Removing the /* #EEF */ comment from the CSS makes it work fine. Does anyone know why this is? It’s interesting to also make note that IE 5.01 doesn’t have this problem, nor does IE6. I think there are fewer bugs in IE 5.01 (although it supports less CSS) than IE 5.5. A few simple things (text-align center and such) to center my current design, and it worked absolutely fine in IE 5.01; IE5.5, however, didn’t center the menu or display the background (due to the bug I just mentioned). In order to center the menu for IE 5.5, which I’m guessing more people use, I had to offset the menu’s centeredness for IE5.01. I’m sure that’s acceptable, as you can still use the navigation. It might not look as pretty, but I doubt many people will be browing my site with IE5.01 (and if they use an old version of IE, there’s not much of a chance that the version will be prior to IE5.5). Thoughts? Anyone encountered this problem before? What were your experiences with it?
Ever thought about throwing CSS away for MSIE5.5?
I am not a big fan of your sIFR headings. The font isn’t the best. It’s good in the header, just not brilliant as the article headings.
May 2nd, 2005 at 5:27 pm
I think the font is too fancy for the current atmosphere this site has. I’d swap it out for georgia or something similar — I read the headers though, so it really isn’t that big of a deal.
May 2nd, 2005 at 7:16 pm
Interesting how you guys are still commenting on my previous entry in this one…
Anyway, I like the font I chose, and I’m going to stick with it until I redesign again. I’d NEVER use a font like Georgia in sIFR because everyone already has Georgia anyway and it would defeat the purpose of using sIFR in the first place. Sorry guys, it stays. I’ll avoid making entries in all caps like this one, though, so that it’s easier to read.
As far as ditching IE5.x support, I don’t think that it’s a bad idea to make the site work in browsers that make it look terrible, because in a lot of cases it’s not that difficult to make the design work fine for those browsers. When I first looked at my blog in IE5.x, it looked terrible, but the fixes weren’t that many, so I decided it was worth doing.
May 2nd, 2005 at 8:06 pm
I wasn’t saying to make it an sIFR, that’d be really unnecessary. Also, sorry for the offtopicness, feel free to just delete my reply, or move it or whatever.
May 2nd, 2005 at 10:05 pm
No problem. If it’s important enough, you’ll inevitably make me aware of it, and if off-topicness is a biproduct of that, then I’m willing to deal with it. Anyway, I don’t like the over-use of fonts, so if I have sIFR at my disposal, then I’m going to use it, and that means more of a font variety. ;)
May 2nd, 2005 at 11:08 pm
I don’t know, Jona. To actually answer your question. Glad you fixed it, though.
As far as Georgia, that would be kind of silly since it’s already an official web font. It is the only serif web-specific font actually. The Times family is a print font.
November 19th, 2005 at 12:01 pm
Just thought I’d let you know your Slightly Remarkable logo does not appear correct in IE 6.0
November 22nd, 2005 at 12:03 pm
Actually now that I browse around your site there are more than a few glitches (’About’ page). Perhaps you should check it out.
November 22nd, 2005 at 12:16 pm