293513 - TB doesn't remember the "Expand all" setting when viewing "Threads w/ unread"

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[jim gosney]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Attached to one newsgroup server, with 11 newsgroups.  TB is used for Newsgroup
reading only -- no mail accounts.  Settings to read "threads with unread" and
"expand all".

Read new messages in a newsgroup.  Either close TB or click on the news server
so a particular group is not selected.  Wait for indication that new messages
are in a group or restart TB after sufficient time to receive new mail.  Go back
into newsgroup.  Some threads will maintain their expanded status.  Others will
not.  

After much trial and error, here is what I have determined...

If the first message at the top of the window is a new message (not part of a
thread), all subsequent threads containing new messages will be collapsed.

If the first message at the top of the window is part of a previously read
thread, that thread will be expanded.  However, all subsequent threads
containing new messages will still be collapsed.  

Window is sorted by "ordered received", "ascending", "threaded".

Reproducible: Always

Steps to Reproduce:
1.  Configure a newsgroup's read settings as "Threads with unread" and "Expand all"
2.  Receive new messages in multiple threads
3.  View messages.

Comment 1

[jim gosney]

Furter testing reveals an additional aspect.  If the first thread in the listing
consists entirely of unread messages (this is a brand new thread), then that
thread will be collapsed.  And as the others, all subsequent will be collapsed
as well.

It appears that the only time the thread will be expanded will be if it is the
FIRST thread in the window AND there is at least one "read" message in the
thread.  Otherwise, the "expand all threads" setting does not take affect.

Jim Gosney
[e-mail]

Comment 2

[Gervase Markham [:gerv]]

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/

Comment 3

[Gervase Markham [:gerv]]

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.

Comment 4

[Goran]

I can confirm that this keeps happening. It seems that TB first applies "Expand all threads" to the newsgroup and then downloads new headers to it, which remain collapsed.