> Another observation:
> This page also triggers the 'em font-resizing bug' in IE/win...
> ...but the bug is only acting on the #nav since that's the only element
> that has font-size declared in 'em'.
> Font-size keywords on body as a starting-point does not prevent this bug
> - it enforces it. In fact: the use of font-size keywords on any
> container will introduce or re-introduce the 'em font-resizing bug' to
> nested elements that have font-size defined in 'em'.
> This bug may be used to enhance font-resizing in IE/win, but since it's
> usually an unwelcome "effect", and also one that many web designers
> don't notice because they don't test with font-resizing in IE/win, I
> thought I'd mention it.
> The cure is to either avoid using 'em' as font-size unit, *or* to base
> 'em' sized fonts on a font-size that has '%' as unit (usually on body)
> and to avoid keywords anywhere in the mix. There are a few other
> options, but they usually only complicates the matter.
I just read your article (and the accompanying one about Minimum Font
Very interesting, but quite complicated for a beginner such as myself.
Going forward, I want to make sure that I'm following best (or at least
- I should replace the 'small' in my body tag with a percentage? 100%
or 62.5% or ????
- I should then use percentages for sizing all other text elements
('p', 'h1', 'h2', 'ul', 'li' etc).?
- Ems - Ems are new to me. I started using them in the navigation menu
to give a 'margin right' to the horizontal list elements (i.e. to space
out the elements). I was keen that when the text was enlarged, that the
spacing between the menu items would enlarge proportionally. Is this a
good use for ems? Or is there a better unit to use? Maybe pixels will
enlarge in the same way?
Sorry - very basic beginner's questions.
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/