Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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?

Solução escolhida

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.

Ler esta resposta 👍 1

Todas as respostas (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

Solução escolhida

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.