On Thu, Oct 2, 2014 at 9:42 AM, Jonathan Kew <jfkth...@gmail.com> wrote:
>> Or do people need to hardcode
>> UA versions to know what UAs support it?
>
>
> I believe that's what Google Fonts currently does, though IMO a better
> approach is to serve CSS that offers both WOFF2 and older (more
> widely-supported) formats, using the @font-face src descriptor's "format
> hint" to let the browser choose the optimal resource depending on what it
> supports:
>
> @font-face {
> font-family: MyFont;
> src: url(myfont.woff2) format("woff2"),
> url(myfont.woff) format("woff"),
> url(myfont.eot) format("embedded-opentype"),
> url(myfont.ttf) format("truetype");
> }
Could we at least add woff2 to the Accept header when fetching fonts?
/ Jonas
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
