@(&*!

OK, so the site is horribly broken in IE and won’t scroll to the bottom. That is annoying. So now it’s broken in a different way, but at least the pages shouldn’t cut off halfway to the bottom. And yes, I’ve said it before and I’ll say it again: IE sucks.

Why something as simple as a two-column layout that displays well in nearly every other browser (although apparently Safari has some issues as well) will get puked on by IE is beyond me. Oh wait, it isn’t beyond me, it’s because Microsoft doesn’t give a damn….

UPDATE: Well, now everything should work. Some of my margins were just off enough that IE and Safari were both getting confused. Plus, I needed to add a second UL to the blogroll so that IE wouldn’t totally munge up the margins. Now that all of that is done, everything seems to be displaying relatively well in IE, although there are a few minor glitches here and there. I’ll do some testing on my Mac later in the day to see if that also fixed the Safari glitches as well.

Oh well, thanks to the miracle of CSS, at least I only had to edit one file… had it been more I might be tearing out what little hair I’ve left…

UPDATE: Yup, looks like Safari displays the page structure just fine. The flourish on the date headers is still a bit off, but otherwise everything looks good..

3 thoughts on “@(&*!

  1. Now that all of that is done, everything seems to be displaying relatively well in IE

    Negative, Jay. The problems on the library’s version of IE persist. Non consistently, however, and this is really annoying. Your main page looks about right to me, but as soon as you get into some of the reply windows, the same things occur: unfinished pages and non-aligned links (on this particular page, all the links starting form Campaign Web Review downwards come into the main yellowish area). However, other pages seem to display well enough.

    But think of how the library folks would react if I (a mere user) suggested they switch over to Firefox or Opera, or at least offer them as an alternative. (But to imagine their reaction, you would have to know German library folk, and the less you know, the better you will sleep ;-))

    J.

  2. I’m guessing that IE is caching the old version – another @&#&! IE bug. Most of the time hitting shift and clicking the reload button makes it fetch a new version rather than the cached one.

    But think of how the library folks would react if I (a mere user) suggested they switch over to Firefox or Opera, or at least offer them as an alternative. (But to imagine their reaction, you would have to know German library folk, and the less you know, the better you will sleep 🙂 )

    I can only imagine… 🙂

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.