193492 - Re-apply 'unread'-based views after manual Get New Messages

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[David Walser]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/2.2.2; Linux 2.4.19; X11; i586; en_US, en)
Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3b) Gecko/20030210

If you set it to only show Threads with Unread, when you first enter the app, it'll work right.

After hitting Get Msgs, it will load all the new threads with unread messages, without hiding the threads you finished reading from before.  This 
shouldn't happen, except for maybe the thread of the message you still have open.

The only way to get a correct display is double-click the newsgroup or folder you are reading in the left pane, which opens up another new window.


Reproducible: Always

Steps to Reproduce:
1. Open newsreader or e-mail
2. Read all messages
3. Hit Get Msgs

Actual Results:  
It loads all new threads with unread messages, without hiding the others that are still being displayed from before.


Expected Results:  
It should clear the message headers frame like opening the app for the first time

Comment 1

[Mike Cowperthwaite]

This behavior is intended.  The message list is not supposed to be updated 
dynamically based on read/unread.

You can get the message list to appear the way you want by simply selecting 
another folder/group and then returning to the original one -- in that case, it 
will re-filter as expected.

I'm going to tweak your bug a little, into an enhancement, because it does kind 
of makes sense that, after hitting Get New Messages, you'd like to refilter.

Comment 2

[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 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[Sebastian Brocks]

This is still not implemented, and I think it should be.
Could someone reopen it please?