3 ms·
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/
by gcp 14y ago
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 http://dev.w3.org/csswg/css3-fonts/#same-origin-restriction
Some related discussion: https://bugzilla.mozilla.org/show_bug.cgi?id=604421 https://bugzilla.mozilla.org/show_bug.cgi?id=604421
- wiradikusuma 14y agoAt 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.
- lucisferre 14y agoThe 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?