Wrestling the CSS daemon

I’ve known for some time that the blog lay­out would casu­al­ly crap its self if viewed in IE for win­dows, espi­cal­ly if the “Text Size was set to “Largest”. And I have for some time insist­ed that the fix for this was sim­ple… use a bet­ter brows­er and/or oper­at­ing sys­tem.
How­ev­er.
Some poor peo­ple are forced to suf­fer IE, so I’ve looked into it.
I’ve decid­ed it is high time to go to a fixed font size for the lay­out… this gets around most of IE’s ren­der­ing bugs if the user sets the font size to any­thing oth­er than “Small­er” (which for some rea­son is the clos­et to every oth­er browsers inter­pre­ta­tion of the CSS rel­a­tive font sizes). But this intro­duces two new prob­lems.
The design is a lit­tle less ‘flu­id’. I gen­er­al­ly pre­fer to design flu­id for web­sites… I’m just crazy like that.
And the sec­ond is that even with all that IE still does­n’t sup­port CSS font size con­trol of table con­tent… great. So until I find a work around for that one my cal­en­dar in the top left still might look crap… oh well.
Of more con­cern with a fixed font size I’ve lim­it­ed acces­si­bil­i­ty… not a good thing, and one of the many things I’ve been try­ing to avoid. So I’ll just have to final­ly get around to the ‘alter­nate view­ing’ CSS’s.
Look at that I’ve raved on and you prob­a­bly haven’t even noticed that I changed any­thing, right???
Oh, and if you real­ly do care, here’s a nice table that shows just how bad CSS sup­port real­ly is.
Which lists IE’s ‘Font sizes — key­words’ as “Bug­gy — a non-triv­ial bug, which although not nec­es­sar­i­ly always trig­gered, when trig­gered is seri­ous.” See, I was right, get a bet­ter brows­er.