70121 - next unread does not work if last message is more than one level deep in thread

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Baba Buehler]

In Mozilla 0.8 the next unread command will not advance to the next thread if
the last message in the thread is more than one level deep in the thread.  In
this case the 'n' key and Go->Next->Unread do nothing.

If the last message in a thread is only one level deep (a reply to the original)
then next unread behaves as expected and moves to the next thread.

I have seen next unread fail to function in other instances too, but this is the
only definitely repeatable case that I have found.

All my mail is in IMAP folders, if that is relevant.

Comment 1

[Jacek Piskozub]

I've seen the same behavior in newsgroup windows. Isn't it a variant of bug 64476?

I mean the "false positives" mentioned in that bug could be the messages hidden
deep in thread that one could not reach with the "n" command. One tends to
assume they are false as there are also some threads with no new postings but
showing the green "new message" icon (another bug?). Looking into a few of them
and not finding any new messages can confuse the user into believing the new
messages are "false positives".

Comment 2

[lchiang]

It does sound like a duplicate of the other bug.
Reporter - can you read the other bug to see if you agree?

Comment 3

[Baba Buehler]

no, this is not related to bug 64476, at least by my read

Comment 4

[Aleksey Nogin]

I just did some exploring using 0.8.1 on RedHat Linux 6.2 and I got a few really
weird results!

In short, if the bug under cursor is more than one level deep _and_ it is unread
(or a "false positive" - e.g. Mozilla thinks it's unread but displays it as
read), then pressing the "Next" button would not work.

I also found what appears to be a new way of creating "false positives", I'll
write about that in bug #64476

Comment 5

[Aleksey Nogin]

I just upgraded to the latest nightly of the 0.9 branch and the Next button
works completely fine!

Comment 6

[Aleksey Nogin]

Since 0.9, I never had any problems with "Next" not working, except for "false
positive" situations of bug #64476, so I believe this is fixed.
.

Comment 7

[(not reading, please use [e-mail] instead)]

since the mail performance landing, next should be working fine within a folder.

there are still some cross folder problems, and there are open bugs on those.

Comment 8

[Jacek Piskozub]

Verifying fixed as I have not seen any Next problems except the things covered
in other bugs.