Closed Bug 1369434 Opened 7 years ago Closed 7 years ago

Returning to a threaded folder collapses all messages

Categories

(Thunderbird :: Folder and Message Lists, defect)

52 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 223970

People

(Reporter: realgrouchy, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170518000419

Steps to reproduce:

I was able to reproduce this on a fresh install with no extensions in TB 52.1.1 on MacOS 10.12.5

1. Go to a folder (e.g. inbox)
2. Click the header of the 'thread' column to turn on threading (or twice if already threaded) until all threaded messages are *expanded*.
3. Go to another folder
4. Return to the original folder.


Actual results:

All message threads are collapsed upon returning to the original folder


Expected results:

The threads should remain expanded. Presumably if I had collapsed/expanded certain threads, it should also remember the individual threading settings.

Possibly related bugs:
Bug 223970 (regarding remembering collapse state, but is about when toggling threading itself as opposed to changing folders)
Bug 482869 (regarding remembering collapse state, but is about when changing collapse state of parent folder)
Bug 521418 (relates to behaviour when closing/reopening TB)
Bug 958815 (ditto)

- RG>
Yes, I can confirm this, also behaving like this in TB 45, so not a regression.

Magnus, how is this meant to work?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(mkmelin+mozilla)
I agree state should ideally be remembered.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mkmelin+mozilla)
Resolution: --- → DUPLICATE
The specific steps here, using the thread column as an expand/collapse toggle, are indeed broken per the dupe bug. But using * and \ to expandAll/collapseAll was fixed to be persistent across folder changes, restarts, and even for single/multiple virtual folders (all using different view code). So that should be used instead. Bug 1192838 and friends.
You need to log in before you can comment on or make changes to this bug.