Closed Bug 226035 Opened 21 years ago Closed 19 years ago

News reader loses "expand all threads" setting on seemingly random threads.

Categories

(MailNews Core :: Database, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: komodo, Assigned: Bienvenu)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031117
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031117

Not a new bug, it's ongoing.  Reading newsgroups, click on veiw/threads/unread.
 Now click on veiw/threads/expand all threads.
All threads will be expanded.
Leave that newsgroup, then go back again.
Seemingly random threads will be collapsed, most of them will still be expanded.
 Once it does collapse a particular thread, it seems to do that to the same
thread everytime until you mark all posts in that thread as read (and basicly
get rid of that thread on your newsreader).

Reproducible: Sometimes

Steps to Reproduce:
1.See Details.
2.
3.

Actual Results:  
Some threads are not expanded.

Expected Results:  
It should have opened the newsgroup again with *ALL* threads expanded.
I'm having the same problem.  It seems like some newsgroups work just fine, and others insist on showing threads collapsed whenever I initially try to read them.
Blocks: 236849
Summary: news reader looses "expand all threads" setting on seemingly random threads. → News reader loses "expand all threads" setting on seemingly random threads.
Product: MailNews → Core
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
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
No longer blocks: 236849
You need to log in before you can comment on or make changes to this bug.