Closed Bug 1861892 Opened 2 years ago Closed 2 years ago

New folder - sort always starts Threaded

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jeff, Unassigned)

Details

Steps to reproduce:

  1. Create a new folder
  2. Move some messages to it

Actual results:

Sort always starts as THREADED - when everywhere else I have selected UNTHREADED

Expected results:

Sort should start as UNTHREADED

Do you have the hidden preference mail.default_view_flags mailnews.default_view_flags set to 0?
If not, you will have threading enabled when creating a new folder.

Flags: needinfo?(jeff)

(In reply to Wayne Mery (:wsmwk) from comment #1)

Do you have the hidden preference mail.default_view_flags set to 0?
If not, you will have threading enabled when creating a new folder.

No - I have NEVER opted in to the new Threaded views - can't stand it.

Flags: needinfo?(jeff)

I feel like there is a misunderstanding. I'm not asking whether you like it.

You wrote "Expected results: Sort should start as UNTHREADED". That is understood.

If you are a new user, or not a new user but have created a new profile, the default is now Threaded, and there is no opt in - mail.default_view_flags mailnews.default_view_flags set to 1, which means new folders default to threaded. To reverse that change, you set mail.default_view_flags mailnews.default_view_flags to 0.

Does changing that preference to 0 work?
Or, is there some other aspect of "Sort" or threading that is a problem?

Component: Untriaged → Folder and Message Lists
Flags: needinfo?(jeff)

(In reply to Wayne Mery (:wsmwk) from comment #3)

I feel like there is a misunderstanding. I'm not asking whether you like it.

You wrote "Expected results: Sort should start as UNTHREADED". That is understood.

If you are a new user, or not a new user but have created a new profile, the default is now Threaded, and there is no opt in - mail.default_view_flags set to 1, which means new folders default to threaded. To reverse that change, you set mail.default_view_flag to 0.

Does changing that preference to 0 work?
Or, is there some other aspect of "Sort" or threading that is a problem?

I've created this (as Number) and assigned 0, restarted TB - no luck, still threaded.

Google suggests mailnews.default_view_flags, created (as Number), assigned 0, restarted, created folder, moved messages into folder - no luck, still threaded.

Flags: needinfo?(jeff)

So I did a search in Config for default_view_flags and saw that there were two mailnews.default_view_flags

  • I deleted my manually added one, and set the system one to '0'.
  • I restarted Thunderbird
  • I created a new folder and moved messages into it
  • The Sort is NOT Threaded

Conclusion: search in Config for default_view_flags, set the value to 0 - works to change the default view to unthreaded. 😄

Next question: Can I edit the TB config to remove all of the manual overrides so that this new default takes effect for my 200+ folders...

(In reply to jeff from comment #5)

Conclusion: search in Config for default_view_flags, set the value to 0 - works to change the default view to unthreaded. 😄

Yes, the preference is called mailnews.default_view_flags. By the way, there is mailnews.default_news_view_flags for Usenet folders as well.

Next question: Can I edit the TB config to remove all of the manual overrides so that this new default takes effect for my 200+ folders...

Just click on the icon with the "Select columns to display" tooltip (to the right of the other column headers) and select "Apply current view to ..."

Just click on the icon with the "Select columns to display" tooltip (to the right of the other column headers) and select "Apply current view to ..."

Indeed, you can even do "Apply current view to ..." to a top level account.

Sorry for the error, it is mailnews.default_view_flags

I think this can be closed as WFM.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.