Original page (source) is http://www.keithjbrown.co.uk/vworks/design/design_2.shtml, where he shows how to translate a page from tables to CSS.
However, I had to go a further step to add a variable min-height, based off of the upcoming events box... if there were more events, we add more to the min-height. Less events, less min-height.
Now the annoying thing is, now my page renders completely differently on every single browser. Close enough to what I want for most, but the variations are quite.. iffy. I think the issue here is the fact that I used the 'em' value, instead of pixels, as I had been doing. Why? Because min-height would be pointless if someone changed the size of the font, which you can easily do on Safari, and that breaks it like a little girl breaking her doll by dropping it off a truck on the beltway.
...Granted, even with using 'em' instead of 'px', increasing/decreasing the size more than once will break the page. Or at least make it look ugly.
So maybe I'll stick with pixels.
Also, another funky thing: Safari adds random spacing above and below my main chunk. I can't figure out why. It's caused by the use of 'p' tags, but I need p tags! Having no 'p' tags = de ugly. It doesn't happen in other browsers, so I don't see why it should be happening in Safari. WTFmuch?
Yeah, OmniWeb doesn't understand min-height at all.
Opera has left-side-bar displaying issues: notably, the repeating background arrow doesn't repeat, and the entire thing is offset to the left by 8 or so pixels.
You know, maybe I should just give up and go back to tables. They're ugly, codewise, but they seem to work. Very well, actually.
You know, I think I'll go to bed. And we'll see from there. XP I hate scrapping work, and making the past, oh, several days worthless, but... since tables work so much better (it renders the same way, more or less in just about every single browser... :P fuck that, ne?)