Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Google Fonts rendering problems on accented characters

  • 1 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan cor-el

zehfred
zehfred
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
Keppele skermôfbyldingen

Bewurke troch zehfred op

Alle antwurden (1)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator
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.