Closed Bug 122908 Opened 20 years ago Closed 11 years ago

Collapsed threads that have labeled messages should be underlined

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kazhik, Unassigned)

References

(Blocks 1 open bug)

Details

Collapsed threads that have labeled messages should be underlined
or colored, as collapsed threads that have unread messages.
QA Contact: esther → laurel
Using feb 01 commercial build: 
1.  A collapsed thread which has a labeled reply (one or more) is indeed
underlined if the thread has unread items.
2.  A collapsed thread which has a labeled topic message is indeed underlined
and colored if there is an unread item in the thread.

I'm not sure I understand what you're requesting...

Do you want a collapsed thread which has one or more labeled components but has
no unread items to show underlining or color (what color would you show if there
are different labels in the thread?) ?

I think reporter wanted to visually distinguish threads containing labeled
messges form another threads, even if all messages in those threads are read
already.

For example I often label some mails from Bugzilla and respond to them later
(when I have more time). When I later rerturn to my folder with bugzilla
messages, It is quite difficult to quickly determine what messages I labeled,
when I am in threaded view.

My opinion is to open (expand) threads containg labeled messages so those
messages are visible when you scroll through the list. But concrete solution
needs some discussion...
> I think reporter wanted to visually distinguish threads containing labeled
> messges form another threads, even if all messages in those threads are read
> already.

Right.

1. Collapsed threads that have unread messages are underlined.
   Now available.
2. Collapsed threads that have flagged messages are flagged in flag column.
   Use different bitmap from normal flag: ex. small or pale colored flag.
3. Collapsed threads that have labeled messages are colored.
 3-1. The thread contains one kind of labeled messages:
      use same but pale color.
 3-2. The thread contains more than two kind of labeled messages: 
      (a) consider strength of labels.
      (b) used 6th coloer
      (c) rainbow colored :-)
      ... need more discussion
See also Bug 131164
Change
 Platform/OS: all
 Severity: enhancement
3-2. (d) Use mixture of appearing colors with corresponding percentages ;-)
Blocks: 236849
Product: Browser → Seamonkey
OS: Windows 2000 → All
Hardware: PC → All
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: laurel → 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: 11 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.