Open
Bug 637670
Opened 14 years ago
Updated 3 years ago
Disable "Attach this image" box in Image Properties for non-remote/non-public sources
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
NEW
People
(Reporter: rsx11m.pub, Unassigned)
Details
(Keywords: ux-error-prevention)
The Image Properties dialog allows to set the "moz-do-not-send" attribute easily by unchecking the "Attach this image to the message" checkbox. This doesn't make sense for URLs which are not remote or not publicly accessible otherwise, given that a "file://" or "mailbox://" reference isn't valid outside the scope of the local machine, and "imap://" references usually aren't accessible by anybody else. The box may be unchecked accidentally or by thinking it applies that the image will be attached as "real" attachment rather than made part of the message body.
The proposal is to have the box checked by default but disabled unless a remote and public source (ftp, http, https, others?) is provided in the "Location" field. It should be possible to nevertheless set "moz-do-not-send" in the advanced properties. Also, if the "moz-do-not-send" attribute is set already either way, or mail.compose.dont_attach_source_of_local_network_links is true, the checkbox shouldn't be disabled as the user appears to be knowing what he or she is doing.
Thus, by default, images from files or other messages are marked to be attached and the checkbox disabled to prevent accidental sending of invalid image SRCs.
Comment 1•13 years ago
|
||
+1. The way a colleague and then myself construed "Attach this image to the message" was indeed that the local file would become an attachment (ie MIME content-disposition of "attachment" rather than "inline"), so the natural tendency is to untick that box. And indeed the image still appears within the compose window, so it's not unless you check the Sent folder that you realise anything is wrong, and it's initially hard to see why such an option exists at all.
The implementation could happen in slightly different ways:
(a) When the Image Location box loses focus, if the contents start "file://" (and the other conditions in the bug descriptions are met) the "Attach this image" tickbox is ticked and greyed out;
(b) When the Image Location box loses focus, if the contents start "file://" (and the other conditions in the bug descriptions are met) the "Attach this image" tickbox is ticked and made invisible;
(c) If the Choose File button is used, and the filename isn't clearly on a shared drive (containing a string like smb4k etc), the "Attach this image" tickbox is ticked and greyed out;
(d) If the OK button is clicked and the Image Location references file:// or imap://, the actual image attach routine silently decides to include the image anyway.
Of these, I favour (b).
Severity: minor → normal
Comment 2•13 years ago
|
||
Also meant to cross-reference to Bug 536949 and Bug 561058
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•