Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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

  • 2 Antworten
  • 1 hat dieses Problem
  • 6 Aufrufe
  • Letzte Antwort von 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.

Geändert am von David Kelly

Alle Antworten (2)

sfhowes
sfhowes
  • Top 10 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.

Geändert am von 452a4083