Closed
Bug 187821
Opened 22 years ago
Closed 22 years ago
no unread message count next to inboxes after retrieving messages until clicking on the inbox
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 161999
People
(Reporter: fused, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030104
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030104
Didn't notice this in 1.3a, just grabbed 20030104 on a new system install and
whenever I do "Get Messages -> Get All New Messages" the unread message count
that normally appears next to the inbox doesn't show up until you click on the
inbox. It still beeps for having new messages, just doesn't display which inbox
has them.
I have 3 accounts set up if that matters, the inbox with new messages is the
third one. Haven't tried it with only one account.
Reproducible: Always
Steps to Reproduce:
1. Get Messages -> Get All Messages
2.
3.
Actual Results:
No unread message count next to inbox until you click the inbox with new messages.
Expected Results:
Bold (#) next to inbox indicating unread messages without having to click each
inbox to find out where the new messages are.
Possible Duplicate of http://bugzilla.mozilla.org/show_bug.cgi?id=187711
Slight Differences
-Snala
I don't think bug 187711 is related to this. What bug 187711 refers to is more
thoroughly covered in bug 162342 which relates to toal message counts.
The bug I reported here is in regards to there being no NEW message count
appearing on inboxes (as opposed to the total message count bugs reported
previously).
The issue discussed in this bug was a recent regression as new message count had
been working fine in pretty much every build i'd seen previously.
Comment 3•22 years ago
|
||
*** This bug has been marked as a duplicate of 161999 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•