1820006 - Message read/unread status unpredictable with 111.0b2

Status: RESOLVED WORKSFORME

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

Description

[Wayne Mery (:wsmwk)]

With 111.0b2, random messages in a folder's messages list are shaded, as if the message had been read, but it is actually unread.

When I click on it a message, goes from shaded to bold.

I believe this is a regression in 111.0b2. I had no such issues with 111.0b1.

Comment 1

[Wayne Mery (:wsmwk)]

I also have just seen a message in a non-inbox folder with status apparently as "read", which should be unread. It did not change to unread when I clicked on it.

That message was filtered automatically from my inbox.

Comment 2

[Wayne Mery (:wsmwk)]

Seeing this with both beta and nightly

Comment 3

[Wayne Mery (:wsmwk)]

Attachment: Screen Shot 2023-03-21 at 6.53.56 PM.png

For me the behavior has changed, I think with 112.0b1, to something more consistent, less random.

I am seeing about 50% of messages filtered into folders show up as "read". Messages I have never touched and would expect to have "unread" status are marked as read. And this is further verified in a second instance of Thunderbird running daily, that has no filters using the same account.

Comment 4

[Wayne Mery (:wsmwk)]

I had expected to see other people reporting the same issue, but that has not happened. So P2->P3.
Still, this is driving me nuts - because message list and message status are my "to do" list.

Comment 5

[Thomas D. (:thomas8)]

Read/Unread is almost completely disfunctional on Daily 113.0a1 (2023-03-25) (64-bit).
Should I create a dedicated meta bug?

Bug 1820006 - Message read/unread status unpredictable with 111.0b2
Bug 1824478 - Mark messages as read (automatically/manually) does not work instantly with Unread quick filter (only after selecting another message)
Bug 1823055 - "Mark Thread as read" is disabled for thread with unread messages, pressing R has no effect.
Bug 1822622 - Cannot mark a message or thread read/unread by just clicking the icon in the Read status column
Bug 1819633 - Read & Unread icons should be different while the message is selected in message list (this affects more icons on Daily)
Bug 1824555 - Clicking any icon of a message row in message list (Read, Junk, Starred) also selects the message and should not
Bug 1816815 - Folder pane unread count and thread pane get “out of sync” - next unread won't find anything
Bug 1825226 - Mark as read has to be applied multiple times to message, undoes action itself
Bug 1825924 - Some new/unread emails not marked as such in a block of them

Comment 6

[Thomas D. (:thomas8)]

My comment 5 has the whole set of related bugs.

Comment 7

[Wayne Mery (:wsmwk)]

Only four still open:
Bug 1820006 - Message read/unread status unpredictable with 111.0b2
Bug 1824478 - Mark messages as read (automatically/manually) does not work instantly with Unread quick filter (only after selecting another message)
Bug 1816815 - Folder pane unread count and thread pane get “out of sync” - next unread won't find anything
Bug 1825924 - Some new/unread emails not marked as such in a block of them

Comment 8

[Vincent Bernat]

I often run into this issue as well. Unread messages may appear as read but after entering in the folder again, they get unread as they should. Also, moving read messages into another folder move them as unread quite often, but not always.

Comment 9

[Steve Edmonds]

Is Bug 1825265 - Message list treeview not updated for new messages until scroll/mouseover event also related to this with an underlying cause.

Comment 10

[Richard Leger]

Also noted in TB 113.0b3 with conversation enabled on Inbox folder, conversations appear folded as read (not bold) despite new unread message (bold) present in the conversation upon reception of new email. So you simply cannot see new unread email on screen (bold) and simply miss them unless you disable the conversation view (which currently you cannot easily do in Card view yet) or open each conversation in row to check if new email arrived in them... the folded conversation shall appear as unread (bold) if at least of of the message it contains is marked as unread to notify end-user that the conversation contain new unread message to prompt end-user to unfold it to access new message.

It seems to affect both Message List Table and Card views so may not directly be linked to Supernova implementation maybe something else append somewhere at some point not sure.

I do not recall such issue in 110 branch I upgraded from so it may have been somewhere in between.

Comment 11

[[:Aureliano Buendía]]

When this issue happens to me, I can read this error message in Console

NS_ERROR_NOT_AVAILABLE: PreferDisplayName: undefined - not a boolean 2 AddrBookCard.jsm:385
getPropertyAsBool resource:///modules/AddrBookCard.jsm:385
set index chrome://messenger/content/about3Pane.js:4134
invalidateRow chrome://messenger/content/tree-view.mjs:498
invalidateRange chrome://messenger/content/tree-view.mjs:478
_doInvalidateRange chrome://messenger/content/tree-selection.mjs:109
adjustSelection chrome://messenger/content/tree-selection.mjs:623
rowCountChanged chrome://messenger/content/tree-view.mjs:642
rowCountChanged chrome://messenger/content/about3Pane.js:3091

Comment 12

[gene smith]

(In reply to Richard Leger from comment #10)

Also noted in TB 113.0b3 with conversation enabled on Inbox folder, conversations appear folded as read (not bold) despite new unread message (bold) present in the conversation upon reception of new email. So you simply cannot see new unread email on screen (bold) and simply miss them unless you disable the conversation view (which currently you cannot easily do in Card view yet) or open each conversation in row to check if new email arrived in them... the folded conversation shall appear as unread (bold) if at least of of the message it contains is marked as unread to notify end-user that the conversation contain new unread message to prompt end-user to unfold it to access new message.

It seems to affect both Message List Table and Card views so may not directly be linked to Supernova implementation maybe something else append somewhere at some point not sure.

I do not recall such issue in 110 branch I upgraded from so it may have been somewhere in between.

Richard, Is the folder you are having this problem with using offline store? I don't know what "card view" even is and I don't use "conversation view" but I can duplicate a simple issue of some new messages automatically changing to unread, but only when the folder has offline store. It works fine without offline store (messages remain unread/bold until marked as read manually -- I don't use automatic marking as read).

Comment 13

[Wayne Mery (:wsmwk)]

Card view is the the new message in vertical layout.

Richard, please see comment 12

Comment 14

[Richard Leger]

(In reply to gene smith from comment #12)

Richard, Is the folder you are having this problem with using offline store?

Yes but only on Inbox and Sent items and only for 3 days worth of email.

I don't know what "card view" even is and I don't use "conversation view"

This is a new view in Thunderbird were list of message appears as cards (over two lines of text sometime - no column attibutes) rather than table record (one message per line with column attribute).

Hope that help answering your question.

Comment 15

[Wayne Mery (:wsmwk)]

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

With 111.0b2, random messages in a folder's messages list are shaded, as if the message had been read, but it is actually unread.

When I click on it a message, goes from shaded to bold.

I believe this is a regression in 111.0b2. I had no such issues with 111.0b1.

I have not been seeing this for some weeks, so I am inclined to close this bug report.

In reply to [:Aureliano Buendía] from comment #11)

When this issue happens to me, I can read this error message in Console

NS_ERROR_NOT_AVAILABLE: PreferDisplayName: undefined - not a boolean 2 AddrBookCard.jsm:385
getPropertyAsBool resource:///modules/AddrBookCard.jsm:385
set index chrome://messenger/content/about3Pane.js:4134
invalidateRow chrome://messenger/content/tree-view.mjs:498
invalidateRange chrome://messenger/content/tree-view.mjs:478
_doInvalidateRange chrome://messenger/content/tree-selection.mjs:109
adjustSelection chrome://messenger/content/tree-selection.mjs:623
rowCountChanged chrome://messenger/content/tree-view.mjs:642
rowCountChanged chrome://messenger/content/about3Pane.js:3091

That is odd. But should it be related to the situation described here?

Comment 16

[[:Aureliano Buendía]]

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

I have not been seeing this for some weeks, so I am inclined to close this bug report.

I agree. We can close this as Wfm now.

In reply to [:Aureliano Buendía] from comment #11)
That is odd. But should it be related to the situation described here?

No.