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



MailNews Core
14 years ago
5 months ago


(Reporter: neil@parkwaycc.co.uk, Unassigned)


(Blocks: 1 bug, {regression})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)




14 years ago
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

Comment 1

14 years ago
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.

Comment 2

14 years ago
That only works for the default sort order, not for threads in any other order.

Comment 3

14 years ago
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.

Comment 4

14 years ago
But that only works if you want the default sort order...

Comment 5

14 years ago
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).


14 years ago
Blocks: 236849
Product: MailNews → Core

Comment 6

12 years ago
*** Bug 231186 has been marked as a duplicate of this bug. ***


10 years ago
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


9 years ago
Product: Core → MailNews Core
Duplicate of this bug: 457404


2 years ago
Depends on: 1192838


5 months ago
Duplicate of this bug: 1369434
You need to log in before you can comment on or make changes to this bug.