182066 - "Next unread" jumps back to a previously read message (unthreaded)

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[jonathan.courtney]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021126
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021126

When mail is ordered by date, the "next unread" button will sometimes cause the
displayed message to jump "backward" to a message previously read.  This *seems*
to be triggered by using the mouse to select a previously read message, and then
continuing with the "next unread" button.

(This is different from Bug 118508, which pertains to the case there the mail is
in threaded mode.)


Reproducible: Sometimes

Steps to Reproduce:
1. Select a mail folder with plenty of unread messages.
2. Sort them by date
3. Begin reading them by using the "next unread" button
4. At some point, use the mouse go back and reselect a previously read message.
5. Continue reading mail using the "next unread" button.

Actual Results:  
Shortly after beginning step #5, the "next unread" button will cause MailNews to
jump "backward" and display one of the recently viewed messages.  Actually the
behavior appears to be that hitting "next unread" causes it to *briefly* advance
to the next unread message (marking it as read) then immediately jump back and
display a previously read message.

Expected Results:  
Simply displayed the next unread message in date order.

I can reproduce this regularly but not consistently.

Comment 1

[Greg K.]

[e-mail], you may have noticed there are a lot of bugs open
about Next Unread. You're sure this isn't a dup of one of them?

Comment 2

[jonathan.courtney]

I've searched through all the "next unread" bugs that I could find (twice now)
but this one seems different from the rest.  As I mentioned, it seems most
similar to Bug 118508, but that one pertains to the behavior when the header
pane is in 'threaded' mode.

Comment 3

[Greg K.]

[e-mail], can you still reproduce this problem using a current
nightly build?

Comment 4

[jonathan.courtney]

No - I cannot reproduce this bug with a recent Mach-O build.

Comment 5

[Greg K.]

Resolving WFM per comment 4.