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: Thu, 21 Jul 2011 00:04:56 +0000
To: Glenn Adams <glenn@skynav.com>, Christoph Päper <christoph.paeper@crissov.de>
CC: W3C Style <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178292B7FA7@TK5EX14MBXC296.redmond.corp.microsoft.com>
Two browsers implement SOR interoperably. Two others do not. What other evidence is needed ? The burden is on you to prove that specifying it in another document without any mention of it in CSS3 Fonts is more likely to improve this situation. The implicit claim that more specs results in better interop seems dubious to me, at the least.

From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Glenn Adams
Sent: Wednesday, July 20, 2011 11:32 AM
To: Christoph Päper
Cc: W3C Style
Subject: Re: css3-fonts: should not dictate usage policy with respect to origin

I would like to see evidence of how specifying or not specifying SOR aids or detracts from "CSS3 Fonts interop". I have seen no evidence to date. The functionality of CSS3 Fonts is unaffected by, and entirely orthogonal to SOR or fetch/access algorithms.

G.
On Wed, Jul 20, 2011 at 12:02 PM, Christoph Päper <christoph.paeper@crissov.de<mailto:christoph.paeper@crissov.de>> wrote:
Sylvain Galineau:
> The right place to define requirements needed to achieve CSS3 Fonts interop is the CSS3 Fonts spec.
Sure.
Received on Thursday, 21 July 2011 00:05:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT