Open
Bug 80254
Opened 23 years ago
Updated 2 months ago
Double-clicking an attachment should ALWAYS bring up dialog asking what to do (open / save), no matter what the extension is
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
NEW
People
(Reporter: Peter, Unassigned)
Details
Attachments
(1 obsolete file)
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9+) Gecko/20010509 Double-clicking an attachment should ALWAYS bring up dialogue asking what to do (open / save), no matter what the extension is. I hate it when it just opens in the browser (destroying what I had there) to show a jpg, when I prefer it to save to disk. I want to be asked.
Comment 2•23 years ago
|
||
You can always save the file after it opens in a browser window. That's not too many more clicks. Let's not make the same mistake Outlook Express made and show a virus warning for every type of attachment, including types known to be safe. I'm not opposed to having a dialog for all attachments, but we need to be careful here.
Reporter | ||
Comment 3•23 years ago
|
||
I just hate it when I absentmindedly doubleclick an attachment and it immediately starts displaying ("downloading") it to a browser window, from where I then have to take additional steps (not always obvious or even successful) to get the file on my hard drive. BTW. we are not talking about virus warning dialogues, but about being notified what that (often thoughtless) doubleclick will do ;)
Severity: normal → enhancement
Keywords: mozilla0.9.2
Reporter | ||
Comment 4•23 years ago
|
||
Currently, as an "always saver" of attachments, I am barred from the convenience of doubleclicking :( A confirmation dialogue would be much better: +-- What do you want to do with this attachment? --+ | | | < save to disk > < open > | | | +--------------------------------------------------+
Keywords: ui
Comment 5•23 years ago
|
||
Peter: how is a dialog on double-click asking "save or open" more convinient than right-clicking and selecting "save as"?
Reporter | ||
Comment 6•23 years ago
|
||
REASON 1: Because most users know only two things about windoze: 1) you can click things, and 2) if clicking doesn't bring the desired result, you can double-click things. Most users don't know about right-click submenus - that's just the sad truth. REASON 2: Because the user is left clicking 99.9% of the time. Moving to a right-click is a (admittedly slight) shift in thought patterns and therefore more of an effort (or how do you explain the rare occurrence of right-clickers?). Bringing double-click convenience to the *right-click impaired* is simply the right thing to do.
Comment 7•23 years ago
|
||
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: mozilla0.9.2 → mozilla0.9.3
Summary: Double-clicking an attachment should ALWAYS bring up dialogue asking what to do (open / save), no matter what the extension is → [RFE] Double-clicking an attachment should ALWAYS bring up dialogue asking what to do (open / save), no matter what the extension is
QA Contact: trix → stephend
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: mscott → nobody
Updated•16 years ago
|
QA Contact: stephend → message-display
Summary: [RFE] Double-clicking an attachment should ALWAYS bring up dialogue asking what to do (open / save), no matter what the extension is → Double-clicking an attachment should ALWAYS bring up dialog asking what to do (open / save), no matter what the extension is
Comment 8•15 years ago
|
||
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
Status: NEW → UNCONFIRMED
Comment 9•15 years ago
|
||
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•15 years ago
|
||
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•15 years ago
|
||
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•15 years ago
|
||
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 13•15 years ago
|
||
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 14•15 years ago
|
||
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 15•14 years ago
|
||
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
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Updated•13 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Comment 16•13 years ago
|
||
Valid RFE (eg for a hidden pref "always ask").
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows NT → All
Hardware: x86 → All
Comment hidden (spam) |
Updated•2 months ago
|
Attachment #9382996 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•