Closed Bug 229780 Opened 21 years ago Closed 2 years ago

[rfe] "Deleted" icon obliviates message status

Categories

(Thunderbird :: Mail Window Front End, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cross, Unassigned)

Details

Now that there are separate icons for a message that is new, read, replied to,
forwarded, and even replied-and-forwarded; I notice that when you delete a
message it shows only the one "deleted" icon.  I suspect it would be "hard" to
implement a masked X image to be mapped over the previously existing icon, but I
presume it would be easy (even if iterative and annoying to do) to make a bunch
of different delete icons.
My real complaint was not being able to see that a message had been replied to
while it was marked as deleted (using IMAP accounts, and "mark as deleted"
rather than "move to trash"); but I've since noticed that new vs. unread vs.
read also get obliviated.  This makes the problem more painful to fix, but it's
the same problem.
Anyone else agree that this is a worthy RFE?  Not critical, for sure, but I'd
certainly like to see it fixed.  And you're advertising the moving of the status
into a visual state into the icon as a feature, but if you make the status
disappear when a message is deleted, then it's less valuable IMHO.
Does noone else agree this would be a valuable enhancement?  Can we get the
extra icons (and small amount of code to use them) in before 0.8?
Would you like me to create icons?  I assume that'd be easier than a "deleted"
over-icon, tho that might be more efficient for size of the distribution...
QA Contact: front-end
Assignee: mscott → nobody

Not sure I understand what is being asked here, but we have strikeout for "mark as deleted" messages. So do we want further complexity? Or is there a real bug here?

Flags: needinfo?(mkmelin+mozilla)

Let's close. Deleted is indicated pretty well.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(mkmelin+mozilla)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.