Re: CORS support font font loading in different browsers

On Sat, Mar 1, 2014 at 11:16 AM, Sergey Malkin <sergeym@microsoft.com>wrote:

>  Hello David,
>
>  Did you hear back from Chrome team? Same origin restriction is probably
> most important mechanism of protecting font IP on the Web, but it doesn't
> work if it is not working in one of the most used user agents.
>

Kenji-san found the following tracking bug for CORS support in Chrome:
https://code.google.com/p/chromium/issues/detail?id=28668

This would be a great one to vote for (by staring) as I just did.

Thank you Sergey!

>
>  Thanks,
> Sergey
>
>  *From:* David Kuettel <kuettel@google.com>
> *Sent:* Friday, February 21, 2014 6:47 PM
> *To:* Sergey Malkin <sergeym@microsoft.com>
> *Cc:* public-webfonts-wg@w3.org
>
>  Hello Sergey,
>
> On Fri, Feb 21, 2014 at 4:30 PM, Sergey Malkin <sergeym@microsoft.com>wrote:
>
>> Hi,
>>
>> I checked CORS support for @font-face font download in different
>> browsers. It appears like IE and Firefox apply CORS, but Chrome doesn't (I
>> only had Windows desktop versions). Is this correct or am I missing
>> something?
>>
>
>  That is my understanding of the current behavior as well.
>
>>
>> If yes, what are the plans for Chrome/WebKit/Blink to implement it, for
>> different platforms? Requirement to apply CORS is MUST in CSS Fonts spec
>> and as I remember Chrome team(Tab?) was not opposed to doing this two years
>> ago.
>>
>
>  Let me check and see...
>
>  Thank you,
> David
>
>>
>> Thanks,
>> Sergey
>>
>> P.S. What www-fonts@w3.org list is used for?
>>
>>
>>
>>
>>
>