276932 - New mail icons (green arrows) should stick until I read the mail

Status: RESOLVED WONTFIX

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Heikki Toivonen (remove -bugzilla when emailing directly)]

New mail icons (green arrows) should stick until I read the mail

This may be as designed, but I have always found this annoying so I am asking if
this could be changed... AFAIK we have 3 states for messages: new, unread, read.
Read messages are indicated in normal text, unread are bolded, and new have
green arrows (in addition to being bolded).

The trouble is that as soon as I go into a folder with new messages and leave
(without even glancing at any of the new messages), all the new messages lose
that status and become simply unread.

I find myself often glancing at messages, then marking them as unread if I did
not finish them. So next time I go to a folder I have no way of knowing which of
the unread I have actually glanced at (and remarked as unread) and which I have
never looked at.

Comment 1

[Stefan Borggraefe]

Do you want Bug 231428?

Comment 2

[Heikki Toivonen (remove -bugzilla when emailing directly)]

(In reply to comment #1)
> Do you want Bug 231428?

No, that's a different thing.

Comment 3

[Jim Booth]

Heikki,

Your definition of "unread" really isn't unread, but unfinished.  I suggest you
try using MESSAGE LABELS for mail you want to come back to.  Just pressing the
numbers 1 through 5 will mark messages in 5 different colors for you to come
back to.

Suggest WONTFIX.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 6

[Karsten Düsterloh]

The green arrows mean "new since you last visited this folder", not "I never looked at this message" => WONTFIX.