Font Awesome problem - the fonts don't display correctly

[titlebar02]

^^^ That print screen is from the Font Awesome site at Github.

Edit - I'm using FF 22 and Vista x32.

The fonts display correctly for me in IE.

I checked this forum - Search found 7 matches: font awesome but the results are really old. The newest is from 2010.

I checked out the info at a thread at support.mozilla.org: Why doesn't firefox display properly icons in sites like github and font awesome?

* gfx.downloadable_fonts.enabled was (and is) set to true.
* In safe mode the fonts still don't show up correctly.
* The thread talks about language setting issues but my set up was (and is) US English.

What else can I do???

===

I don't know how long I've had the problem. Hmm... years? Now that I think about it - I remember those ugly rectangles appearing at Github and some porn sites but I thought it was a noscript thing because I use that add-on to disable font-face.

The problem is the fonts are a lot more common now and those ugly rectangles are starting to appear everywhere.



They are FF 22 and Vista x32.

[Lee_Dailey]

howdy titlebar02,

that page works correctly for me. i'm using ff22 on win7x32. i have no idea why you are not seeing the proper stuff.

have you tried to force a full reload of the site? [shift-reload button] or perhaps clear your cache?

take care,
lee

[titlebar02]

howdy titlebar02,

that page works correctly for me. i'm using ff22 on win7x32. i have no idea why you are not seeing the proper stuff.

have you tried to force a full reload of the site? [shift-reload button] or perhaps clear your cache?

take care,
lee

Reloading, clearing the cache, even restarting. Nothing works. As far as I know - Font Awesome stuff doesn't work for me at any site. You reminded me to give o/s and version details in my first post. They are FF 22 and Vista x32.

[Elbart]

Is browser.display.use_document_fonts set to 0? Default is 1.

Does it also happen in a new, clean profile?

[titlebar02]

Is browser.display.use_document_fonts set to 0? Default is 1.

Does it also happen in a new, clean profile?

browser.display.use_document_fonts set was set to 0. I changed it to 1 and restarted Firefox. No change. The fonts still don't display correctly.

it's very late for me - I'll create a new profile tomorrow.

[Elbart]

If you type "font." in about:config, are there actually any "user set" entries?

[titlebar02]

If you type "font." in about:config, are there actually any "user set" entries?

I'm not entirely sure what you mean. You mean the bolded stuff - right?

Code: Select all

font.name.serif.x-western Trebuchet MS
font.size.fixed-x-western 16

I'm brain dead - I entirely forgot that years ago I, myself, set up Trebuchet MS as a sort of defacto "default" font. I can't even remember how. Maybe in the user-such-and-such.css or wherever. I'll figure out what I did and post about it later.

And - I'll make a clean profile as a test.

===
Edit #1

I found "user-such-and-such.css or wherever" aka userChrome.css

Code: Select all

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");

* { font-family: "Trebuchet MS" !important; font-size: 9pt !important; } /* Global UI font */

I don't know how/when/if I set up "font.size.fixed-x-western" to 16.

===
Edit #2

In a clean profile - the fonts display correctly.

[Lee_Dailey]

howdy titlebar02,

kool! [*grin*] you tracked it down and now others who run into similar problems will be able to see how to fix it.

i had totally forgotten that you could force font replacement ... [*blush*]

take care,
lee

[titlebar02]

howdy titlebar02,

kool! [*grin*] you tracked it down and now others who run into similar problems will be able to see how to fix it.

i had totally forgotten that you could force font replacement ... [*blush*]

take care,
lee

Questions

• How do I force font replacement?
• Is the font object the same as font-face?
• What other about:config settings can I check? I set noscript to block font-face. And I guess noscript changed that (and other things?) in my about:config. If so - that would explain that even in safe mode - Font Awesome doesn't work.

I checked the Noscript icon drop-down and I was reminded of something obvious. At fortawesome.github.io (etc) Noscript indicates font objects are being blocked.

[Lee_Dailey]

howdy titlebar02,

i was referring to the use of the "font-family:" code making firefox use that instead of what the page might specify. i had forgotten one could _do_ that. [*grin*]

take care,
lee

[Elbart]

• How do I force font replacement?
• Is the font object the same as font-face?
• What other about:config settings can I check? I set noscript to block font-face. And I guess noscript changed that (and other things?) in my about:config. If so - that would explain that even in safe mode - Font Awesome doesn't work.

NoScript can change the setting regarding downloadable fonts, yes, but it isn't setting any font-overrides.
In your opening post, you said that you had the problem for years. Maybe you experimented with a font-addon and then forgot that you changed some settings.
Glad to hear that the site is working in a new profile.

[titlebar02]

• How do I force font replacement?
• Is the font object the same as font-face?
• What other about:config settings can I check? I set noscript to block font-face. And I guess noscript changed that (and other things?) in my about:config. If so - that would explain that even in safe mode - Font Awesome doesn't work.

NoScript can change the setting regarding downloadable fonts, yes, but it isn't setting any font-overrides.
In your opening post, you said that you had the problem for years. Maybe you experimented with a font-addon and then forgot that you changed some settings.
Glad to hear that the site is working in a new profile.

In pure frustration I went to fortawesome.github.io and I allowed Font objects in Noscript. The result? The fonts displayed just fine.

My Noscript setting for "Forbid @font-face" was enabled. I changed it to disabled and I went to another site as a test to see if the fonts worked. They did.

===

New question

• How risky is it to allow font-face?