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

On Jun 21, 2011, at 12:41 AM, Florian Rivoal wrote:

> 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

I agree with the position that all resource types should behave consistently and predictably. In my experience implementing web properties for the past 15 years, this means a more permissive default rather than a more restrictive default. 

Having one resource type behave differently or unexpectedly relative to other resource types will decrease overall adoption.

From my perspective, web fonts (still) have significant challenges to their adoption. Challenges quite outside the scope of this WG. I'd rather not see more obstacles constructed.

Garrick Van Buren
612 325 9110
Free, Subscription, and Web Native fonts.

Received on Tuesday, 21 June 2011 13:33:06 UTC