The Font-Face Firefox Fiasco

Post by andrewcooke » Thu, Jul 05, 2012, 7:58 PM UTC

JoshTriplett wrote: post #10

andrewcooke wrote: post #7

so how do google web fonts work? i just started to use them - all i do is include a http://fonts.googleapis.com/css?family=Muli:300,400 rel="stylesheet" type="text/css"> and everything "just works". even in firefox. as far as i know, the fonts are being pulled in from google. all i did was include the above link in my pages, but my site is served from my isp ( http://www.acooke.org if you're curious). that's fonts, i…

Loading fonts from another domain requires that domain to explicitly whitelist your use as acceptable, using a CORS (cross-origin resource sharing) policy. ~$ GET 'http://fonts.googleapis.com/css?family=Muli:300,400' | grep src: src: local('Muli Light'), local('Muli-Light'), url(http://themes.googleusercontent.com/static/fonts/muli/v4/zR-6QGMCFX5j-6nbH_HpIQ.ttf) format('truetype'); src: local('Muli'), url(http://them…

Post by leephillips » Fri, Jul 06, 2012, 1:02 AM UTC

bryckbost wrote: post #3

Zirro wrote: post #2

"It seems Firefox is the only browser to adhere to the specification in this regard." I fail to see how being the only browser to honour the specification is anywhere near being a "fiasco" (which is defined as "a thing that is a complete failure"). There's most likely a reason for the way the specification is designed, and in this case Firefox should get credit for being the only browser doing it correctly.

True. The fiasco is more or less around the issue of discovering the root cause of why my fonts weren't displaying properly in Firefox, when they did in webkit.