Re: Difficulty with font-face cross-domain restrictions

2013-01-05 Thread Pamela Fox
Perhaps then, it could be a setting/header that we could opt-in-to, instead of having to opt out of, i.e., if I put the header there, then you obey it, but otherwise, you don't care? Why we still had problems after adding "*": we have multiple codebases and have gone through a few iterations of ho

Re: Difficulty with font-face cross-domain restrictions

2013-01-05 Thread Robert O'Callahan
One reason behind this is: what if you were using a font that wasn't free, but had a license that required you to prevent deep-linking of the font from other sites to where it's hosted on your site? Firefox and IE give you a way to do that. Chrome doesn't. In this case, it's a free font so it does