This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 55.0.3 not displaying correct website fonts, other browsers do

more options

Firefox 55.0.3 is not displaying the correct headline fonts on this site www.upskills.co.nz. It defaults to Times New Roman. The correct font is Source Sans Pro; which is a Google font, correctly loaded in css and loads correctly in Chrome and other browsers including mobile. Only Firefox is not displaying it correctly. Why?

Firefox 55.0.3 is not displaying the correct headline fonts on this site www.upskills.co.nz. It defaults to Times New Roman. The correct font is Source Sans Pro; which is a Google font, correctly loaded in css and loads correctly in Chrome and other browsers including mobile. Only Firefox is not displaying it correctly. Why?

Chosen solution

Could be that, or Ctrl+Shift+r bypasses cached files, so perhaps Firefox was stubbornly clinging to an old version of the CSS file and now that has been resolved.

Read this answer in context 👍 1

All Replies (3)

more options

Could you open Firefox's Network Monitor, click the Domain column to sort the Google stuff together, and look at the status of the requests? I have three successful requests, as shown in the attached screenshot. (After a reload bypassing cache -- Ctrl+Shift+r.) What do you get?

Info on Network Monitor: https://developer.mozilla.org/docs/Tools/Network_Monitor

more options

The strangest thing is that as soon as I refreshed with network monitor running the font loaded properly. Clearly there is a quantum observer effect at play.

more options

Chosen Solution

Could be that, or Ctrl+Shift+r bypasses cached files, so perhaps Firefox was stubbornly clinging to an old version of the CSS file and now that has been resolved.