270506 - Cross-folder navigation for next unread message doesn't go to next folder if any unread mails exist in current folder - wraps to top

Status: NEW

(Thunderbird :: Folder and Message Lists, defect)

Description

[salzrat]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: 

There is a quite annoying behavior in "Go to next unread message" (n-key).  I
find this useful because "unread messages" constitute a sort of "todo-list" for me. 

Reproducible: Always
Steps to Reproduce:
1. This bug is only visible for people who have "Mark as read automatically
after ... seconds" to a very high value.
2. if there is more than 1 unread message in a folder, press n repeatedly
Actual Results:  
TB will wrap around to the first unread message in the same folder 

Expected Results:  
gone to the next folder containing an unread message

There is a very simple fix:

In the file chrome\mail\content\messenger\msgViewNavigation.js, in function:
function ScrollToMessage(type, wrap, selectMessage)
change the line
gDBView.viewNavigate(type, resultId, resultIndex, threadIndex, true /* wrap */ );
to
gDBView.viewNavigate(type, resultId, resultIndex, threadIndex, /* true */ wrap );

Then, in file chrome\mail\content\messenger\mail3PaneWindowCommands.js, in function
function MsgNextUnreadMessage()
change the line
GoNextMessage(nsMsgNavigationType.nextUnreadMessage, true);
to
GoNextMessage(nsMsgNavigationType.nextUnreadMessage, false);

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[salzrat]

I think this is still a bug in the latest version, and I have listed a way how
to fix it. I can't do more.

Comment 3

[Mike Cowperthwaite]

*** Bug 320364 has been marked as a duplicate of this bug. ***

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)

Comment 5

[Mike Cowperthwaite]

This behavior not only still exists, it will be more visible as people take advantage of the patch from bug 297534.

Whether someone deems it worth fixing is another question.

Comment 6

[Wayne Mery (:wsmwk)]

I'm not sure there's much point in wrapping within the folder from the last unread to the first unread message in the sort.

Comment 7

[Bryan Clark (DevTools PM) [:clarkbw]]

I can see how this makes sense.  Thunderbird doesn't have an idea of the messages you've looked at, but haven't marked read (because you jumped to the next message before the unread message was marked read)  so it has no way of determining this situation correctly.  I feel like the fix might be a bit complicated.  While annoying I can't see this getting much traction unless someone has a working patch.

Comment 8

[Michael A. Pasek]

The current behavior -- moving to next unread message in the same folder -- would be what I would expect.  That is not to say that the reporter's desired method of operation isn't also valid, but think it's more of an RFE than a bug, with possible exception noted below (dependent on design intent).  

Should the behavior be controlled by "mailnews.nav_crosses_folders ?  If so, the default is "1" (ask), so when on the last unread message in a folder, should it prompt whether or not you want to go to the next folder ?  "No" would leave you in the same folder, "Yes" would jump to next.  Proper operation for the case where the user did NOT want to be prompted, but DID want the behavior noted in the description, would require another setting for 'mailnews.nav_crosses_folders' if the design intent of the current implementation was to stay in the same folder.