Closed Bug 557550 Opened 14 years ago Closed 13 years ago

Double clicking a top level message in threaded view opens all child messages

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 522837

People

(Reporter: robert, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4

When I have a threaded view, and I double click a message with unfolded "children", then all messages in the whole tree opens.
This can be several hundreds sometimes, and it is really irritating.

Reproducible: Always

Steps to Reproduce:
1. Set a threaded view on a folder
2. Double click the top parent message of any message with a + in front




Only opening the message I actually clicked on, not all of its children
the top level line represents all the messages, so that's what double click should do. However, you're completely right that it does not make sense to open 100 messages in tabs. What we used to do when the user accidentally tried to open a lot of messages (e.g., if you had 100 messages selected, and pressed <enter>) is warn the user when more than a certain number of windows would be opened, controlled by the pref "mailnews.open_window_warning", which defaults to 10. In 3.0, we seem to do the following:

ignore the pref when opening a bunch of messages in tabs
if set to open messages in new windows, and you double click on a thread with 10 or more collapsed msgs, we just expand the thread. If less than 10, we open the windows.

I don't know if we've gotten rid of the warning entirely, but we do seem to be paying attention the pref. Bryan, do you think we should make tabs respect the same pref, and do you think we should not be warning?
The Fx equivalent, browser.tabs.maxOpenBeforeWarn, defaults to 15.
Generally, when a thread is collapsed and its head selected, there are a lot of
operations that act on the thread as a whole, and opening is just one of them.
To work around this behavior (along with all the other head-as-entire-thread operations) for now, set mail.operate_on_msgs_in_collapsed_threads to false in Edit -> Preferences -> Advanced -> General -> Config Editor….
Good hint Nathan! Thanks a lot! 
I would not have guessed the connection to double-click!

As a reply to David, let us remind that unless I am wrong: Double click has opened only the top message in TB2. It not about tabs only, some people use a message window. It is a real problem when so many windows flood the desktop, and must be closed by hand.

This 'open thread message', alongside with advancing to 'next in thread' on message delete, was for me the very standard way of traversing and disposing messages. This is probably another bug that 'delete' now just closes the window. Some people use Mail Tweak extension to circumvent, but this extension has its own load of malfunctions and I was forced to disable it.
is this not a duplicate of bug 522837?
(In reply to Wayne Mery (:wsmwk) from comment #6)
> is this not a duplicate of bug 522837?

I agree with you
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.