W3C home > Mailing lists > Public > www-style@w3.org > November 2008

Re: [css3-fonts] duplication and @font-face rules

From: Michael Day <mikeday@yeslogic.com>
Date: Fri, 07 Nov 2008 09:05:01 +1100
Message-ID: <49136A0D.70208@yeslogic.com>
To: "L. David Baron" <dbaron@dbaron.org>
CC: www-style@w3.org

>   (A) The user agent uses the first of those values for which it has
>   a usable font (e.g., a local() font that is present or a url()
>   that is in a format it supports) and ignores the rest.
>   (B) The user agent uses all of the values for which it has a
>   usable font, picking each glyph from the earliest in the list that
>   has a glyph for the character.
> (B) seems like it has some advantages, particularly when local() and
> src() are combined, and the font available locally may have more or
> fewer glyphs in it depending on what the user has chosen to install.
> It also feels more CSS-like to me (which could mean it fits author
> expectations better, although maybe not).
> (A) seems like it may have some advantages in terms of speed or
> bandwidth usage.
> However, current implementations in WebKit nightlies and in Gecko
> nightlies seem to do (A).

Prince does (B), and this behaviour is quite useful.

Best regards,


Print XML with Prince!
Received on Thursday, 6 November 2008 22:05:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:41 UTC