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 ».

Learn More

Jibberish

  • 1 réponse
  • 1 a ce problème
  • 12 vues
  • Dernière réponse par cor-el

more options

I'm having trouble with reading basic copy on Firefox. I've attached a set of screen grabs, one from Firefox, one from Chrome. You can see that the written copy on the Firefox version shows as jibberish. Chrome works fine. What is the Problem. I can find nothing on this. THANK YOU!

I'm having trouble with reading basic copy on Firefox. I've attached a set of screen grabs, one from Firefox, one from Chrome. You can see that the written copy on the Firefox version shows as jibberish. Chrome works fine. What is the Problem. I can find nothing on this. THANK YOU!
Captures d’écran jointes

Toutes les réponses (1)

more options

This is usually caused by a problem with a specific font and you need to identify this font and fix this.

You can check in Font Book for font issues like corrupted and duplicate fonts. Note that you shouldn't disable "Allow pages to choose their own fonts, instead of your selections above" as this will cause issues with iconic fonts used by webpages to display small icons (you may see text labels instead of icons).

You can right-click and select "Inspect" to open the built-in Inspector with this element selected.

You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Fonts tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.

See also:

  • 1803406 - [macOS] Text rendering issues when users have multiple fonts which internally use the same name, and the OS chooses differently among them for different Firefox processes

Comment 2: This looks like an example of bug 1803406. You will probably find that it can be resolved by finding and removing duplicate fonts installed in the local ~/Library/Fonts folder, that are conflicting with standard system fonts.