[advanced search] Search Messages resets the sort order / sort column. column choices and order should persist
Categories
(Thunderbird :: Search, defect)
Tracking
(blocking-thunderbird3.1 -, thunderbird_esr6868+ fixed, thunderbird69 fixed, thunderbird70 fixed)
People
(Reporter: sspitzer, Assigned: alta88)
References
()
Details
Attachments
(2 files, 2 obsolete files)
33.58 KB,
patch
|
alta88
:
review+
aceman
:
review+
jorgk-bmo
:
approval-comm-esr68+
|
Details | Diff | Splinter Review |
31.90 KB,
patch
|
jorgk-bmo
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
Reporter | ||
Comment 1•19 years ago
|
||
Comment 2•18 years ago
|
||
Updated•18 years ago
|
Comment 4•16 years ago
|
||
Comment 5•16 years ago
|
||
Comment 6•16 years ago
|
||
Comment 7•16 years ago
|
||
Comment 8•16 years ago
|
||
Updated•15 years ago
|
Comment 11•15 years ago
|
||
Updated•14 years ago
|
Comment 14•14 years ago
|
||
Comment 16•13 years ago
|
||
Comment 17•13 years ago
|
||
Updated•10 years ago
|
Comment 18•6 years ago
|
||
possible to do here what squib did in bug 528044 ?
Assignee | ||
Comment 23•5 years ago
|
||
- share threadTree in an inc file for search access to all columns.
- make user's column selection and sort order persistent for search.
- remove some dead attributes from threadTree.
this depends on Bug 545906 changes else it won't apply.
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Comment 28•5 years ago
|
||
Assignee | ||
Comment 29•5 years ago
|
||
Comment 30•5 years ago
|
||
Assignee | ||
Comment 31•5 years ago
|
||
ah right, removed dupe strings; there's some other bug about it. anyway, if aceman has any substantive comments, i'll do them in a followup. one r+ is enough here.
Comment 32•5 years ago
|
||
Assignee | ||
Comment 33•5 years ago
|
||
(In reply to :aceman from comment #32)
Comment on attachment 9082894 [details] [diff] [review]
searchCols.patchReview of attachment 9082894 [details] [diff] [review]:
Thanks, this looks good to me. I thought that the column selection is now
shared between the main thread pane and the search window, but that is not
the case.
No, and it shouldn't be. In fact, it can't be since in threadpane the column selection is folder specific and stored in the .msf db.
::: mail/base/content/SearchDialog.js
@@ -240,5 @@
- gFolderDisplay.setColumnStates({
- subjectCol: { visible: true },
- correspondentCol: { visible: Services.prefs.getBoolPref("mail.threadpane.use_correspondents") },
- senderCol: { visible: !Services.prefs.getBoolPref("mail.threadpane.use_correspondents") },
Is this solved in the Search dialog with some other code now? Or is it done
by the automatic restoration of columns and this code was only needed when
we always initialized the search columns from scratch?
The search dialog column selection and sort is restored based on persisted dom attributes (used to be xulStore.json but now is in xulStore/data.mdb), since there's no backing db, as there is for folders in threadpane.
Btw, someone should do the same dedupe for the addressbook list and search, along with making those colpickers sticky.
Comment 34•5 years ago
|
||
Something we should backport? Looks like an old bug.
Comment 35•5 years ago
|
||
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/f6e91a51bd51
Persist search dialog list column choice and sort column/order; share threadTree between 3pane and search. r=aceman
Updated•5 years ago
|
Comment 36•5 years ago
|
||
Bug 545906 also got the ESR approval. And it makes sense to backport. The string changes are only removals, so no problem.
Comment 37•5 years ago
|
||
Comment 38•5 years ago
|
||
TB 69 beta 3:
https://hg.mozilla.org/releases/comm-beta/rev/d16312466cccd7771275d32ee45d88474f7f6c83
Updated•5 years ago
|
Comment 40•5 years ago
|
||
Updated•5 years ago
|
Comment 41•5 years ago
|
||
TB 68.0 ESR:
https://hg.mozilla.org/releases/comm-esr68/rev/38fb021b6113d7876673d8aeaad54c2c31b3a67b
Comment 42•5 years ago
|
||
Also working in TB 68 ESR.
Comment 43•4 years ago
|
||
Today is 09-Feb-2021 and I'm running the latest TB 78.7.1 (standard user release). The SORT issue has either regressed or still persists -- the sort order still changes for every search within the current session and reverts to a default.
If I sort by something (say, "DATE ^"), then close the search panel, that something becomes the default for the next session. When I open a new search, the first sort will be by this default, and likewise all subsequent sorts within the session -- even if I re-sort by something else (say, "DATE v"). If I close & reopen, the most recent sort criteria is the new default for the next session, and all subsequent searches in the new session will initially sort by this default.
So then...
If I am in the search panel already, any SORT will work. But any re-SEARCH will revert to the most recent DEFAULT, as set in the above examples.
I expect and want the SORT -- in the current SEARCH session -- to persist as I most recently set it in this (current) session, such that a re-search or new search will come up sorted in that order. Most likely, I'm trying to find and isolate something, and having to re-change the SORT parameter or re-flip the sort order is a major distraction.
Description
•