Closed Bug 1666409 Opened 5 years ago Closed 5 years ago

Messages not marked as read

Categories

(Thunderbird :: Folder and Message Lists, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: kjell, Unassigned)

Details

(Whiteboard: [closeme 2021-02-01])

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

Steps to reproduce:

Since upgrading from 68 to 78 messages do not become "read" as they should. In 68, when I view a message it is automatically marked as read. This still happens sometimes in 78, but sometimes, I can view the message repeatedly both in the main 3-pane window and in a separate window (double-click message), but it stays "unread". The asterisk that marks it as new also stays in place. I am not sure, but I think it mostly (only?) happens in threads, for messages that are not the thread root.

Also, uncofirmed, it seems to mostly (only?) happen to messages that I have received because I have BCC to myself, i.e. my own outgoing messages that have been BCC:d to my inbox.

Actual results:

Messages that I view stay marked as unread and also as new (if applicable).

Expected results:

Messages that I view should be marked as read (and the "new" mark should be removed), as they did in 68 and older versions.

I am seeing the same issues. Marking "read" is inconsistent and "sticky". Most of the time I have to click on the message in the list and hit "m" to force it. I think a side issue with this is I am also getting alerts to emails that I have read and thought we marked. Apparently they were not marked and the alert can pop us many minutes or even an hour later.

kjell, are you seeing this issue when using the latest update?

Flags: needinfo?(kjell)
Whiteboard: [closeme 2021-02-01]

(In reply to Wayne Mery (:wsmwk) from comment #2)

kjell, are you seeing this issue when using the latest update?

No, it seems to be fixed. Thanks!

Flags: needinfo?(kjell)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.