IE fix
I've just implemented one of my ideas, my last one, which was to stick some tables back into the code to fix up IE problems. They're user-agent based, so nobody else should see them. If you're an IE user, take some time to click this link, then come back to this page, hold down Control and click the Refresh button near the top of your window. You don't need to know what it all means, but it should make things slightly prettier.
You'll note, along with people using other browsers, that the footer has been moved into the content column, rather than spanning both columns. On Gecko browsers, this is to stop the comment Javascript from moving the footer down without closing the whitespace above it. For everyone else, it just makes things a lot easier.
I'd like to point out that we here at Something Emporium have a proud and noble tradition of IE problems, and this is unlikely to be the last. My problems with tables aren't just motivated by a wish to be cutting-edge or ponsy – CSS has been a standard for eight years, nine in December, and anyone who knows the standards process can ponder how long it was a working draft before that. Tables are slow, they're inflexible, they don't degrade and they don't print nicely. Furthermore, and this is probably the most important reason, they make life a helluva lot harder for people who aren't reading this on a huge 19" monitor – perhaps they're looking at a cellphone screen or listening to their screen-reader software. In these cases, semantic markup makes things Better.
Found that snow I was looking for by the way!
You'll note, along with people using other browsers, that the footer has been moved into the content column, rather than spanning both columns. On Gecko browsers, this is to stop the comment Javascript from moving the footer down without closing the whitespace above it. For everyone else, it just makes things a lot easier.
I'd like to point out that we here at Something Emporium have a proud and noble tradition of IE problems, and this is unlikely to be the last. My problems with tables aren't just motivated by a wish to be cutting-edge or ponsy – CSS has been a standard for eight years, nine in December, and anyone who knows the standards process can ponder how long it was a working draft before that. Tables are slow, they're inflexible, they don't degrade and they don't print nicely. Furthermore, and this is probably the most important reason, they make life a helluva lot harder for people who aren't reading this on a huge 19" monitor – perhaps they're looking at a cellphone screen or listening to their screen-reader software. In these cases, semantic markup makes things Better.
Found that snow I was looking for by the way!