Make column pickers sticky/persistent (menu should behave like a panel, i.e. stay open for selecting multiple columns until user clicks outside or ESC)
Categories
(Thunderbird :: Folder and Message Lists, enhancement)
Tracking
(thunderbird_esr6868+ fixed, thunderbird69 wontfix, thunderbird70 fixed)
People
(Reporter: tanstaafl, Assigned: alta88)
References
Details
Attachments
(1 file, 1 obsolete file)
15.75 KB,
patch
|
aleca
:
review+
jorgk-bmo
:
approval-comm-esr68+
|
Details | Diff | Splinter Review |
Comment 1•14 years ago
|
||
Comment 2•14 years ago
|
||
yes, this is really annoying.
i suppose this can be done generically in toolkit, meaning the autogenerated picker menupopup's menuitem attribute is derived from the column's attribute.
This makes the column picker menus sticky for folderpane, threadpane, and advanced search list. Requires the patch in Bug 1569791.
Comment 7•5 years ago
|
||
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/055cf553a73e
Make threadpane and folderpane column picker popups stay open for multiple selects. r=aleca
Updated•5 years ago
|
Any chance this can be uplifted so it makes it into the upcoming ESR?
Assignee | ||
Comment 10•5 years ago
|
||
the sheriff would have to decide if the required special uplift of the required m-c patch is worth it. imo, it would be nice.
Comment 11•5 years ago
|
||
Please request uplift here and quote the m-c bug. Oh, it's in comment #6.
Assignee | ||
Comment 12•5 years ago
|
||
Comment 13•5 years ago
|
||
"No risk" is funny ;-) - How many endless hours have I discussed about "no risk" or "low risk" patches :-(
Since so far we don't have a TB release branch on M-B, this would have to go straight to ESR 68 where we do have such a branch. I'll see what I can do. At the very latest, we can ship it in TB 68.2 after spending time in TB 70 beta which is released with TB 68.1.
Assignee | ||
Comment 14•5 years ago
|
||
I don't rightly know, were you ever a professional statistician? ;) Do we have loss functions for patches? Or thresholds for "low"? I'll go out on a limb and say there is 0 risk (rather than the fuzzy so low it approaches no that I meant). And as you know, 0 risk (Bayes, integrated) is theoretically legitimate. Oh, and I do exclude operational mistakes like copy/paste errors whilst transplanting, etc etc.
Slow day ;)
Comment 15•5 years ago
|
||
Comment 16•5 years ago
|
||
TB 68.0 ESR:
https://hg.mozilla.org/releases/comm-esr68/rev/ba8630fdfa1b26235bda8447386d7d787225d8b7
Comment 17•5 years ago
|
||
The side effect is that add-ons adding a column now need to add the closemenu="none"
otherwise picking their column still closes the menu.
Assignee | ||
Comment 18•5 years ago
|
||
Correct. It's not unreasonable to document that addons should do that, but it might be better to ensure it when custom columns are registered. Or maybe do in the custom element code like the original patch did. Many of the worst problems with custcol were fixed a while ago, and the biggest one remaining is that they aren't handled in View->Sort by at all unless the addon goes out of its way to do it.
Thanks for the uplifts.
Description
•