Closed
Bug 267845
Opened 20 years ago
Closed 20 years ago
folder with enabled 'grouped by sort' forgets opened branches e.g. yesterday; on folder reopen tree is always collapsed
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: psycrow, Assigned: Bienvenu)
References
Details
(Keywords: fixed-aviary1.0)
Attachments
(1 file)
2.76 KB,
patch
|
mscott
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Opera/7.54 (Windows NT 5.1; U) [en]
Build Identifier: version 0.9 (20041103)
IMAP account
this is annoying especially in the INBOX
Reproducible: Always
Steps to Reproduce:
1.select folder
2.activate grouped by sort
3.open a tree branch
4.switch to other folder and back
Actual Results:
you should see a fully collapsed tree
Expected Results:
the tree should remember the previously opened branches
![]() |
||
Comment 1•20 years ago
|
||
Confirmed on win2k with TB 0.9
At least it remembers the last message you had open...
Comment 2•20 years ago
|
||
Threaded views don't remember individually opened threads, either.
However, if you use View|Threads|Expand All on a threaded view, that setting
is remembered. For a Grouped view, Expand All does the right thing but
doesn't stick.
Status: UNCONFIRMED → NEW
Ever confirmed: true
![]() |
||
Comment 3•20 years ago
|
||
Opened 'grouped by sort's are closed when thunderbird is restarted.
(thunderbird doesn't remember the opened state of 'grouped by sort') will this
bug cover this as well?
Comment 5•20 years ago
|
||
This makes group by sort very unfriendly. Can we get this fixed for 1.0?
Flags: blocking-aviary1.0?
![]() |
||
Comment 6•20 years ago
|
||
if you tell us to remember the last opened message we open the branch and select
the correct message making this bug not very severe. minusing for 1.0
Flags: blocking-aviary1.0? → blocking-aviary1.0-
![]() |
||
Comment 7•20 years ago
|
||
It's not about the last opened message, but the look of the tree. After using
the group sort for a while, I'm pretty much inclined to give up using it because
every time I switch to a different folder, all the unselected threads collapse.
Basically, every time you want to come back to a folder you've recently
visited, only the thread which had a message selected is kept open - all others
lose their old state.
To recap: if you have, say, grouping by date with 5 groups (today, yesterday,
last week, two weeks ago and old mail), open the first 4 of them, then select a
message at random, then switch to a different folder and back to the first one,
you'll find all folders collapsed apart from the one with the last selected
message (which is opened, and that message is selected).
I believe the open/collapsed state should be kept when leaving a folder; the
fact that the last selection is kept is excellent, but not enough IMHO. I use
to keep both today & yesterday opened (so that I can always see most recent
mails) and find it very annoying to have to reopen the folders each and every
time I return to the folder.
1.0+ please?
![]() |
Assignee | |
Comment 8•20 years ago
|
||
remember which group by date groups are expanded (and only group by date). One
caveat, this won't remember groups that are empty; e.g., if you delete all of
yesterday's messages and then open the folder the next day, we won't expand
yesterday, even if it was expanded when you deleted the last message in it...
Assignee: mscott → bienvenu
Status: NEW → ASSIGNED
![]() |
Assignee | |
Comment 9•20 years ago
|
||
Comment on attachment 166959 [details] [diff] [review]
proposed fix
just store each date group bucket as a bit in an int we write to the db...
Attachment #166959 -
Flags: superreview?(mscott)
![]() |
||
Updated•20 years ago
|
Attachment #166959 -
Flags: superreview?(mscott) → superreview+
![]() |
Assignee | |
Updated•20 years ago
|
![]() |
||
Comment 10•20 years ago
|
||
Excellent, it seems it's working perfectly (20041125).
Thank you David!
![]() |
Assignee | |
Comment 11•20 years ago
|
||
*** Bug 268979 has been marked as a duplicate of this bug. ***
![]() |
||
Comment 12•20 years ago
|
||
*** Bug 271627 has been marked as a duplicate of this bug. ***
Comment 13•9 years ago
|
||
I'm seeing this again with TB 45.
You need to log in
before you can comment on or make changes to this bug.
Description
•