6.0.0-beta1
7/6/25

[#8222] "Show page with first unread message" only works the first time
Summary "Show page with first unread message" only works the first time
Queue IMP
Queue Version 4.3.4
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester eduardo (at) kalinowski (dot) com (dot) br
Created 04/27/2009 (5914 days ago)
Due
Updated 05/15/2009 (5896 days ago)
Assigned
Resolved 04/29/2009 (5912 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/15/2009 09:28:29 PM Michael Slusarz Comment #4 Reply to this comment
Rejecting.  This doesn't make much sense from a UI standpoint so it 
shouldn't be an option to the user.
04/29/2009 03:36:39 PM eduardo (at) kalinowski (dot) com (dot) br Comment #3 Reply to this comment
Then please change this to a "feature request" to have an option of 
having that behavior. If there are several unread messages in several 
pages, I think it would be more useful to go to a page with unread 
messages, not to a page I've already seen.
04/29/2009 03:27:51 PM Jan Schneider Comment #2
State ⇒ Not A Bug
Reply to this comment
This is the expected behavior, so that you get back to the same page 
if you navigate between folders.
04/27/2009 08:52:25 PM eduardo (at) kalinowski (dot) com (dot) br Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ "Show page with first unread message" only works the first time
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
I have selected the option to display the "page with the first unread 
message" in folder view. The first time I open a folder, this works. 
However, in subsequent visits to the folder, that same page shown in 
the first time is displayed, even if there are no more unread messages 
in that page.



When browsing folders with a lot of messages, sorted by thread, new 
messages can be spread out in several pages, and looking for them 
manually is very hard. That option of displaying the page with the 
first unread message is very useful.



It used to work well in the 4.1 version, but since somewhere around 
4.2 it has stopped working.

Saved Queries