Open Bug 223970 Opened 21 years ago Updated 2 years ago

Unthreading and rethreading expands all threads, doesn't remember collapse state

Categories

(MailNews Core :: Backend, defect)

defect

Tracking

(Not tracked)

People

(Reporter: neil, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

Steps to reproduce problem:
1. Collapse all threads
2. Toggle threads off
3. Toggle threads on

Expected results: Threads all collapsed

Actual results: Threads all expanded
I see this with 1.5 final.  There is a pretty easy work around.  If instead of
toggling threads back on in the view menu, you click on the display message by
threads column header, the threads return collapsed.
That only works for the default sort order, not for threads in any other order.
Really, does for me.  I just tried it starting from sorted by subject, junk
status, sender, read/unread, date (both ways), and priority and when I clicked
on the "click to display message threads" column header the messages threaded
nicely in all cases.
But that only works if you want the default sort order...
That's true.  If you want threaded in other than the default sort order it takes
a second trip to the view menu (View --> Threads --> Collapse All Threads).
Blocks: 236849
Product: MailNews → Core
*** Bug 231186 has been marked as a duplicate of this bug. ***
Assignee: bienvenu → nobody
QA Contact: esther → backend
Summary: Unthreading and rethreading expands all threads → Unthreading and rethreading expands all threads, doesn't remember collapse state
Product: Core → MailNews Core
Depends on: 1192838
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.