120342 - Collapsing folder-tree clears message-list if in sub-folder

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Neil Pilgrim]

linux build 2002011108

To reproduce:
1) select a mail sub-folder (-> message-list updated to be that folder)
2) collapse parent folder, using twisty

Expected behaviour:
Message-list unchanged, no folders selected in folder-list.

Current behaviour:
Message-list clears

This is an annoying bug for filing messages via DnD, where closing a parent
folder - to get more space for expanding other folder-trees. This appears to be
a NS4.7 feature not in moz, though the NS4 behaviour is not ideal since on
closing the parent the parent is highlighted, so the message-list does not match
the highlighted folder (ie. current moz behaviour is better in that respect)

Comment 1

[Vadim Berezniker]

Well. Mozilla now does the same thing.
Collapsing a parent while having a child select, changes the selection to the forum.

I agree that it would be nice if you could collapse a folder w/o losing the
selection. 

Mozilla could indicate that your current selected folder is not visisble by
highlighting the parent in a distinct color but that would probably be another bug.

Confirming on linux trunk #2002032919

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420