Need help? Check out our Support site, then

Custom Fonts not Working

  1. @thesacredpath @designsimply @villagedrummerfiction
    The fonts are working fine for me using both Firefox 9.0.1 and IE8. They have worked each and every time that I have entered this thread and clicked into the blog in question.

  2. @villagedrummerfiction
    I'm over 55 and visually challenged. The font size on the blog is easy for me to read just as it is now. Did you know that anyone on the interent can increase or decrease the font size on any site we visit in 2 seconds flat?

  3. villagedrummerfiction

    My wife said the same thing, but I have trouble reading it. It was better once I bolded the text, but still rather light gray colored. I wonder if you are seeing it correctly or the enlarged version. IF they look the same on both Firefox and IE, you are seeing the correct version (not the one I'm seeing with my Firefox). Thanks for your advice.


  4. Yes I am seeing bolded text using both IE8 and Firefox 9.0.1 browsers. IMO the bolding is unneccessary.

  5. I'm wondering if there is a difference between Firefox for windows and Firefox for a mac. I'm on a mac and the font customization doesn't work for me. I can't even see the fonts on Firefox. It does, however, work in Safari. I tried it at work on a windows machine and IE works. I wiill try to test Firefox on the windows machine tomorrow.

  6. Oh and btw.. there is a HUGE difference between changing font sizes in code as opposed to just changing how you view it in a browser. Yes, people can change the browser, it is easy - but there are artistic reasons to want to change the size of a font in the native website language.

  7. @bethbeeman'
    This thread posted by villagedrummerfiction pertains only to the Fjords04 theme. Please start another thread of your own for your Twenty Eleven CSS editing questions as CSS editing is theme specific. Here's the link to do that with

  8. @timethief It's not a theme specific issue. It's a custom font package issue. I'll keep posting :)

  9. @bethbeeman
    I can see the font changes on your Twenty Eleven theme blog in both Firefox 9.0.1 and in IE8. If you wish to check corss browser compatibility you can use this free site

  10. edit: "corss" was meant to be "cross"

  11. Thanks... but it's also about the usability of the custom fonts package - can't edit my site from Firefox. No problem in Safari. I'm on a Mac - it may be mac version of FF issue.

  12. You can upgrade any browser version here.

  13. Thanks.. but I don't need help using an ap to view in other browsers or instructions on how to upgrade my browser. I'd like to get back to the discussion on the first page of this thread. I will check the fonts out in IE at work today. I've also opened a support ticket with Typekit.

  14. Ok... I finally got this resolved thanks to the wondertul Typkit staff. Here's what they recommended. The first option fixed my problem with Firefox.

    From Typkit:

    Issues with Firefox are usually related to some browser setting that is causing trouble. Here are couple things you can check:

    There's a preference in Firefox preferences that disables webfonts (and any other custom font preferences) on all webpages. Under Preferences > Content > Fonts & Colors > Advanced > Allow pages to choose their own fonts. The box should be checked.

    There's also a hidden preference in Firefox that disables downloadable fonts. Open a new tab, type about:config in the URL bar and hit enter, type downloadable_fonts in the filter box, and make sure the value of the gfx.downloadable_fonts.enabled preference is set to true. To change the value, just double click on the preference row.

    Web developer toolbar (a Firefox extension) has an option for disabling referrers that will prevent fonts from loading properly. To check: In the toolbar, open the Disable menu and make sure that the Disable Referrers option is unchecked.

    You can also disable referrer request headers via a hidden preference in Firefox. Some addons or other software might have changed this preference for you. To check: Open a new tab, type about:config in the URL bar and hit enter, type network.http.sendRefererHeader in the filter box, and make sure the value of the network.http.sendRefererHeader preference is set to 2 (not 0 or 1). To change the value, double click on the preference row.

    95% of the time, one of the above solves issues with Firefox.

  15. Hmmm, interestingly enough in my FF, I just checked all those things and mine are all what they should be.

    {shrugs and mumbles}

  16. I have however bookmarked this for future use.

  17. @thesacredpath I'd suggest going to the Typekit page and sending them an email. They are incredibly response and helpful. This was the first thing they wanted me to try... I got the impression that there might be some other tricks :)

  18. stuttgenstudios

    I have been having the same EXACT problems as other people in this thread regarding Firefox with my custom fonts that were paid for not working 8 times out of 10 for the past 6 months. I have emailed Typekit and have not heard back. Did anyone else try? This is so frustrating...

  19. villagedrummerfiction

    I found out that Firefox no longer suppports XP (which is what I am still running on). I think FF will work if you have Windows7, but I'm fed up with them. I switched to Google Chrome and have not had any problems since.

Topic Closed

This topic has been closed to new replies.

About this Topic