W3C home > Mailing lists > Public > www-style@w3.org > April 2010

[css3-fonts] same-origin restriction definition

From: John Daggett <jdaggett@mozilla.com>
Date: Mon, 5 Apr 2010 01:18:36 -0700 (PDT)
To: www-style <www-style@w3.org>
Message-ID: <1331460226.99370.1270455516898.JavaMail.root@cm-mail03.mozilla.org>
Follow-up to Bert's original mail "[css3-fonts] various comments and typos"

  http://lists.w3.org/Archives/Public/www-style/2010Mar/0553.html

Bert Bos wrote:

> k) Appendix A doesn't seem to belong in this spec. The "same-origin"
> restriction is also incompatible with W3C's Recommended Web architecture
> (see, e.g., section 2.5 in "Architecture of the World Wide Web, Volume
> One" at http://www.w3.org/TR/2004/REC-webarch-20041215/#uri-opacity)

I'm not at all clear why same-origin restrictions are incompatible
with W3C's Recommended Web architecture.  Same-origin restrictions
exist for scripts, are you saying those are incompatible also?

The reason for defining this here is that this spec defines the load
behavior of @font-face and a same-origin restriction affects that.
Whether that's required or not is probably an issue to be decided in
conjunction with the newly-formed Web Fonts group but having the
description of this in the same spec where @font-face is defined
certainly makes things easier for authors and implementers.

John
Received on Monday, 5 April 2010 08:19:10 GMT

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