Closed Bug 153115 Opened 22 years ago Closed 14 years ago

Use "disabled" appearance for messages marked "deleted"

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mozilla, Unassigned)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
BuildID:    Official release 1.0

When a message has been marked for deleted, please "ghost" the message in the
list like Netscape 4.7 does.  I know you change the message's icon to have a red
line through it (indicating deletion), but if the message is still unread, it
stays bold and stays in your face.  Ghosting the message -- read or unread --
really removes it from your attention.

If you don't like ghosting, I still think messages that are marked for deletion
are too visible.  They should call less attention to themselves than the
non-deleted messages.

Reproducible: Always
Steps to Reproduce:
1. Delete an unread message.
2. Its entry in the message list stays bold which calls attention to itself.


Actual Results:  A little red line goes through the message icon, indicating
that it is marked for deletion.

Expected Results:  All messages marked for deletion should not continue to call
attention to themselves.  The little red line through the message icon is not
sufficient to remove it from your attention.
QA Contact: olgam → huang
Confirming as an RFE.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Ghost deleted messages → Use "disabled" appearance for messages marked "deleted"
happens on all platforms.
OS: Mac System 9.x → All
Hardware: Macintosh → All
Product: Browser → Seamonkey
See also bug 280003, bug 228309.

You can customize this for yourself by adding the following to your
userChrome.css file (in the profile's chrome directory):

  treechildren::-moz-tree-cell-text(imapdeleted)
  {
    color: silver !important;   /* pick color to your preference */
  }
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: huang → message-display
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.