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

Steps to reproduce:

A. Observed new message indicator in folder pane
Clicked on folder to check new messages

B. Observed new message indicator in folder pane
Clicked on folder to check new messages

C. Observed NO new message indicator in folder pane
Clicked on folder to check new for messages

Actual results:

A. No new messages.

B. New messages had arrived, subject in bold but no new message indicator to the left.

C. New messages were indicated in the message list of the folder

Expected results:

A. B. C. If there are new messages it should be indicated in the folder pane, there should be new messages with a new message indicator to the left.

Not present in 102.12

I confirm this is a bug. I first experienced it in 114b1. I have not evaulated it with any prior releases (114b1) but it does not exist in 102.

I should have noted I a(In reply to Steve from comment #2)

I confirm this is a bug. I first experienced it in 114b1. I have not evaulated it with any prior releases (114b1) but it does not exist in 102.

I'm using a Windows 10 / x64 machine and TB 115b6.

Steve, thanks for reporting this.

There are indeed still lingering message list issues. Check for 116 beta in about 24 hours, and let us know if it still happens. (and even 116.0b1 may still have issues)

This is still happening in 116.0b1

This is still happening in 116.0b1

And it's still occurring in 116.0b2

And it's still occurring in 116.0b3

So what do you need from me to confirm this issue? I'm at a total loss as to how to go about resolving this. I've uninstalled all TB instances and reinstalled 102 as well as 116 and the issue still exists in 116 but not 102. The fact that others have reported the issue should give some credence to it. I realize it's not a show stopper especially if the majority of the users aren't experiencing it. I realize you have limited resources and are only addressing the show stoppers but I have to tell you as someone who has donated dollars I feel a little left behind. I don't expect the organization to stop and address this immediately but some help at some point would be appreciated.

Below is my original post and I was not aware there was already a post. So I'll include it again.

I have two releases of TB installed. The first is TB 102.12 installed that I use as my production mail.
I have also installed TB 115b6 to make sure I can easily migrate when TB releases 115.

They use different email accounts so there is no overlap.

In TB 102.12 when a message is marked as "read" the font changes to normal while other unread messages remain bold. It has been this way for innumerable releases.

This does not occur in 115b6 (or in 114b1 and other beta releases).
The font remains bold even after the state of the message changes to "read".
I've kept all my settings between the two versions the same so I can see the differences.
I set messages to be marked as automatically read immediately on display.

So far this seems to be the only difference of any significance (at least to me).
I have done the standard uninstall, remove all traces and reinstalled TB but can't get this feature to work.

Is there a setting or configuration change I should be making that I don't know about?
I tried comparing the config settings but got overwhelmed with the sheer number of comparisons.

Thanks.

I have no trouble with the bold changing to not-bold when a message is read, the little green dots may or may not be against an unread message or appear randomly. In 102 the new message gold sparkles stay against the new messages until the folder is changed to another folder.
I just saw a sparkle on my TBbeta folder, clicked on it, the new messages all had sparkles and were bold but no green dots, then a minute later the sparkles disappeared so I no longer know what is new without looking at the time, then a few minutes later the green dots appear against the unread messages.
openSUSE.

I just clicked on another folder with a sparkle, the new messages have no sparkles but they all have green dots.

The inbox seems the best behaved, not sure if it ever has problems, I don't know if this is an issue handling Gmail labels.

Confirming based on two reporters.
Please post your results after using 116.0b4 early this week, and also 116.0b5 which should be avilable later in the week.

116.0b4 still exhibits the behavior. However, the message indicator turns off. That is, when the message arrives the indicator is green and when the message is highlighted the indicator goes off but all of the text (Subject, Date, Correspondents etc.) remains highlighted in bold and does not go to normal.

Continued issue in 116.0b5

Continued issue in 116.0b5

Continued issue in 116.0b6(In reply to Steve from comment #13)

Continued issue in 116.0b5

I meant Continued issue in 116.0b6

Continued issue in 116.0b7

And 117b1

Confirm also in 117.0b1 on openSUSE, switching back to 102.

There may be a slight difference of experiences here...

(In reply to Steve from comment #8)

This does not occur in 115b6 (or in 114b1 and other beta releases).

But I believe Steve Edmonds' comment 0 is with 115 beta

It will be great if you can both find a regression range using https://mozilla.github.io/mozregression/quickstart.html
I would start with nightly build date range of 2023-05-20 and 2023-07-04

From comment 2 it seems possibly from 114b1. I selected 115 because I was a bit frustrated at that point but fairly sure it was happening in 114.

See bug 1840246
On Windows 10 /x64 I've narrowed it down to between release 110b4 (no problem) and 111b1 Build 1 (problem appeared).

117.0b2 problem continues

(In reply to Steve X from comment #20)

See bug 1840246
On Windows 10 /x64 I've narrowed it down to between release 110b4 (no problem) and 111b1 Build 1 (problem appeared).

The time frame Steve X gives in comment 20 110b4 to 111b1 matches to the merge of supernova code into nightly builds, which then became 111b1, i..e the very start of supernova.

If Steve Edmonds was using betas prior to 114.0b1 and did not experience the problem:

• then it is not a match to Steve X
• The regression range Steve E needs to check with mozregression is 114 and 115 nightly builds between 2023-04-01 and 2023-06-02
• alternatively, if the issue occurred first in 114.0b2 or later, then examine the beta checkins list https://hg.mozilla.org/releases/comm-beta/pushloghtml?startdate=2023-05-09+8%3A00%3A00&enddate=2023-06-01+10%3A00%3A00

102 has previously had 2 child processes, 110 onwards only seems to have 1. 102.15.0 now only seems to start 1 child process.
I think I am starting to see this bug in 102.15.0. It can often take some time to confirm this due to the randomness.

I am definitely seeing this issue in 102.15.0 and not in 102.13.0.
I have a suspicion this is to do with push notifications not working consistently in folders (labels) on gmail IMAP connections, Account Settings > Server Settings > Allow immediate server notifications when new messages arrive. I have checked this and consistently 102.13.0 has receipt notification a few seconds after sending a new email. The results are variable in 102.15.0, sometimes it can be 15-30 seconds, other times not at all and new mail does not show until I click on the folder.

I don't know if the number of folders has any effect. What happens if there is not enough time to check all folders within the time set in Account Settings > Server Settings > Check for new messages every ?? minutes