We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Google Fonts rendering problems on accented characters

  • 1 odpowiedź
  • 1 osoba ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od cor-el

more options

Hello,

Has anyone come across this weird bug? If you look at the attached screenshot, you'll see that every accented character gets a space after. This doesn't happen in any other browser, only Firefox. If Google Fonts is turned off (using a fallback font), the issue doesn't exist. I suppose there might be a fix?

Thanks,

Frederico

Hello, Has anyone come across this weird bug? If you look at the attached screenshot, you'll see that every accented character gets a space after. This doesn't happen in any other browser, only Firefox. If Google Fonts is turned off (using a fallback font), the issue doesn't exist. I suppose there might be a fix? Thanks, Frederico
Załączone zrzuty ekranu

Zmodyfikowany przez zehfred w dniu

Wszystkie odpowiedzi (1)

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.