- From: John Daggett <jdaggett@mozilla.com>
- Date: Mon, 16 Mar 2009 07:45:35 -0700 (PDT)
- To: Aaron <aaron.cicali@gmail.com>
- Cc: www-style@w3.org
Hi Aaron,
> Since we're already font-challenged on the web, wouldn't it be great if
> we could specify an alternate ruleset if a particular font wasn't
> available?
>
> For instance:
>
> body {
> font: 28px normal georgia, 26px bold times new roman;
> }
Just curious, what's the problem here you're trying to solve? Varying
size based on the font I can see as desirable, not sure I see the use
case for specifying bold or normal per font. Have you played with
font-size-adjust, implemented currently in FF 3.0?
> While we're at it...how about CSS font anti-aliasing? Instead of
> allowing silly little programs like Internet Explorer anti-alias ALL
> fonts on our pages (even little itty bitty ones), shouldn't WE, the
> DEVELOPERS be the ones specifying which fonts to anti-alias? I
> appreciate a good fuzzy edge on my headings, it just doesn't make
> sense in other places.
I'm with Vladimir on this, having an author controlled attribute for
this is a bad idea. These preferences are very user-dependent and
hardware dependent, the level of subpixel aliasing varies across display
types. What might seem nice to a Mac OS user is not necessarily what a
ClearType user wants to see and vice versa. After all, it's the users,
not authors, who are reading the text.
Regards,
John Daggett
Mozilla Japan
Received on Monday, 16 March 2009 14:46:16 UTC