Closed Bug 313401 Opened 19 years ago Closed 6 years ago

forwarding multipart/related message inline does not include body, if <html> tag has attribute and View/Message Body As/Simple HTML is used

Categories

(MailNews Core :: Composition, defect)

Product:
MailNews Core
Component:
Composition
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 394322

People

(Reporter: ajschult784, Unassigned)

Details

(Keywords: regression)

Attachments

(2 files)

message-to-be-forwarded source
14.02 KB, text/plain
Details
Two multipart/related mails, one = <html id="...">, another = <html>
4.28 KB, text/plain
Details 
If set the pref to View->Message Body As->Simple HTML and then try to forward a
multi-part email (inline), the compose window includes the headers of the
original message, but not the body.

Steps to reproduce
1. View->Message Body As->Simple HTML
2. Edit->Preferences->MailNews->Composition->Forward Messages Inline
3. Attempt to forward message (I'll attach a sample one)
==> Composition window includes headers but not body from message-to-be-forwarded

This regressed between linux suite builds 2005060102 and 2005060205, perhaps bug
11034.
forwarding this message omits the body.  Drop it in Local Folders to make it a
folder containing the message.

Also note that the html part has <html
xmlns:v=3D"urn:schemas-microsoft-com:vml">.  If I switch it to <html>, then the
body is forwarded as expected.
I can also reproduce the bug with tbird 1.5b2 (linux)
This is true whether your compose window is plain text or HTML.
It does not occur with TB 1.0.
Keywords: regression
OS: Linux → All
Hardware: PC → All
Version: Trunk → 1.8 Branch
>            Version|Trunk                       |1.8 Branch

?
I changed the version because the regression occured in that branch.
(1.8 = Seamonkey 1.0 = TB 1.5)
It regressed before the branch (see comment 0).  The 1.8 branch was created 8/12/06.  But either way, isn't Version=1.8 only for bugs that only occur on the branch?
QA Contact: composition
Product: Core → MailNews Core
Confirming bug still exists with Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1.
I tried to reproduce this on TB 14 and 15, and what I get is different than the description.

If I take https://bugzilla.mozilla.org/attachment.cgi?id=200456 and make it a local folder, I see a message with the body content "foo" and an image as an attachment.

If I try to forward it, I get a message with "foo" as the content, but no attachment. This is not what comment 0 describes.

So that is not correct behaviour, but it is different than the reporter. Could you clarify please?
I experience the same result as the reporter:  if I open that message and do Message -> Forward As -> Inline, then a composer window pops up with the following text, which contains the headers but not the message body.  The attachment isn't there either.


-------- Original Message --------
Subject: 	Invitation to Reception by Nanyang Technological University at
AIChE Annual Meeting 2005
Date: 	Fri, 21 Oct 2005 09:34:32 +0800
From: 	Mariyam Binte Mohamed <Mariyam@ntu.edu.sg>
To: 	<ajschult@verizon.net>
Two simple/ordinal multipart/related HTML mails with a valid embed image.
Difference is Subject:, Message-ID:, and <html> tag only.
Shown elements by Forward inline in HTML mode(Tb 13.0.1/17.0a1 on Win-XP):
>                                           View/Message Body As
>                                  Original HTML            Simple HTML
>  mail-01 : <html id="root_tag">  html text, embed image   Nothing
>  mail-02 : <html>                html text, embed image   html text, embed image

"text/html under multipart/alternative under multipart/related" was not relevant. It was problem when mail is multipart/related mail, attribute of HTML tag is used, and Simple HTML mode is used.

(In reply to Kent James (:rkent) from comment #8)
> I tried to reproduce this on TB 14 and 15, and what I get is different than
> the description.
>(snip)
> If I try to forward it, I get a message with "foo" as the content, (snip)

As Andrew Schultz(bug opener) says, this bug was for;
(a) not-well-formed mail
    part 1: multipart/related
      part 1.1: multipart/alternative
        part 1.1.1: text/plain, mail body text = Dear Andrew
        part 1.1.2: text/html,  mail body text = foo
          no <img src="cid:..."> for image part under multipart/related
          <html xmlns:v=3D"urn:schemas-microsoft-com:vml"> (quoted-printable)    
      part 1.2: image/gif; name="worst.2.gif"
           Content-ID: <9.0.0.74.0.53201321691068.88521624@vitro.abc-cards.ch.9>
           Content-Disposition: inline; filename="worst.2.gif"
(b) View/Message Body As/Simple HTML
(c) If html tag is chaned to <html>, problem disappears.
Note:
If View/Message Body As/Plain Text, text in text/plain part(Dear Andrew) was shown. So, when Plain Text mode, text/plain part is already used by Tb as expected, instead of converted text from text/html part. 

Kent James, did you check with View/Message Body As/Simple HTML?

> but no attachment.

As you know, because finename parameter is specified for non-referred image/gif part under multipart/related, Tb shows it "as if attachment" at atachment pane to provide a way to save this image/gif data to file. This image/gif part is never valid/legal embed part in multipart/related nor valid/legal attachment part in multipart/mixed. It's also applicable to non-displayable part under multipart/alternative.
I think "no attachment when Forward in inline" is very normal if test mail attached by bug opener, except that it is different from user's normal expectation or usual guess from "image/gif file shown at attachment pane".
IIRC, this "mismatch between VALID Tb's behaviour and user's expectaton" is already reported in some bugs.
Thanks WADA, I missed the "Simple HTML" part. Now I can reproduce.

Next question: How important is this? That is, are emails with this problem created naturally as part of a widely used application like Outlook or Gmail?
Version: 1.8 Branch → Trunk
(In reply to Kent James (:rkent) from comment #11)
> Next question: How important is this? That is, are emails with this problem
> created naturally as part of a widely used application like Outlook or Gmail?

As seen in following HTML source of original mail attached by bug opener, 
> <html xmlns:v=3D"urn:schemas-microsoft-com:vml">
many of mailers/mail systems provided by MS put xmlns attribute in <html> tag.
i.e. If Tb user uses (a) "Simple HTML" mode for (b) HTML mail made by MS's software, user usually experiences this bug upon (c) "Forward in inline".
> number of users of (a) : not so many, rather rare than Original HTML users
> number of users of (b) : can not be small
> number of users of (c) : I believe ordinal user's preference is not "Forward as attachment".
So, number of users of (a)&&(b)&&(c) is not negligible, even though not so many.
Summary: forwarding multipart message inline does not include body → forwarding multipart/related message inline does not include body, if <html> tag has attribute and View/Message Body As/Simple HTML is used
If someone gets around to this, the mozmill test from bug 394322 can probably be useful.
I believe this bug is a variant of bug 496723.
   If "Simple HTML" mode, <html> is internally complemented by sanitizing in Tb.
   So, phenomenon of bug 496723 is exposed upon "Inline Forward".
See Also: → 394322
Status: NEW → RESOLVED
Closed: 6 years ago
No longer depends on: 496723
Resolution: --- → DUPLICATE
See Also: 394322 →
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: