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

Re: A way forward

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 24 Jul 2009 17:32:59 -0500
Message-ID: <dd0fbad0907241532i6b7d8496o40b72596abffc46d@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotypeimaging.com>, "robert@ocallahan.org" <robert@ocallahan.org>, John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
On Fri, Jul 24, 2009 at 5:27 PM, Sylvain Galineau<sylvaing@microsoft.com> wrote:
> I believe there is a simple work-around to resolve this problem. Root string
> in EOT-Lite does not have to be empty, it may contain the domain name of the
> origin that will simply be ignored by all other browsers except IE. When
> EOT-Lite is processed by Firefox and other browsers – the root string is
> ignored and same origin restriction is applied. For legacy IE browsers – the
> root string will serve the same purpose of same origin restriction and,
> therefore, no need to require Referrer checking.
> Vladimir
>
> Technically that’d work but it also defeats one of the main purposes of the
> original proposal which was to get us all out of the rootstring management
> nightmare.

That's really only necessary (1) if the font vendor's EULA requires
it, (2) if an individual author decides that it's easier than Referer
checking, and (3) as long as current IEs with the old behavior persist
enough for us to care.

Considering that in any *new* proposal we have *no* consensus font as
long as (3) holds, we're still green.

~TJ
Received on Friday, 24 July 2009 22:33:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:03 GMT