With 68.3.1, I can no longer change font colors or background colors in message body.
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: bugzilla, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
As you can see by this video showing the problem trying to change the font color:
https://www.dropbox.com/s/q08vkp647ffmllm/Font%20Color%20Bug%20%2868.3.1%29.mp4?dl=0
with TB version 68.3.1 (Mac), I can no longer change font colors or the background color of a message (other buttons like bold and such still work).
I can reproduce this problem on the Mac on two different computers, one computer running latest MacOS: 10.15.2, and the other computer running Mac OS 10.14.6.
Also historical message reply sections have lost their color codings .
I have tried to change the messaging options from the default, but none of these steps has solved this problem.
Actual results:
The font color will not change. The background will not change. The font color stays black. Historical messages have lost their color in reply sections also. All text remains black -- either trying to change font color or even reviewing previous messages.
Here's the video link showing the problem trying to change the font color:
https://www.dropbox.com/s/q08vkp647ffmllm/Font%20Color%20Bug%20%2868.3.1%29.mp4?dl=0
Expected results:
The font color should change, the background color should change as they did in the previous release.
Will there be an update that fixes this?
Thanks.
Updated•5 years ago
|
Sorry I missed the other posting.
Any idea when the bug will be fixed?
Thank you! :)
I noticed that the update to Thunderbird today, 68.4.1, still does not fix the font color problem.
Is there any timeline on this bug fix?
thanks
Comment 4•5 years ago
|
||
(In reply to bugzilla from comment #3)
I noticed that the update to Thunderbird today, 68.4.1, still does not fix the font color problem.
Is there any timeline on this bug fix?
thanks
You will have to follow bug 1605557 for that information since this bug is resolved as a duplicate of that one.
It appears to me that there is a workaround in Bug 1605557 Comment 4 for MacOS users.
Description
•