Closed Bug 35676 Opened 24 years ago Closed 24 years ago

Folder icon should lose diamond when no new messages.

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rzach, Assigned: gayatrib)

Details

The folder icon with the green diamond indicating new messages in the folder
stays there even when the last unread message is read and the unread count goes
to zero.  It should turn into the ordinary folder icon.

Actually, it maybe should turn into the ordinary folder icon when there are no
new messages in the folder, but the master mail UI spec is still on gooey, where
I can't see it.

Linux build 2000.04.11.09
The folder icon with the green diamond should only be displayed when the 
folder contains any new messages (the most recently downloaded messages - new 
AND unread, not just unread messages).  Once the folder no longer contains any 
new messages, the folder should be the ordinary folder icon.

Note: the name of the folder would still remain bold if the folder contains 
unread messages (new or non new).
Scott, are we up to spec?
Assignee: selmer → putterman
On Linux build 2000.04.12.11:
1. Open folder
2. Click Get Msg (let's say there are new messages)
3. Click Get Msg again (no new messages)

Actual result: green diamond after (2), green diamond still there after (3)
although green diamonds on unread messages downloaded at (2) are gone.

Expected result (according to what Jennifer said): Green diamond should go away
at (3).
reassinging to gayatrib. This may be a duplicate.
Assignee: putterman → gayatrib
Summary: Folder icon should lose diamond when no unread → Folder icon should lose diamond when no new messages.
Status: NEW → ASSIGNED
Target Milestone: --- → M18
Seems like UI cleanup work, M18.
fix ready in local tree.
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Using 2000-08-22-08 M18 on Linux
Verified: Fixed
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.