Why do web fonts in Firefox work in a different domain?

Question

I experimented with the fantasy of the new features of the OpenType font in Firefox 3.5 and I had a problem. I tried to embed the font in a different domain than the page on which it will be used, and this did not work. I thought it was a mistake, but from what I read on the MDC man page, I noticed this note:

In Gecko, web fonts are subject to the same domain restriction (font files must be in the same domain as the page using them) unless HTTP access controls are used to access this restriction.

It looks like they specifically designed the browser this way. Out of curiosity, why would they do this? Is there a security risk when embedding a font? Or is it legal or copyright issues? Or something else?

Answer 1

If you want to get around it, you can try adding this to your .htaccess:

Header set Access-Control-Allow-Origin * 

To answer your question, this is probably due to the fact that since version 3.5 of Firefox supports the role sharing standard .

Answer 2

Legal trademarks and copyrights sometimes restrict domain-based use when embedding fonts.

Edit: That's why you should always look at the tiny letters of the font licenses you can buy. If you created it, you have full ownership and no problem.

PS: I am not a lawyer, but I can confirm this case with several of my clients.