142966 - Suggestion to add "Open with..." to attachment's context menu

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Hakon]

The context menu in the list of attachments contains the item "Open",
which when clicked on opens the common open/save dialogue.
But this seems a little redundant, since there is already the item "Save as..."
in the context menu.

I suggest that instead the context menu would contain both "Open" and "Open
with...".

"Open" would open the file immediately with the associated viewer, which would
save a few clicks. If there is none associated, this menu item would be dimmed.

"Open with..." would of course open the dialogue where you could choose which
application to view the file with.

Comment 1

[jglick]

>The context menu in the list of attachments contains the item "Open",
>which when clicked on opens the common open/save dialogue.

It seems to depend on the file type. If its a .doc, you get the Open/Save 
dialog. If its a gif/jpeg or html file, it is opened in the browser 
automatically.

I think your idea is good. I seem to remember something about security issues 
though and opening certain types of attachments automatically. Maybe that is 
only a concern when users double an attachment though? 

Comment 2

[R.K.Aa.]

*** Bug 159000 has been marked as a duplicate of this bug. ***

Comment 3

[Miha Psenica]

I agree, 'Open With...' would be very helpful, at least for us advanced users.
Isn't Mozilla all about having control?!

Comment 4

[Robert Kaiser]

MASS-CHANGE:
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 5

[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