If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

When a newsgroups has disappeared and is removed, the next newsgroup is not checked [index error]

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
--
minor
RESOLVED EXPIRED
15 years ago
9 years ago

People

(Reporter: Jonas Kvarnström, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
I am subscribed to some newsgroups at a private server.  Recently some groups
were removed.  The next time I started Mozilla (1.2 alpha), I got a few dialog
windows asking whether to remove group A, group C, group E, group G, and so on.
 Groups B, D, F, and H were also removed, but I got no questions about them.

There appears to be a bug in that when I remove group A, all the remaining
groups are moved to lower indices in some list or array, but the loop index is
still increased.  So group B is where group A used to be, and is not checked --
Mozilla goes on to check group C.  It is removed, D is put in its place, and E
is checked, and so on.

After this procedure I have the groups B, D, F, H, and so on.  If I double-click
the news server in the side bar (to collapse it) and double-click it again (to
expand it), I get the same question about group B and F, and so on.

This has happened on Red Hat Linux 7.3 / Mozilla 1.2 alpha and on Windows 2000 /
Mozilla (unknown version -- either 1.1 or 1.2 alpha).

Sorry about the bad summary, but I can't come up with a short way of describing
this.

Comment 1

14 years ago
Reporter: Is this still a problem with a current Mozilla build?

Comment 2

14 years ago
*** Bug 245229 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED

Updated

9 years ago
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: stephend → search
You need to log in before you can comment on or make changes to this bug.