Closed Bug 1806270 Opened 1 year ago Closed 11 months ago

Bad font rendering in Firefox 109 on Windows 10

Categories

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

Firefox 109
Desktop
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1803154

People

(Reporter: pg_78, Unassigned)

References

Details

Attachments

(2 files)

Attached image fonts_109.png

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

Steps to reproduce:

  • Upgraded to Firefox 109 beta (specifically 109.0b3) on Windows 10

  • Browsed as normal

Actual results:

  • Font rendering (apparently across many fonts) is worse on 109 than 108: fonts appear "blockier". Possibly an anti-aliasing problem?

Expected results:

  • Fonts should look (at least as) good on 109 than on 108.

For comparison, the same text as rendered on v108. This is from https://www.mozilla.org/en-US/privacy/firefox/

OS: Unspecified → Windows 10
Hardware: Unspecified → Desktop

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: Text' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Graphics: Text
Product: Firefox → Core
Flags: needinfo?(jfkthame)

After searching around a bit, looks like this may be essentially the same as https://bugzilla.mozilla.org/show_bug.cgi?id=1803154

However, that bug characterises the fonts as "thicker" after the change, which isn't the whole story. Obviously there are some subjective aesthetics involved, but seems to me that the rendered fonts have not just become thicker, but have clearly degraded in quality - they are "blockier" and less even.

See Also: → 1803154

(In reply to pg_78 from comment #3)

However, that bug characterises the fonts as "thicker" after the change, which isn't the whole story. Obviously there are some subjective aesthetics involved, but seems to me that the rendered fonts have not just become thicker, but have clearly degraded in quality - they are "blockier" and less even.

Can you get back what you had in 108 when you modify Firefox's gfx.font_rendering.cleartype_params.gamma to the value of GammaLevel from Windows's registry Computer\HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY1 or other DISPLAY?

(In reply to Fanolian from comment #4)

(In reply to pg_78 from comment #3)

However, that bug characterises the fonts as "thicker" after the change, which isn't the whole story. Obviously there are some subjective aesthetics involved, but seems to me that the rendered fonts have not just become thicker, but have clearly degraded in quality - they are "blockier" and less even.

Can you get back what you had in 108 when you modify Firefox's gfx.font_rendering.cleartype_params.gamma to the value of GammaLevel from Windows's registry Computer\HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY1 or other DISPLAY?

Yes, that works!

Modified that preference to 2200 (the same value as the registry key) and now it looks the same as FF108 (and as other applications on Windows).

In case it's relevant, I have two displays, both with the exact same value for that registry key.

Severity: -- → S3
Priority: -- → P3

Unfortunately, I'm experiencing the same issue, but the tweaking of gfx.font_rendering.cleartype_params.gamma doesn't produce any visibly different results.
I believe the key might be that I have ClearType turned OFF (in Windows 10) as it gives me eye strain and headaches.
Apologies if this should have been created as a new bug. Happy to provide more details and additional screenshots if so.
Thanks.

I think we can close this as a dupe of bug 1803154, where we backed out the change from bug 1801512 that originally caused the change in rendering here.

Please follow up if that backout did not restore the previous rendering for some reason...

Status: UNCONFIRMED → RESOLVED
Closed: 11 months ago
Duplicate of bug: 1803154
Flags: needinfo?(jfkthame)
Resolution: --- → DUPLICATE

(In reply to Jonathan Kew [:jfkthame] from comment #7)

I think we can close this as a dupe of bug 1803154, where we backed out the change from bug 1801512 that originally caused the change in rendering here.

Please follow up if that backout did not restore the previous rendering for some reason...

*** This bug has been marked as a duplicate of bug 1803154 ***

Yes, the backout did indeed restore the previous rendering, so happy for this to be closed!

You need to log in before you can comment on or make changes to this bug.