Bug 1840246 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36

Steps to reproduce:

With version 115.0b4 (64-bit) I click the previous button at the top of the standalone message window in the toolbar.


Actual results:

I messages by date descending and start at the bottom going up. Clicking previous in the standalone message toolbar will therefore retrieve the next message up in the list. When doing this, the next message retrieved sometimes but not always retains a bold font indicating not read. When stepping through unread messages in this manner, several may not change to show they were read. Also if I click on one of these messages to render it, it still may not change to show being read.


Expected results:

As each message appears in the standalone message window it should no longer have a bold font in the list.

This issue reliably happens each day when I fetch email and go through my list, and occurs for at least one or two messages in the list. I noticed messages do not change to unread immediately. There is a delay. When I go to a previous message using the standalone message window, it may wait for up to three seconds before changing to read in the list. This indicates the click event has terminated, and changing the message in the list is performed by another thread or service event. It is very latent and laggy in this regard. Pursuant to this issue, sometimes the servicing event is not recognizing status for a message should change. This began happening with the 115 branch. I did not install 111, 112, 113, or 114 due to user interface issues, so cannot say when this problem began occurring.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36

Steps to reproduce:

With version 115.0b4 (64-bit) I click the previous button at the top of the standalone message window in the toolbar.


Actual results:

I [sort] messages by date descending and start at the bottom going up. Clicking previous in the standalone message toolbar will therefore retrieve the next message up in the list. When doing this, the next message retrieved sometimes but not always retains a bold font indicating not read. When stepping through unread messages in this manner, several may not change to show they were read. Also if I click on one of these messages to render it, it still may not change to show being read.


Expected results:

As each message appears in the standalone message window it should no longer have a bold font in the list.

This issue reliably happens each day when I fetch email and go through my list, and occurs for at least one or two messages in the list. I noticed messages do not change to unread immediately. There is a delay. When I go to a previous message using the standalone message window, it may wait for up to three seconds before changing to read in the list. This indicates the click event has terminated, and changing the message in the list is performed by another thread or service event. It is very latent and laggy in this regard. Pursuant to this issue, sometimes the servicing event is not recognizing status for a message should change. This began happening with the 115 branch. I did not install 111, 112, 113, or 114 due to user interface issues, so cannot say when this problem began occurring.

Back to Bug 1840246 Comment 0