1840213 - Previous/next message control should be inactive if no previous message in standalone message window

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Reader UI, defect)

Description

[David McDivitt]

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:

While stepping through messages with the previous message button at the top of the standalone message window, I scroll into the last message and click the previous message button with the message scrolled.

Actual results:

It repaints the same message again, fresh. Because of this I am not able to tell I am at the last message. If scrolled into the message, the message window changes and it looks like another message in the list, when it's just the same message re-rendered and not scrolled any longer.

Expected results:

If there is no previous message the previous message button should do nothing.

I have 115.0b4 (64-bit) now and have noticed this for all 115 versions. I skipped 111, 112, 113, and 114 because of the user interface so cannot say what version began this issue.

Comment 1

[Wayne Mery (:wsmwk)]

Steve does this reproduce for you?

Comment 2

[Steve Edmonds]

I am unable to follow these instructions, I don't see a previous message button, not sure what the stand-alone message window is (unless it is open message in new window) and not sure how you scroll into the last message in a stand-alone window.
May be a more detailed step by step set of instructions would help.

Comment 3

[David McDivitt]

Attachment: 2023-06-25 15_33_41-Fathers Day savings start NOW!! - Mozilla Thunderbird.jpg

Comment 4

[David McDivitt]

Attachment: 2023-06-25 15_34_10-Fathers Day savings start NOW!! - Mozilla Thunderbird.jpg

Comment 5

[David McDivitt]

Let us assume this is the last message in the list and I scroll a bit into the message. If I click previous on the standalone message window it will render again, fresh, as if a different message. There is no way for me to know I'm at the end of the message list. Instead, the previous button should not do anything because there is no previous message to go to. The way the application used to work is, if I click previous and it doesn't do anything I know I'm at the last message.

Comment 6

[Steve Edmonds]

I have worked out what you mean, verified it is a change from 102 and noted something else that could be improved.

To replicate,

1. open the message in a new window from the top of the message list. The message should be long enough such that you need to scroll into it.

Take note that previous message is the message ABOVE the current message in the message list as it was sorted when you open the message in a new window and next message is the message BELOW the current message in the message list as it was sorted when you open the message in a new window. Previous and next have nothing to do with date of arrival of the messages.
If the message list is resorted differently while the message window is open next and previous does not update and next and previous remain as per the sort order when the message was opened in the new window.

2. Scroll into the message
3. Click Go>Previous>message. The message reloads giving the impression it is a new message unless you took careful note of the sender, subject and date/time. TB102 does not reload the message.

Alternatively.

1. open the message in a new window from the bottom of the message list. The message should be long enough such that you need to scroll into it.
2. Scroll into the message
3. Click Go>Next>message. The message reloads giving the impression it is a new message

Comment 7

[David McDivitt]

I stayed with 110.b04 which was the last version before supernova. Because toolbar buttons did not work in the standalone message window I stayed with 110.b04. This had something to do with integrating new tool bars. Looking at he bug I submitted: 1829343, a comment says the fix was approved for beta and went out in version 114.0b4.

Comment 8

[David McDivitt]

The issue is no longer observed in version 117.0b6 (64-bit).