User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Build ID: 20130329030832 Steps to reproduce: Right-click on an image o, and select "Email Image..." Actual results: Thunderbird opened a new window for composing a message, and the URL of the image is pasted into the body of the message. Expected results: The actual image is attached to the email. I don't know if this is a Firefox or a Thunderbird bug, but when I select "Email Image...", I expect the image to be emailed. Emailing only the link to the image is not what the menu item implies. I could have sworn that Firefox used to work properly at one point, but I don't remember when.
I was able to reproduce this in Firefox 20.0 and it happens whether I'm using Gmail or Thunderbird as my mail client. So I think it must be a problem in Firefox or Core. I'm pretty sure this used to work - am marking it as a regression.
Perhaps a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=234678 . Has this feature always just pasted the path to the image into the email body, or did it ever actually email an image?
Honestly, I don't know if it ever worked in Firefox/Thunderbird. It works with Seamonkey, which is what I normally use. Perhaps the "fix" for this bug is to simply rename the menu item to something like "Email Image Link". However, I find it ridiculous that it can't be fixed.
Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/4.0 Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20130203 Firefox/21.0 This issue is not a regression because I was able to reproduce it on Firefox 4 (Build ID:20110318052756). Also is reproducible on Firefox 20 (Build ID:20130326150557) and on Firefox 21 (Build ID:20130203030932). In Opera and Chrome there is no "Email Image" option.
The Email image option was only implemented from Firefox 16. On all versions eversince it works the same: the URL for the image is added to the email, not the image itself. Marking this bug as an enhancement request since the current behavior is by design.
How about just changing the name of the menu item, so that it's not misleading?