Open Bug 1729198 Opened 1 year ago Updated 2 months ago

TB ignores anti-aliasing settings of Windows 10

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 91
defect

Tracking

(Not tracked)

People

(Reporter: andreas.franz, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

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

Steps to reproduce:

I have disabled anti-aliasing of fonts systemwide on Windows 10 21H1

Actual results:

Folderpane and message list shows anti-aliased fonts.

Expected results:

No anti-aliasing as set in system-settings.

Blocks: tb91found
Duplicate of this bug: 1731646
See Also: → 1679528

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.1.2

I'm experiencing the same erroneous behavior after upgrading from v78.14.0. Folder and message list pane now show anti-aliased fonts. Message pane is not affected.

Exactly the same problem here. Fonts are jagged and blurry after updating to 91. Please fix it, I'm having a really hard time reading anti-aliased fonts.

See Also: → 1734912
Duplicate of this bug: 1738008
See Also: → 1730223
See Also: → 1733808
Status: UNCONFIRMED → NEW
Depends on: 1724057
Ever confirmed: true
See Also: 1733808

Last TB version that is fully respecting ClearType settings on Windows 10 is v68.12.1, see here:
https://limpi.hu/private/1_TB_68.12.1_ClearType_can_be_fully_disabled.png
I am still using this version because I really hate ClearType!

I tested the latest TB version (v91.10.0), it is still not respecting ClearType settings on all controls! :(
See here:
https://limpi.hu/private/2_TB_91.10.0_ClearType_still_present_on_many_controls.png
(The controls marked with red are using CearType.)

I reported this bug 2 years ago (https://bugzilla.mozilla.org/show_bug.cgi?id=1679528),
but nothing happened, it was not even confirmed! :(

Please fix this! I would like to use the latest version, but I do not want to see any ClearType texts.

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