349313 - Manually marking Mail as Junk cause another Mail to be displayed

Status: RESOLVED DUPLICATE of bug 209748

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Oliver Kluge]

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.0.6) Gecko/20060730 SeaMonkey/1.0.4
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.0.6) Gecko/20060730 SeaMonkey/1.0.4

If you manually mark mail as being Junk in the Inbox, that is not currently highlighted (selected), the selection moves one down, i.e. some other mail actually gets displayed that you did not want to get read, with HTML that could lead to web bugs being loaded, thus more spam is produced.


Reproducible: Always

Steps to Reproduce:
1.Mark any mail as Junk in the Inbox, that is not currently selected
2.Watch what the selection (highlight) does: it moves down
3.

Actual Results:  
Mail is being displayed that the user did not intend to be displayed, since the user did not make any new selection.

Expected Results:  
Selection should remain unchanged.

One more example to make my point clearer:

Say you have three spam mails in the Inbox that for some reasons have not been filtered. You have opened any e-mail with legitimate content. You directly click on the trash icon of the first of the mails whose header directly indicated they are spam. So the first spam mail gets transported to junk (and erroneously being marked as being read, but I filed another bug for that), and now the selection moves one down - eventually leading to spam being displayed.

The selection should in my view not change unless the user instructs the Mail program to do so.

Comment 1

[Mike Cowperthwaite]

Already fixed for TB 2.0 and SM 1.1.  (Your other bug was also fixed for SM 1.1, too.)

From  <http://www.mozilla.org/quality/bug-writing-guidelines.html>:
> Before you enter your bug, you need to make sure it has not been previously 
> reported. 
> Next, be sure that you've reproduced your bug using a build released within
> the past three days. Our development process moves at lightning speed, and
> the bug you've found may already have been fixed.

*** This bug has been marked as a duplicate of 209748 ***