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

RE: css3-fonts: should not dictate usage policy with respect to origin

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Fri, 15 Jul 2011 23:57:25 +0000
To: Christoph Päper <christoph.paeper@crissov.de>, "W3C Style" <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178292AF86E@TK5EX14MBXC296.redmond.corp.microsoft.com>

> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf
> Of Christoph Päper
> Sent: Tuesday, July 05, 2011 4:41 AM
> To: W3C Style
> Subject: Re: css3-fonts: should not dictate usage policy with respect to
> origin
> Levantovsky, Vladimir:
> > Yet, the overwhelming majority of people have agreed there _are_ many
> good reasons to have this requirement. Should their opinions also be
> considered?
> Sure, and they should be rejected - actually redirected, since many of
> these reasons are quite valid (others less so), but they (and the
> requirement itself) should rather be moved to a more suitable, possibly
> yet to be drafted specification, e.g. "Web Fonts". Leave both WOFF and CSS
> alone, they are simply not the right place.

The right place for what ? The right place to define requirements needed to
achieve CSS3 Fonts interop is the CSS3 Fonts spec. This may be a separate 
concern from an architecture standpoint; but whether the font specified in 
the src descriptor of @font-face should load or not is certainly not a separate 
concern to users of the features or to its implementors. It's perfectly 
appropriate to define the actual mechanism elsewhere and it was never the goal 
to specify the details of the actual enforcement mechanism in CSS3 Fonts. 

It's fine to disagree with the merits of the requirement. But let's not argue 
it's objectionable to require same-origin in CSS3 Fonts yet perfectly OK to 
have another spec require CSS3 Fonts to be implemented along this requirement 
for the purpose of achieving conformance in 99.99% of the use-cases CSS3 Fonts 
is designed for. The aim is to ship interoperable web fonts implementations, 
not to maximize the number of normative documents defining that interoperability.
Received on Friday, 15 July 2011 23:57:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:02 UTC