1636585 - Firefox76 and later versions do not support cleartype to adjust the font. I don't know if it is a bug or the font rendering engine has been changed in version 76

Status: RESOLVED INACTIVE

(Core :: Graphics: Text, defect, P3)

Description

[liurenjie]

Attachment: Compare files.zip

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Firefox for Android

Steps to reproduce:

1. After updating firefox76, the font adjusted by claertype does not take effect
2. Reinstall and restore settings, the problem remains
3. I downloaded the nightly78 version, the problem is the same as the 76 version
   4.Compared with the display effect of the 75 version, 78 version, ie, edge, chrome browser, it is found that the 78 version and chrome display effect

Actual results:

I used ClearType to adjust the thicker font, so that it usually looks very comfortable on my laptop. But after updating the 76 version, the font is very thin because it is not affected by the ClearType adjustment, and it looks very tired

Expected results:

Hope that the 76 and later versions can be adjusted to ClearType as before, you can switch back to the original font rendering or fix this bug

Comment 1

[:Gijs (away/busy until Mar 10)]

Not a security bug that needs to stay hidden.

Comment 2

[Timothy Nikkel (:tnikkel)]

Would you by willing to use https://mozilla.github.io/mozregression/ to narrow down to find out what change caused this?

Comment 3

[Firefox Bug Husbandry Bot]

Because this bug's Severity is normal and has not been changed, and this bug's priority is -- (none,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to Timothy Nikkel (:tnikkel) from comment #2)

Would you by willing to use https://mozilla.github.io/mozregression/ to narrow down to find out what change caused this?

Lee, I was unable to contact the reporter a month ago

Comment 5

[Lee Salzman [:lsalzman]]

Going to mark this bug inactive for now. If the reporter can help us with the necessary regression info, then we can reopen it.