automatic inlining should be optional



MailNews: Message Display
15 years ago
12 years ago


(Reporter: Tom Howland, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

In the 1.1 composer, I would copy a web page with photographs from Navigator to
Composer. The resulting mail message had the html from the web page, but the
images were pointing to the original source. This was lovely behavior. I could
send people rich content without cluttering up their mailboxes with jpegs.

I understand that it is safer and perhaps less surprising to inline everything
but I wish that I could get the old behavior back.

Reproducible: Always

Steps to Reproduce:
1. visit a web page with graphics
2. compose an (html format) mail message
3. paste the web page into the mail message
4. send the message to yourself
5. look at the inlined graphics

Actual Results:  
got a really large email message

Expected Results:  
referenced the graphics from the mail message by hyperlinks to the originating
QA Contact: yulian → stephend
this has nothing to do with attachments --> mail window front end.
Assignee: mscott → sspitzer
Component: Attachments → Mail Window Front End
QA Contact: stephend → olgam


15 years ago
QA Contact: olgam → esther


15 years ago
Severity: normal → enhancement

Comment 2

13 years ago
Reporter, how do you paste the page into composer?

Comment 3

13 years ago
(In reply to comment #2)
> Reporter, how do you paste the page into composer?

The normal way -- select all, copy

By the way, I can get what I want by attaching a web page with the correct base
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.