W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

Re: .webfont Proposal

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 8 Jul 2009 14:43:31 -0700 (PDT)
To: Tal Leming <tal@typesupply.com>
Cc: Erik van Blokland <erik@letterror.com>, www-font <www-font@w3.org>
Message-ID: <24142586.205561247089411669.JavaMail.root@cm-mail02.mozilla.org>
> - The <allow> element would list domains that are licensed to use the
> font. A meta URL, "any", would signify that the font could be used on
> all domains.

This is a root string proposal in another form and suffers all the same
problems, a complete pain to manage, need URL's for every staging and
cached version, including every possible local version (i.e. the
complete set of possible file://<drive>/<path> permutations possible for
those working as site devs).  All web-caching solutions (e.g. Akamai)
would need to generate new versions of fonts per server, since the base URL 
is going to be different.  Change your site around?  Regenerate all your
fonts.  Generally sucky.

Same-site origin restrictions are simple, font linking is allowed only
when the origin is the same.  CORS is only involved for *exceptions*,
such as a font library wanting to provide general access to everyone, so
99% of the time authors don't need to worry about CORS at all.

Received on Wednesday, 8 July 2009 21:44:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:40 UTC