State (collapsed/expanded) of threads not stored/remembered
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
People
(Reporter: redux, Unassigned)
Details
(Keywords: dupeme)
Attachments
(1 file)
Steps to reproduce:
In a folder, with threaded view enabled:
- expand or collapse a thread
- move to another folder
- return to the previous folder
Actual results:
The state (collapsed or expanded) of the thread is not stored/remembered, and seems to always revert back to the same state it was in before (which also seems arbitrary somehow...I have folders where threads are always expanded, and others where they're always collapsed...unless I'm missing something)
Expected results:
The state (collapsed or expanded) for a specific thread should be stored/remembered, so revisiting the folder at a later point has the threads in exactly the same state that I last left them at.
Is this a defect report or an enhancement request? To my knowledge and experiments with version 102, individual thread states were never persisted and didn't survive folder switching or restart. What is persisted is whether all threads in a folder are collapsed or expanded. That can be set via the "View > Threads" menu.
Updated•8 months ago
|
Description
•