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

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

From: Florian Rivoal <florianr@opera.com>
Date: Tue, 21 Jun 2011 14:41:11 +0900
To: "John Hudson" <tiro@tiro.com>, "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotypeimaging.com>
Cc: "Glenn Adams" <glenn@skynav.com>, Martin J. D├╝rst <duerst@it.aoyama.ac.jp>, "Jonathan Kew" <jonathan@jfkew.plus.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "W3C Style" <www-style@w3.org>, "3668 FONT" <public-webfonts-wg@w3.org>, "www-font@w3.org" <www-font@w3.org>
Message-ID: <op.vxevexkf4p7avi@localhost.localdomain>
> True, and this is why I believe it is important to define what the  
> default initial state is. I'd guess that the default state for many  
> resource types would be "From-Origin=any" but it can also be resource  
> type specific, so there can be cases (e.g. webfonts?) where setting a  
> default to "From-Origin=same" could make sense. It really needs to be  
> looked at from an author point of view and whether a particular default  
> state would make authors' life easier or not.

In the current Form-Origin proposal, From-Origin=any is achieved by not  
having the header. I am not sure I agree that not having this header  
should mean different things for different types of resources. Consistency  
and predictability leads to fewer bugs.

  - Florian
Received on Tuesday, 21 June 2011 05:42:16 GMT

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