Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Since updating to 68.1 I cannot tell the difference between read and unread mail

  • 2 odgovora
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od 452a4083

David Kelly
David Kelly
more options

Since the 68.1 update that was offered automatically my unread mail is only SLIGHTLY different then read mail, I have to look for the little green dot to see unread mail, I am using the new dark mode, in light mode I can see the bold font for unread, in dark mode not much difference. How can I change the color of unread mail to be different from read mail.

Since the 68.1 update that was offered automatically my unread mail is only SLIGHTLY different then read mail, I have to look for the little green dot to see unread mail, I am using the new dark mode, in light mode I can see the bold font for unread, in dark mode not much difference. How can I change the color of unread mail to be different from read mail.

Izmjenjeno od David Kelly

Svi odgovori (2)

sfhowes
sfhowes
  • Top 25 Contributor
more options

Look for articles that propose a userChrome.css file to adjust the row color or the font or color of the text. One such example:

https://www.reddit.com/r/Thunderbird/comments/9jb20e/different_row_color_for_unread_emails/

452a4083
452a4083
more options

This isn't a solution. I can no longer see the difference between read and unread messages after this recent "update". I need the program switch back to being functional out of the box which is isn't now. It appears that some developer broke the ability to see the difference between read and unread messages in order to fix some complex customization. The answer shouldn't be to require users to do some other some other complex customization to fix the program so its functional again. If it wasn't actually broken, it shouldn't have been changed.

Izmjenjeno od 452a4083