r
Cc : wha...@whatwg.org; Mikko Rantalainen; www-st...@w3.org
Objet : Re: [whatwg] New work on fonts at W3C
On Mon, Jun 22, 2009 at 4:23 PM, Brad Kemper wrote:
> So your argument, in effect, is that site owners should not be allowed to
> restrict their content, because it might actually work?
A server serving documents containing references to content from other
sites, embedded or not, does not distribute that content. It would only
redistribute in case of hot piping. Some sites have a policy disallowing
publishing backdoor hyperlinks; the legal implications of such a policy are
quest
Aryeh Gregor wrote:
> On Mon, Jun 22, 2009 at 10:43 AM, Brad Kemper wrote:
>> This makes sense to me. I was surprised and found it counter-intuitive to
>> learn that CORS could be used to list the servers that are allowed access,
>> but could not and would not restrict access to servers not on that
On Tue, Jun 23, 2009 at 8:15 AM, Aryeh Gregor
> wrote:
> I believe that's the major rationale for not permitting cross-origin
> restrictions on existing media types. The only way this could work is
> if *all* browsers agreed to implement it all at once, and it would
> still seriously annoy a lot
On Mon, Jun 22, 2009 at 4:23 PM, Brad Kemper wrote:
> So your argument, in effect, is that site owners should not be allowed to
> restrict their content, because it might actually work? Or because older
> browsers and browsers that have yet to implement the standard could be used
> for the same sor
If browsers start refusing cross-domain image requests, some servers will
work around this problem using hot piping. I am not sure this would be
good-but I cannot say it would be bad either.
IMHO,
Chris
On Mon, Jun 22, 2009 at 10:43 AM, Brad Kemper wrote:
> This makes sense to me. I was surprised and found it counter-intuitive to
> learn that CORS could be used to list the servers that are allowed access,
> but could not and would not restrict access to servers not on that list. Why
> not? If the
Anne van Kesteren wrote:
> On Sat, 20 Jun 2009 17:07:06 +0200, Brad Kemper
> wrote:
>> I didn't mean it should be restricted by default. Just that CORS could
>> restrict it like anything else if you told it to. And that the font
>> could instruct the CORS mechanism.
>
> That's not how CORS works.
