Image right-click menu in HTML mail should have "Properties" option

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: Justin Kerk, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030120
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030120

When you right click on an image in an HTML mail message, there is no
"Properties" item in the menu like there is in the Mozilla browser.

Reproducible: Always

Steps to Reproduce:
1. Open an HTML mail message with images.
2. Right click on one of the images.
Actual Results:  
No "Properties" option.

Expected Results:  
"Properties" option in the list just like with the web browser.

There are a couple situations I can think of offhand in which this would come in
handy:

* You get an HTML newsletter with ad banners and you want to see if the server
they're on is used for anything else before blocking it (this is how I first
noticed the problem)

* You get an HTML spam that uses images and you want to find out the server used
for hosting so you can complain to the abuse department

These can be worked around by copying the image's address to the clipboard and
then pasting it somewhere, but that's rather inconvenient.

It's also disconcerting from an interface perspective to have an option that one
commonly uses in the Mozilla browser missing from the Mozilla mail client.

Comment 1

14 years ago
Another problem with the the lack of HTML-element Properties, is that users
can't modify anything they added using the Insert HTML option.
 
Prog.

Comment 2

14 years ago
brade@comcast.net suggested the following workaround in Bug 143593, comment 1:

> in the mean time, a workaround is to select the portion of html that you want to
> edit and to go to the "Insert" menu and choose "HTML..."
> That will open a dialog window (small tho) which contains the portion of html
> source for the selection.  You can make your changes there and then click OK and
> they should be inserted/reapplied.

Prog.

Comment 3

14 years ago
This is actually part of the menu spec:
  http://www.mozilla.org/mailnews/specs/threepane/MailMenus.html

Note that for images which are also links, the spec calls for separate "Image 
Properties" and "Link Properties" menu entries; the browser currently combines 
both sets of properties into a single window, and I think this would be best in 
the Mail window as well.
Severity: enhancement → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: laurel → message-display

Comment 4

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 5

9 years ago
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 6

9 years ago
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 7

8 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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.