BUG: Forward HTML inline and Content-Transfer-Encoding: quoted-printable

[Arivald]

I just discover this bug.

When user try to forward HTML message inline, and this source message has
Content-Type: text/html; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
headers then TB incorrectly decode HTML attachment, and produce errors.

for example, this source lines:

<TABLE=20
style=3D"BORDER-RIGHT: #999999 1px solid; BORDER-TOP: #999999 1px solid; BO=
RDER-LEFT: #999999 1px solid; BORDER-BOTTOM: #999999 1px solid"=20
cellSpacing=3D0 cellPadding=3D0 width=3D490 border=3D0>

Apperas in forwarded message as:

<table style="" border-top:="" border-left:="" solid;=""
border-bottom:="" #999999="" 1px="" solid="" border="1"
cellspacing="cellPadding=widthI0">

As we can see, for some reason TB try to forward HTML without removing
transfer encoding first.

another example:

<IMG height=3D266 src=3D"cid:e084846e84c9ce1f7662f878=
ba49c6cf"=20 width=3D540 border=3D0></A>

become

<img moz-do-not-send="true" height&6="" src="ailbox:///C%7C/[...]"
widtht0="" border="</A">

As result, all images in forwarded HTML are broken.

This case does not apply to replying, replies are ok.
Also i found, if source message have headers like this:
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
then forwarding work correctly...

Only charset has been changed... very strange.

Can somebody verify it is TB bug, not only my installation problem?

--
Arivald

[Dan Mosedale]

Arivald wrote:
> I just discover this bug.

Unfortunately, posting about random bugs has the problem that people
don't feel compelled to respond to those postings, and/or they respond,
but the posting gets lost track of over time. If you could file this in
Bugzilla, that would be great. It should take a similar amount of
effort to making a newsgroup post.

Dam