1824478 - `Mark messages as read` (automatically/manually) does not work instantly with `Unread` quick filter (only after selecting another message)

Status: RESOLVED WORKSFORME

(Thunderbird :: Folder and Message Lists, defect, P2)

Description

[hans109h]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0

Steps to reproduce:

Select a folder, then click the "unread" button on the quick filter tool bar

Actual results:

The folder contents is filtered to unread messages only. When a message is selected it is not automatically marked as read. It becomes marked as read only when another message is selected.

Expected results:

The message should be automatically marked as read upon clicking on it.

Comment 1

[Thomas D. (:thomas8)]

Thanks Hans! Confirming for Daily 113.0a1 (2023-03-25) (64-bit), Win10.
I'll morph similar bug 1823055 to cover Mark thread read, which is a bit different.

STR

• Ensure default setting Automatically mark messages as read: Immediately on display.
• Show quick filter bar, and choose Unread subfilter.
• Click on an unread message and observe read status
  • Alternatively, click on the Read icon (I think we have another bug for that)
  • Alternatively, press M on keyboard
• Select another message

Actual result

• Message does not get marked read (automatically/manually) until you select another message

Expected result

• Message should get marked read instantly (automatically/manually)

Comment 2

[Geoff Lankow (:darktrojan)]

This is working on Daily now.

Comment 3

[hans109h]

In 112.0b5 this is still an issue, but in addition to the reported but, now if I switch to the unread quick filter, and then remove the filter, the automatic immediate marking of a message as read appears to be disabled. The only way to visibly mark the message as read is to click onto another message.

Hopefully the fix mentioned in daily addresses both of these problems.

Comment 4

[Wayne Mery (:wsmwk)]

THanks for the update.
Let us know if it improves with next week's updates.

Comment 5

[hans109h]

Still having the same result after today's update.

Comment 6

[Wayne Mery (:wsmwk)]

I can report this consistently consistently works in 113 and fails in 112. (Well, in 112 it is marked as read but the message list is not updated until I mouse or keyboard away)

Please report your results next week, when beta becomes 113.

Comment 7

[hans109h]

All good in 113 as of today for me.