- From: Chris Lilley <chris@w3.org>
- Date: Tue, 26 May 2009 15:00:13 +0200
- To: "Anne van Kesteren" <annevk@opera.com>
- CC: www-style@w3.org
On Monday, May 25, 2009, 8:01:34 PM, Anne wrote: AvK> On Mon, 25 May 2009 18:50:45 +0200, Chris Lilley <chris@w3.org> wrote: >> On Monday, May 18, 2009, 10:09:13 PM, Anne wrote: >>> It is about alleviating the same-origin policy in certain scenarios. >>> (Whether the same-origin policy should apply for fonts at all is >>> something I'm not sure about.) >> I didn't express an opinion on whether it *should be* only that at least >> one implementation *does* currently impose a same-origin policy for >> webfonts, and does allow CORS to be used to widen that policy. AvK> Just to be clear, I didn't mean to imply you were. I was just stating my AvK> own reservation. OK, so we are on the same page, then. Actually I have reservations myself; I discovered this when a talk I was doing, intended to be live but then saved to local disk in case of network issues, mysteriously stopped working. Mozilla (3.5b4) decided that local disk was not the same as w3.org so refused to download fonts any more. I guess w3 should add cors for the webfont download tests, to avoid such problems. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Tuesday, 26 May 2009 13:00:23 UTC