Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Đã lưu trữ

Google Fonts rendering problems on accented characters

cor-el đã trả lời
zehfred

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
Đính kèm ảnh chụp màn hình

Được chỉnh sửa bởi zehfred vào

Tất cả các câu trả lời (1)

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.