News for hackers. Stuff that matters.
Re:Firefox cross domain font issue by schrijver on Thursday July 05, 2012 @07:26AM (#4202608)
It would also be nice if Firefox would solve this. If we can load an image from another domain we should be able to load a font from another domain by default.

Though I do see how a font has more potential for malware than an image, the other browser makers apparently don’t see any qualms with cross-domain font loading. Anyone know Firefox’s rationale for doing this differently from the other vendors?

Re:Firefox cross domain font issue by gcp on Thursday July 05, 2012 @07:47AM (#4202649)
It's required by the standard. Firefox complies with the standard, the other browsers don't, so there is nothing for Firefox to "fix".

http://dev.w3.org/csswg/css3-fonts/#same-origin-restriction

Some related discussion: https://bugzilla.mozilla.org/show_bug.cgi?id=604421

Re:Firefox cross domain font issue by wiradikusuma on Thursday July 05, 2012 @08:07AM (#4202690)
At least they should allow it for root domain to access subdomain's. I put all static files in a subdomain to make them free of cookies, but such restriction makes things difficult.
Re:Firefox cross domain font issue by lucisferre on Thursday July 05, 2012 @11:18AM (#4203392)
The reasoning given, that font vendors don't want people linking to their fonts, seems pretty wrong headed. This is just another stupid standard making life harder and hurting productivity for web developers.

I've never managed to fully understand the purpose of any cross-domain rules on the browser. So many can be easily (relatively) circumvented, why waste people's time at all?

Re:Firefox cross domain font issue by robin_reala on Thursday July 05, 2012 @07:50AM (#4202654)
An image is data. A font is an executable. There’re good reasons to not allow this.
Re:Firefox cross domain font issue by camo on Thursday July 05, 2012 @08:38AM (#4202747)
So is javascript.

This is a ridiculous argument - there are no "good" reasons only a lot of FUD and font vendors who want this as a roundabout form of asset protection. The fonts are accessible by anyone who can use wget and can be copied and hosted anywhere else instead. Useless on all fronts, this just restricts the public web from end users.

Do not forget that the website must link to the asset in question. Why would they link to something they don't trust? Everyone trusts jQuery to not be malicious and everyone has links to cross-origin code running on their site. This is what makes the web a "web". Otherwise you would only be able to link with yourself.

Re:Firefox cross domain font issue by barrkel on Thursday July 05, 2012 @10:01AM (#4203029)
Code is data; data is code. There is no fundamental distinction. Image decoders interpret a code, the output of which is a bitmap.