On Dec 23, 2008, at 8:43 AM, David Hucklesby wrote:
> In most browsers running on 96 DPI displays, a font-size of 82%
> displays at 13px. With the font stacks I am using, this is the
> font-size I would like to use for monospace fonts to match 100%
> font-size of other text.
>
> Oddly, with a base font-size of 100% on the BODY, Safari (Win & Mac)
> and Google Chrome display monospace font of 82% at a miniscule 11px.
> Even more strange, if I change the base font to 16px, Webkit now
> behaves as other browsers and displays this same font at 13px.
>
> FWIW I do not see this behavior in other browsers - even Camino.
>
> Should I expect this?
Yes. In some way. It is a complicated issue with font-fallback and
users preferences. WebKit has indeed a different behaviour than
others. They have, I believe, an open bug on this.
I assume that you've added the 'monospace' keyword in your rule for
monospace font.
Compare the following:
[style]
pre {white-space: pre;}
.a {font-family: monospace;}
.b {font-family: 'DejaVu Sans Mono', monospace;}
.c {font-family: 'DejaVu Sans Mono';}
p {font-family: 'DejaVu Sans Mono';}
[html]
<pre class="a"> xxxx</pre>
<pre class="b"> xxxx</pre>
<pre class="c"> xxxx</pre>
<p class="a">xxxx</p>
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/
