W3C home > Mailing lists > Public > www-style@w3.org > July 2010

Re: [css3-fonts] How to handle download error in case of multiple @font-face for a font-family?

From: Yuzo Fujishima <yuzo@google.com>
Date: Thu, 15 Jul 2010 12:11:36 +0900
Message-ID: <AANLkTim-LmdUFcTh0-BFskJEUfJRAwmjYzca1eeFnmTF@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: John Daggett <jdaggett@mozilla.com>, www-style@w3.org
Hi, John, Tab,

Thank you for the responses.
Please consider adding to the spec some text for clarification.

Yuzo

On Thu, Jul 15, 2010 at 3:52 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Wed, Jul 14, 2010 at 5:55 AM, John Daggett <jdaggett@mozilla.com>
> wrote:
> > Yuzo Fujishima wrote:
> >
> >> /* Second */
> >> @font-face {
> >> font-family:myfont;
> >> src: url(DownloadErrorNumber.ttf); /* Assume this causes a download
> error */
> >> unicode-range: U+30-39;
> >> }
> >>
> >> What should happen if DownloadErrorNumber.ttf is unavailable and causes
> >> a download error for the second rule? Should we:
> >> (A) Ignore only the second rule, i.e., the first and the third rules
> >>     remain in effect , or
> >> (B) Ignore all the rules for the same font family, i.e., ignore all the
> three?
> >
> > It looks like the definition of the @font-face 'src' descriptor needs to
> > be clearer about this, the intent is that if all the values in the src
> > list fail for whatever reason that face is ignored, the effect is
> > equivalent to the omitting the @font-face rule definition (option (A) in
> > your list.

> Agreed that (A) is definitely what's desired, and that the prose needs
> some clarity on the matter.

> ~TJ
Received on Thursday, 15 July 2010 03:12:44 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:29 GMT