Closed Bug 303651 Opened 19 years ago Closed 18 years ago

Message window behaviour: open new messages in new window and existing window do the same thing

Categories

(Thunderbird :: Preferences, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: hobbsee, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

In thunderbird:
Tools, options, general

Message window behaviour: 
open new messages:
in new window
in existing window

These options seem to do the same thing - when you double click on a message
header, it will open in a new window, no matter which option is selected.

Reproducible: Always

Steps to Reproduce:
1.tools, options, general, select open new messages in existing window
2.double click on message header, it opens in new message window.
3.tools, options, general, select open new messages in new message window
4.double click on message header, it opens in new message window.
Actual Results:  
The message opens in a new window, whether the message is set to open in a new
message window, or the existing message window.

Expected Results:  
If the option of "open new messages in existing message window" is selected,
then double clicking a message should open it in the preview pane, just like a
single click would

using extensions:
minimise to tray
autocopy
allow empty subject
no new window on double click
If no message window (that is, a standalone message window) is open, then one 
has to be opened.  The preference's UI clearly states "message window"; the 
message pane is not a window.  If there *is* a standalone message window already 
open, that preference is followed.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
(In reply to comment #1)
> If no message window (that is, a standalone message window) is open, then one 
> has to be opened.  The preference's UI clearly states "message window"; the 
> message pane is not a window.  If there *is* a standalone message window already 
> open, that preference is followed.

There is at least one report that this preference is not followed, to keep a single standalone message window
news://news.mozilla.org:119/1fOdnT-q1Ms2RrHZnZ2dnUVZ_vednZ2d@mozilla.org

It wasn't working for me on trunk. It opened a new standalone message window for every message double clicked. 

I changed it from "existing window" to "new window" and back to "existing window" and then it worked - keeping just one standalone message window. 
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
... my trunk version being version 3 alpha 1 (20060330)
(In reply to comment #2)
> (In reply to comment #1)
> > If no message window (that is, a standalone message window) is open, then one 
> > has to be opened.  The preference's UI clearly states "message window"; the 
> > message pane is not a window.  If there *is* a standalone message window already 
> > open, that preference is followed.
> 
> There is at least one report that this preference is not followed, to keep a
> single standalone message window
> news://news.mozilla.org:119/1fOdnT-q1Ms2RrHZnZ2dnUVZ_vednZ2d@mozilla.org

That would be mine. It works for me, I just didn't understand that "Current message window" isn't the same window where preview-panel is.

But it doesn't remove the fact that Thunderbird doesn't have possibility to entirely disable this "message window" for appearing. I don't like it appearing, unless I start to actually write new message (in new message window).
I tried this on 1.5.0.4rc2 Thunderbird for Mac, as well as a previous 1.5.0.2 version, and I found that toggling the "new message" window option does not make a difference. It always opens it in the current pane, unless you double click on it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.