"Go -> Next -> Message" broken with threads. "N" goes to next thread
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
People
(Reporter: nobody-bugzilla.mozilla.org, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
I am using sorting with threaded enabled.
- Open first message of a thread. (Separate window, not inline)
- Use 'f' to forward to the next message (Go -> Next -> Message should be equivalent)
Actual results:
Thunderbird navigated to the first message in the next thread.
(This does not always happen for all threads, just sometimes)
Expected results:
Thunderbird should navigate to the next message in the same thread.
It used to work that way in earlier versions.
|
||
Comment 1•6 years ago
|
||
"Just sometimes" bugs are hard to fix, can you say something more specific?
|
Reporter | |
Comment 2•6 years ago
|
||
I tried it out a bit more and it seems like following:
If I double click on the first message on a thread to open it in a new window, using f consistenly gives me the first message of the next thread. (Incorrect behavior)
If I double click the second message on a thread to open it in a new window and use b to navigate back to the first message of the thread,
I can use f and will correctly get to the second message in the thread again.
|
||
Comment 3•6 years ago
|
||
Don't we use Go > Next > Unread Message or "N" if we want to stay in the thread and read the next unread message?
Works for me.
|
|
Reporter | |
Comment 4•6 years ago
|
||
I have checked again how I can reproduce this reliably. Unfortunately, contrary to my second post, it seems like opening the first message of a thread and then using f is not a sufficient precondition to make the behavior observable reliably. There seems to be some condition involved which is not obvious to me. It seems like this is most frequently happening for threads where I have not opened the second message for some time or where I have yet to open it for the first time.
Unfortunately n is not a workaround for me: There are times where I want to read an old thread again.
It definitely seems weird to me that f sometimes advances to the next message in the thread, but sometimes also advances to the next thread.
It also seems weird to me that using f once gets me to a message from which I cannot get back to the original message by using b once.
|
||
Comment 5•6 years ago
|
||
I'd be really suprised for this to have changed between 60 and 68, i.e. if it broken in 68 it may have been broken in 60.
That said, not much being reported in this area in recent years - https://mzl.la/2PcSUcG Compact is one possible cause.
|
|
||
Comment 6•4 years ago
|
||
Reporter, do you see this issue when using version 78?
Resolved per whiteboard
Description
•