287394 - forward HTML message inline munges original message

Status: RESOLVED DUPLICATE of bug 307023

(Thunderbird :: General, defect)

Description

[Rob Hudson]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla Thunderbird version 1.0 (20041206)

I received an HTML email.  When I forward it, thunderbird copies the message
inline but the HTML is broken.

Example...

Original message excerpt:

It didn't make much more sense on second thought either, there has to be simpler
ways to put the local coffee bar on a map, but then movies such as <i>"<a
href="http://www.imdb.com/title/tt0120148/">Sliding Doors", </a></i>"<i><a
href="http://www.imdb.com/title/tt0108122/">Short cuts</a>"</i> and <i>"<a
href="http://www.imdb.com/title/tt0175880/">Magnolia</a>"</i> came to my mind.

Inline message of the above:

It didn't make much more sense on second thought either, there has to be
simpler ways to put the local coffee bar on a map, but then movies such
as /"Sliding Doors", <ttp://www.imdb.com/title/tt0120148/">/"/Short cuts
<ttp://www.imdb.com/title/tt0108122/">"/ and /"Magnolia
<ttp://www.imdb.com/title/tt0175880/">"/ came to my mind.

I received the above message with newspipe, an RSS to email program.

Reproducible: Always

Steps to Reproduce:
1. Receive a message with HTML
2. Forward it as inline
3.



Expected Results:  
Expect the forwarded inline message to either be correct non-munged HTML, or
more like how Mutt handles messages with the link and a [1] to a footnote of the
actual URL.

Comment 1

[Scott Eade]

I am seeing something like this too with Thunderbird 1.0.2.  It doesn't occur
for all messages, but it is certainly consistently occurring for regular set of
messages that I send out from a webapp - these messages contain tables with a
mix of th and td elements with colspans and utilise an embedded css style sheet.
 The corruptions are confined to the table.  What I see are missing end quotes
on attributes (e.g. colspan, class, etc.) which result in the following html
source being encoded.

i.e. I get things like:
    <tr class="&gt; &lt;th style=ext-align:right;"
 colspan="&gt;Group members 2 or more days overdue&lt;/th&gt;
          &lt;td style=ext-align:right;vertical-align:baseline;"
 align="ight&quot;" valign="aseline&quot;">
1&nbsp; </tr>

instead of:
  <tr class="b">
    <th style="text-align:right;" colspan="3>
      Group members 2 or more days overdue
    </th>
    <td style="text-align:right;vertical-align:baseline;" align="right"
align="baseline">
      1&nbsp;
    </td>
  </tr>

Please let me know if I can assist in providing further examples.

Scott

Comment 2

[Mike DeWolfe]

I found this also. When I tried sending a message via Outlook with an HTML
attachment, it kept the HTML of the message separate from the HTML of the
attachment.
When I sent the same attachment and the same message via Thunderbird , it
combined the HTML of the message and the attachment.

Comment 3

[Sönke Tesch]

The problem of the missing characters Scott noted looks similar to bug 307023,
even though in that case, only HTML attributes are affected. Are the mails (or
parts thereof) you're trying to forward encoded using quoted-printable?

Comment 4

[Sönke Tesch]

The problem of the missing characters Scott noted looks similar to bug 307023,
even though in that case, only HTML attributes are affected. Are the mails (or
parts thereof) you're trying to forward encoded using quoted-printable?

Comment 5

[Scott Eade]

Yes, the messages I am forwarding are encoded using quoted-printable - from the
message source:

    Content-Transfer-Encoding: quoted-printable

Sönke Tesch appears to be right in suggesting that this might be the same as bug
307023 - as indicated there, the problem occurs when the message is forwarded,
but not when "Reply" is used instead on the same message.

I am currently running version 1.0.6 (20050716) and the problem still occurs.

Scott

Comment 6

[Mike Cowperthwaite]

Duping to a later bug because it had a more complete test case.

*** This bug has been marked as a duplicate of 307023 ***