Mail Window Front End
14 years ago
13 years ago


(Reporter: Joshua Bowman, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040707 Firefoxy/0.9.0+
Build Identifier: 

This isn't major, but I'd like to see a global threading switch. When on, every
folder and view except what is specifically marked not-threaded is threaded;
when off, everything acts as it does now. (Possibly including search results,
but that might be overreaching.)

Anytime I copy my profile to another machine/install or restore a backed-up
profile, all of the per-folder view options reset. Occasionally, but not really
reproducably, folders seem to randomly lose their threadedness as well, which
necessitates redoing everything.

Alternately, at least take per-folder threaded/unthreaded (which should be a
single checkmark option anyway since it's only a binary value) out of the bottom
of the view->sort by submenu, and place it at the top of the threads subfolder,
where it would be more logical.

Reproducible: Always
Steps to Reproduce:
1. Copy profile to new computer
2. Check threaded-ness of folders.
Actual Results:  
Old folders are no longer threaded.

Expected Results:  
All folders should be threaded. (That's how my setup is, anyway.)

Comment 1

14 years ago
This also happens with thunderbird-0.8.3 (Debian unstable). My thinking is that
it may be reseting the focus whenver it receives a notify from the IMAP server
that a new mail has arrived. 

I am not absolutely sure of this, because it often resets when there isn't a new
mail visible - but that may just indicate that a new message has arrived into
one of the OTHER subscribed folders, not the currently viewed one.

Please, please fix this. I find it terribly disrupting to my workflow.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.