Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Some fonts not displaying correctly since recent update

  • 6 réponses
  • 6 ont ce problème
  • 1 vue
  • Dernière réponse par FuzzySponch

more options

After an update couple of weeks ago, fonts on some sites and in some emails started defaulting to the "Last Resort" system font.

The same sites and emails open correctly in Chrome. From what I can tell, the affected fonts are all stylized (bold, scaled larger than the surrounding type or emoticons).

I made sure my Firefox fonts default to Arial, Courier and Times New Roman, with "Allow pages to choose their own fonts..." selected. When I deselect this option, the fonts in the content display correctly but the site navigation fonts turn to "Last Resort." (I tried to upload screen grabs of everything, but got a spinning wheel.)

Thanks.

After an update couple of weeks ago, fonts on some sites and in some emails started defaulting to the "Last Resort" system font. The same sites and emails open correctly in Chrome. From what I can tell, the affected fonts are all stylized (bold, scaled larger than the surrounding type or emoticons). I made sure my Firefox fonts default to Arial, Courier and Times New Roman, with "Allow pages to choose their own fonts..." selected. When I deselect this option, the fonts in the content display correctly but the site navigation fonts turn to "Last Resort." (I tried to upload screen grabs of everything, but got a spinning wheel.) Thanks.

Toutes les réponses (6)

more options

This could be related with the recent switch in Firefox 52+ from Cairo to Skia for canvas/content rendering.

Firefox 52+ has changed from Cairo to Skia for canvas/content rendering.

You can modify these gfx.*.azure.backends prefs on the about:config page to revert to the old font rendering swap the skia,cairo order to cairo,skia or remove the skia and leave cairo.

  • gfx.canvas.azure.backends = direct2d1.1,cairo,skia
  • gfx.content.azure.backends = direct2d1.1,cairo,skia

You can open the about:config page via the location/address bar.

You can accept the warning and click "I'll be careful" to continue.

more options

Thanks, cor-el! I'm new to this and want to be sure I don't screw things up:

I'm on a Mac, and when I go to modify the prefs, I get a window that says "Enter string value" and the only editable text there now is skia.

So do I use the full string you have above that starts with direct2d1.1, or should I enter just cairo,skia because I'm not on Windows?

more options

On Mac you won't see direct2d1.1 (that is Windows only, so sorry about the confusion).

If you have skia,cairo or only skia on Mac then change that to cairo,skia

more options

I thought this was working, but just had another page load with only "Last Resort" loaded, and again, the same page loads fine with correct fonts in Chrome.

Sad, because I don't like Chrome.

more options

Maybe check for font issues in Font Book and also do a font test.

You can do a font test to see if you can identify corrupted font(s).

more options

The problem started happening in application menus yesterday—I couldn't read the menu bar in Photoshop—so clearly not a Firefox problem!

So today I ran FontNuke, and so far, so good.

Thanks for all your help, though—it was all good advice and now I know how to troubleshoot much better than I did before.