W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2016

[csswg-drafts] [css-fonts-4] Extra unknown arguments to format() specifier should forbid font downloads/uses

From: litherum via GitHub <sysbot+gh@w3.org>
Date: Fri, 21 Oct 2016 20:15:00 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-184559366-1477080899-sysbot+gh@w3.org>
litherum has just created a new issue for 

== [css-fonts-4] Extra unknown arguments to format() specifier should 
forbid font downloads/uses ==
When discussion the format() specifier with regards to font 
variations, we came across diverging behavior between different 

There are two possible mechanisms (that I know of) for fallback:

@font-face {
    src: url("file-novariations.otf") format("opentype");
    src: url("file-variations.otf") format("opentype", "variations");


@font-face {
    src: url("file-variations.otf") format("opentype", "variations"), 
url("file-novariations.otf") format("opentype");

Currently, Edge and Firefox would download the variation font even 
when though the browsers don't (currently) understand variations.

The spec states:

> The format hint contains a comma-separated list of format strings 
that denote well-known font formats. Conformant user agents must skip 
downloading a font resource if the format hints indicate only 
unsupported or unknown font formats.

This seems to imply that the format() identifier will be used if any 
of the arguments are known. Instead, in order to support modern and 
future font behaviors, web authors should be able to list the 
requirements that the browser needs to understand in order to use a 
font. Therefore, the format() identifier should be used if all of the 
arguments are known.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/633 using your GitHub 
Received on Friday, 21 October 2016 20:15:11 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:04 UTC