109821 - Need File: Open <Folder/Newsgroup>

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Ben Ruppel]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.5+)
Gecko/20011112
BuildID:    20011112

When going through newsgroups/mail, it is nice sometimes to be able to
check/reference your mail/newsgroups.  In order to do this, I can double-click
or right click > Open in New Mail Window on the other folder.  However, doing
this looses focus on my current folder so I loose my place in the current
folder.  In Navigator I could at least hit the newsgroup button on the
quicklaunch toolbar to get a second mail/news window open.  Mailnews should have
a File > New Mail Window entry or something.

Reproducible: Always
Steps to Reproduce:
1.go to a newsgroup and go through some messages
2.realize that you would like to reference something in your inbox
3.try to figure out how to go to your inbox without loosing your place in your
newsgroup.

Actual Results:  Well, one solution would be to right click on an alternate
folder, but this changes your focus to another folder (this is another bug). 
You can right click on your current folder, open it in another window, and
change the folder of the new window, but this isn't very obvious.

Expected Results:  I should be able to get a new mail window in an easier way.

Comment 1

[Olga]

Currently we have 'Open in New Mail Window' context menu item for each Folder.
I've just played with opening new mail windows by using this menu item or
double-clicking on any folder. I see described inconvenience. 

Comment 2

[Olga]

Updating multiple bugs. This is a valid UI issue. Would be nice to have it fixed
if time allows.

Comment 3

[scottputterman]

We have a couple of bugs on making right clicking and double clicking not
changing the focus.  However, I think the menu item is a good idea.  reassiging
to ssu.

Comment 4

[jglick]

The menu item, "Open in New Mail Window" already exists and works. 

Right clicking/dislaying a context menu should Not select the item and change 
the user's focus is bug 30560.

Author, does that take care of your issues?

Comment 5

[Ben Ruppel]

Yes yes, you are right.  If bug 30560 were fixed my issues would be solved. 
It's still a bit undiscoverable IMHO, but I guess adding a New > Mail Window
menuitem would be considered not worth the clutter.  

Comment 6

[jglick]

File menu currently has "Open Message".

What if, message has focus, File: Open Message", but if a Folder/Newsgroup has 
focus, it was "File: Open <Folder/Newsgroup>"?  Would need to be disabled if 
Account had focus.

Comment 7

[Ben Ruppel]

jglick: Your idea is nice and it would be consistent.  The only problem is that
I would still have to click on a folder first and then go to the File menu, when
I could just right click on the folder in the first place.  So... while it makes
it more discoverable, it's not a very useful way of opening a new mail window.  

Would it be so bad to put the item File>New>Mail Window in?  We have such items
as New>Blank Page to Edit and New>Address Card.  If it is a problem, perhaps
this item would only show up in the mail window file menu.

Comment 8

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420