Closed Bug 30891 Opened 25 years ago Closed 24 years ago

Should display correct Total number & Unread number after downloading all news headers

Categories

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

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: huang, Assigned: sspitzer)

Details

Used 03-07-08/09-M15 commercial build for all platforms: Should display correct Total number & Unread number after downloading all news headers Setup Info: Used new profile/account manager to create new news account. Steps: 1)Create new news account 2)Subscribed one newsgroup 3)After selecting that newsgroup for downloading All news headers 4)Check the status bar on the right side. 5) Actual Results: Total number & Unread number are not correct, it seemed it still retrived based on 500 msgs for total & unread numbers. Expected results: From the right side of the bottom status bar, it should display the correct downloaded total & unread numbers. Additional Info: I was using news.mozilla.org (netscape.test)for downloading all header. Additional Concern: I am not quite sure the 500 headers part is correct or not....please check for downloading 500 headers' total & unread number as well. Thanks. (I was using news (mcom.test))
QA-me
QA Contact: lchiang → huang
moving to m16.
Target Milestone: M16
Triage to M17. Please add beta2 keyword if this must make beta2. Please let me know if this must be done by M16 feature freeze.
Target Milestone: M16 → M17
Karen, does this still happen to you?
Yes. it is still occurring. By using today's 06-30-09-M17 commercial build for downloading all the headers The Total numbers & Unread numbers are still not correct. Downloading news.mozilla.org news server with the newsgroup: netscape.public.mozilla.build
I tried again for the second time and it's working!! I believe that Seth already fixed this bug along with other bug. The way I though that this problem was still occurring was because this newsgroup (netscape.public.mozilla.build) headers is too big for downloading. I am thinking that there is some other refresh problem for that (should be another or existing bug) -- this bug should be fixed now. Marking as fixed in order to marking as verified.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.