- From: Christoph Päper <christoph.paeper@crissov.de>
- Date: Wed, 20 Jul 2011 20:02:24 +0200
- To: W3C Style <www-style@w3.org>
Sylvain Galineau: > Christoph Päper >> Leave both WOFF and CSS alone, they are simply not the right place. > > The right place for what ? Any kind of transport layer requirements or restrictions, especially normative ones. > The right place to define requirements needed to achieve CSS3 Fonts interop is the CSS3 Fonts spec. Sure. > It's fine to disagree with the merits of the requirement. I don’t necessarily disagree with the default same-origin restriction and its opt-in cross-origin relaxation for *Web Fonts*, I question its merits for *CSS Fonts*, because I see none whatsoever. > The aim is to ship interoperable web fonts implementations, Exactly, and the CSS Fonts module is just one part of “web fonts”. Other parts are supported font formats, e.g. WOFF, and font distribution models, e.g. HTTP with mandatory CORS/FO. CSS Fonts ⊊ Web Fonts
Received on Wednesday, 20 July 2011 18:02:54 UTC