Open Bug 310628 Opened 19 years ago Updated 12 years ago

Insert HTML moves tags from HEAD to BODY

Categories

(SeaMonkey :: MailNews: Composition, defect)

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

Tracking

(Not tracked)

People

(Reporter: michael.besteck, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de-AT; rv:1.7.10) Gecko/20050727
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; de-AT; rv:1.7.10) Gecko/20050727

Related environment:
The Mail Window of the suite:
Mozilla 1.7.10
Mozilla/5.0 (X11; U; Linux x86_64; de-AT; rv:1.7.10) Gecko/20050727
(mozilla.org downloaded english language version with installed german/austrian
language pack)
OS: Suse 9.3
Hardware:
CPU  AMD Athlon 64 3000+
Mainboard ASRock ("Upgrade") w/ VIA-Chipset

Bug Description:
Mozilla Mail changes correctly formatted HTML-source inserted while composing
email into uncorrectly formatted HTML. As a result HTML-formatted parts of
Multipart MIME Emails do not render correctly in Outlook Express [OE]

(a) (probably a real bug):
CSS-style definitions in the "<header>...</header> of HTML source, inserted into
an "empty" email via the "insert HTML" function
are stripped off the leading dot (".") [_this_ causes problems rendering in
OutlookExpress],
the CSS-style definitions are moved inside the "<body>",
meta-tags are moved inside the "<body>",
the "<title>" is doubled and emptied inside the "<head>".
The rendering failures of CSS-styles in OE disappeared after manually adding the
dots (".") in the ".eml"-file that Mozilla Mail stripped off.

Example:
============ inserted Source part (start) ============
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
  
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

  
  <meta name="AUTHOR" content="Michael Besteck">
  <title>Bewerbung</title>

  
  
  <style type="text/css">
<!--
body { left: 0px; top: 0px; margin: 0px; padding: 0px; color: #000000;
background-color: #FFFFFF; line-height: normal; font-family: Arial, Helvetica,
sans-serif; font-size: 4.5mm; font-style: normal; font-weight: normal;
font-variant: normal; text-decoration: none; background-attachment: scroll;
background-repeat: repeat-y;}
table {  vertical-align: middle; text-align:left;}
td {  vertical-align: text-top; text-align: left; padding: 2mm;}
a {  color: #0000FF; font-family: Arial, Helvetica, sans-serif; font-size:
4.5mm; font-style: normal; font-weight: normal;}
hr { width: 100%; height: 0.7mm; margin-top: 8mm; margin-bottom: 8mm; color:
#5555AA; background-color: #5555AA; border-width: 1px; border-style: none;
border-color: #000000; text-align: center;}
.divBody {  position: absolute; top: 0px; left: 70px; margin: 0px; padding: 0px;}
.tdGreyTitle { white-space:nowrap; padding: 2mm; color: #FFFFFF;
background-color: #0E1B8D; font-size: 6mm; font-weight: bold; vertical-align:
middle; text-align: left; background-repeat: repeat-x;}
-->
  </style></head>
<body style="background-image: url(bgline.jpg);">
<div class="divBody">
<table style="vertical-align: middle; text-align: center; width: 100%;"
border="0" cellpadding="0" cellspacing="0">
============ inserted Source part (end) ============
============ Mozilla-Mail formatted part of the "final" email (start) ============
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body alink="#000099"
 background="cid:part4.06090801.07070308@freenet.de" bgcolor="#ffffff"
 link="#000099" text="#000000" vlink="#990099">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="AUTHOR" content="Michael Besteck">
<title>Bewerbung</title>
<style type="text/css">
<!--
body { left: 0px; top: 0px; margin: 0px; padding: 0px; color: #000000;
background-color: #FFFFFF; line-height: normal; font-family: Arial, Helvetica,
sans-serif; font-size: 4.5mm; font-style: normal; font-weight: normal;
font-variant: normal; text-decoration: none; background-attachment: scroll;
background-repeat: repeat-y;}
table { vertical-align: middle; text-align:left;}
td { vertical-align: text-top; text-align: left; padding: 2mm;}
a { color: #0000FF; font-family: Arial, Helvetica, sans-serif; font-size: 4.5mm;
font-style: normal; font-weight: normal;}
hr { width: 100%; height: 0.7mm; margin-top: 8mm; margin-bottom: 8mm; color:
#5555AA; background-color: #5555AA; border-width: 1px; border-style: none;
border-color: #000000; text-align: center;}
divBody { position: absolute; top: 0px; left: 70px; margin: 0px; padding: 0px;}
tdGreyTitle { white-space:nowrap; padding: 2mm; color: #FFFFFF;
background-color: #0E1B8D; font-size: 6mm; font-weight: bold; vertical-align:
middle; text-align: left; background-repeat: repeat-x;}
-->
</style>
<div class="divBody">
<table style="vertical-align: middle; text-align: center; width: 100%;"
 border="0" cellpadding="0" cellspacing="0">
============ Mozilla-Mail formatted part of the "final" email (end) ============


(b) (rather a question of policy)
If there are more than 1 images referenced inside the HTML source,
OutlookExpress can only access
the first image and does not "find" the others. As much as i remember this is
not a problem of Mozilla,
but of Redmonds "i am the standard"-way. Anyhow, such eml does not render the
second and following images in HTML emails on OE.
The rendering failures of images in OE disappeared after manually adding a line
break between the image parts in the ".eml"-file.


Example:
============ Mozilla-Mail formatted part of the "final" email, between HTML
source and first image (start) ============
</body>
</html>

--------------080209060606050409040406
Content-Type: image/jpeg;
 name="PB804_125x168_SDLO.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.00080902.01050100@freenet.de>
Content-Disposition: inline;
 filename="PB804_125x168_SDLO.jpg"

/9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
============ Mozilla-Mail formatted part of the "final" email, between HTML
source and first image (end) ============
============ Mozilla-Mail formatted part of the "final" email, between first and
second image (start) ============
TNJKFWSEj9spv9SAjcIOxH/XxXgzJDKHYBVAv1JvvY/8/wAPhwXeqiV2XzGxte3w36ep/dx/
/9k=
--------------080209060606050409040406
Content-Type: image/png;
 name="subject.png"
Content-Transfer-Encoding: base64
Content-ID: <part2.06020903.06080406@freenet.de>
Content-Disposition: inline;
 filename="subject.png"

iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAACXBIWXMAAAsSAAALEgHS3X78

============ Mozilla-Mail formatted part of the "final" email, between first and
second image (end) ============
============ Mozilla-Mail formatted part of the "final" email, between second
and third image (start) ============
kcOGYfSIEWBTNRvtJ9CQwZ6y2KPeyzRyMUk6eTnPhf/3158NEXuJAvFgqwAAAABJRU5ErkJg
gg==
--------------080209060606050409040406
Content-Type: image/jpeg;
 name="bgline.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part4.06090801.07070308@freenet.de>
Content-Disposition: inline;
 filename="bgline.jpg"

/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
============ Mozilla-Mail formatted part of the "final" email, between second
and third image (end) ============

Severity/Comment:
RFCs should be a must to keep and i believe for shure that Redmond would be able
to follow them - to me this seems one incarnation of the so called "browser-war".
I do not like war as i do not like Redmond.
But i like Mozilla and use it already for long time for email and browsing.
Since well designed HTML emails are very important to me and i commonly use
email "officially", its no good solution to me to end all my emails saying
"Please use a RFC conform email client to view this email" as i started with today.

Reproducible: Always

Steps to Reproduce:
1. Insert HTML-source like in e.g. when composing email as desscribed under Details
2. save that email as xxx.eml
3. open it with OutlookExpress
Actual Results:  
Bad/Uncorrect rendering - all images but the first are not visible

Expected Results:  
keep the inserted HTML as it was inserted
I can confirm that the tags from <HEAD> were moved inside <BODY> (the new HEAD
has its own duplicate TITLE tag) with linux seamonkey trunk 20050929.  But the
"." aren't removed for me.
Assignee: general → composer
Status: UNCONFIRMED → NEW
Component: General → Composer
Ever confirmed: true
QA Contact: general
Summary: Mozilla Mail changes correctly formatted HTML-source inserted while composing email into uncorrectly formatted HTML. As a result HTML-formatted parts of Multipart MIME Emails do not render correctly in Outlook Express → Insert HTML moves tags from HEAD to BODY
Version: unspecified → Trunk
MozillaAS v1.7.x is not supported anymore.

Can you reproduce with SeaMonkey v1.1.9 ?
Assignee: composer → nobody
QA Contact: composer
Still here, build:
Mozilla/5.0 (Windows NT 5.2; rv:13.0) Gecko/20120227 Firefox/13.0a1 SeaMonkey/2.10a1
Steps to reproduce:
1) Create new html e-mail
2) Paste via Insert - HTML code from "inserted Source part"
3) Save letter as file with .eml extension
Actual Results:
css code reallocated from head to body
Expected Result:
Code leaved intact
Also, moving bug to mail section
Component: Composer → MailNews: Composition
OS: Linux → All
QA Contact: composer → mailnews-composition
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.