On Dec 24, 2008, at 10:26 AM, David Hucklesby wrote: > It seems that the "monospace" keyword affects more than just Webkit. > Playing with the font stack as you suggested, I found that > *eliminating* > that keyword made Webkit play along --- but using *only* that keyword > gives Gecko the same bad behavior I noted for Gecko. Well, Firefox > 3.0.4 on Mac, anyway.
'bad behaviour' is very relative [1]. But yes. Look at your prefs in Gecko: for 'monospace' the default is 13px (and that is cross platform), where as the default for serif/sans-serif is 16px. WebKit has the same font-size settings. One of the reasons is that monospace fonts tend to be much larger (aspect-ratio) than serif/sans-serif fonts. In the future, Gecko will probably get rid of all those settings completely, and use font-size-adjust to create an equally sized pref setting for fonts. Ideally, in your situation, you'd use font-size-adjust. Unfortunately, that is only supported by Gecko. I do this, progressive enhancement at work. [1] and, as was clear from my previous answer, I don't think the behaviour in WebKit based browsers is a bug in the narrow sense of the word. Philippe --- Philippe Wittenbergh http://l-c-n.com/ ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
