- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Mon, 3 May 2010 22:23:21 +0000
- To: Anne van Kesteren <annevk@opera.com>, John Hudson <tiro@tiro.com>
- CC: "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>, Robert O'Callahan <robert@ocallahan.org>
> From: public-webfonts-wg-request@w3.org [mailto:public-webfonts-wg- > request@w3.org] On Behalf Of Anne van Kesteren > FWIW, I'm not opposed to adding a same-origin protection mechanism for > resources, but I think it should not be limited to fonts. E.g. we could > have > > From-Origin: same > > or some such for resources which would mean that the resource can only > be > used if it is same-origin with the Document to which the resource is > applied. What is limited to fonts ? What in its proposed used for web fonts constrains CORS in any way ? We already have a mechanism to force resources to be loaded from the same-origin as the document. And one major browser has already used it for this purpose (Firefox).
Received on Monday, 3 May 2010 22:23:58 UTC