News account shows incorrect number of unread messages



14 years ago
10 years ago


(Reporter: greg-mozilla-bugzilla, Assigned: Bienvenu)


Windows XP

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319

This may be a regression of bug 59681. That's why I've chosen Product: Core and
Component: MailNews: Database.

Reproducible: Sometimes

Steps to Reproduce:
1. Subscribe to on (if you can)
2. Open the drop-down for the account
3. Select the line "r.f.sourdough"
4. Read all the unread messages
5. Close the drop-down
6. Go to 2

5'. Click on Get Msgs
6'. Select the name of the account (i.e. off the line "r.f.sourdough")
7'. Go to 3
Actual Results:  
First time around:
At 2, shows (in bold) e.g. "r.f.sourdough (11)" (i.e. 11 unread messages).
After 4, shows (non-bold) "r.f.sourdough" (i.e. no unread messages).

Second and subsequent times around (i.e. after 6 or after 7'):
At 2 or 5', shows (in bold) "r.f.sourdough (11)" again.
At 3, shows (non-bold) "r.f.sourdough" (correctly).

Expected Results:  
Second and subsequent times around, should not change from (non-bold)

The bug may be restricted to occasions when there are no new messages. If a new
message has arrived and Get Msgs is clicked, the correct new total (i.e. 1) is
shown. If that message is read and the procedure continued as before and no
further messages have arrived, it goes back to the original wrong number (i.e.
11 in the example above).
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.