Apply current view to folder and its children
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
People
(Reporter: andrixnet, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0
Steps to reproduce:
In TB115 if I use "Apply current view to folder and its children" to set columns, order, widths, sort order to other folders, apparently it does not work.
I set my preferred view for INBOX on an IMAP account.
I say "Apply current view to folder and its children" on that account (assuming it will apply to all it's folders as well). Or I apply on another IMAP account.
Actual results:
Nothing changes.
Using "Apply columns to" however seems to do the job. So what should "current view" do differently is unclear, I can see no change using it.
|
Reporter | |
Comment 1•1 year ago
•
|
||
Might be related to an older issue: bug 1735367 (?)
I remember this part of the UI having problems in this part in version 68 and some earlier.
|
||
Comment 2•26 days ago
|
||
I confirm partially this bug in v128 (on TB for Windows)
I have a huge message folder tree "work" which is a brother folder of INBOX, DRAFT, SENT.....
This message folder tree contain approx 10000 folders and 50000 msgs files.
If I try to apply the customized first "master" folder view to the full folder tree then only approx the first 500 folder views are changed.
It could be 300 or 800. Its difficult to count.
But then suddenly all folders in message tree folder (on the right) below remain unchanged.
Re-applying a couple of time "Apply columns/current view to" folder and children does not help
This is clearly a number-of-folder-limit problem.
A fix should be easy.
I can confirm the issue too as OP described. I am on MacOS 12.5.X + TB v128.2.3esr connected via IMAP but I have nowhere near that many subfolders as @ThomasSten (I only have 9 and it STILL fails), so I don't know if that's the cause?
@OP, what provider are you using out of curiosity?
|
||
Comment 4•9 days ago
|
||
This has hopefully been fixed now by bug 1872595.
Description
•