![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Since TB78 there is no way to disable ClearType in message body
I just tried 78.11.0 version and the problem is still present. See attached 2 pictures!
Enabling/disabling HW acceleration does not help and also other configuration setting changes do not help. They work only in 68. In TB78 message body text is always rendered with ClearType, no matter what... :(
I reported this bug about a half year go: https://bugzilla.mozilla.org/show_bug.cgi?id=1679528 Nobody even confirmed it...
So I am still using 68.12.1 because of this.
Could you please fix this bug? Enabling/disabling ClearType seems to work everywhere in TB78 except the most important place: the message body...
所有回覆 (2)
I will asked the truly obvious question. Have you tried updating your video driver software in the operating system.
My guess is Mozilla have removed the basic option to disable clear type.
These bugs were in the post 68 timeframe https://bugzilla.mozilla.org/show_bug.cgi?id=1569174 https://bugzilla.mozilla.org/show_bug.cgi?id=1565158
there are probably more, I just had a quick look at what has been happening. Getting a compatible video driver would probably be much better than trying to fight the tide of clear type bit on the operating system and your applications.
Everything is updated. And I tried everything else too.
And as I wrote: This bug is only present in TB78 and it is not present in TB68. And in TB78 only the massage compose/display window (message body) is affected.
When I re-install TB68 the problem solves instantly! (In TB68 I can enable/disable ClearType properly with the HW acceleartion setting, in TB78 too, except only the message body wich also is the most important part for me...)
So I think it is clear, that the bug is related to TB78's message compose/display component(s) only. And it is independent from my software environment. TB68 works perfectly on it.
Developers should investigate this! I reported this problem detailed here: https://bugzilla.mozilla.org/show_bug.cgi?id=1679528 I don't know why nobody is inspecting it...
Anyway I continue to use TB68 then! But I still hope you will fix this someday...
Thx