Re: CORS support font font loading in different browsers

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.

Thanks,
Sergey

From: David Kuettel<mailto:kuettel@google.com>
Sent: ?Friday?, ?February? ?21?, ?2014 ?6?:?47? ?PM
To: Sergey Malkin<mailto:sergeym@microsoft.com>
Cc: public-webfonts-wg@w3.org<mailto:public-webfonts-wg@w3.org>

Hello Sergey,

On Fri, Feb 21, 2014 at 4:30 PM, Sergey Malkin <sergeym@microsoft.com<mailto: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<mailto:www-fonts@w3.org> list is used for?