Closed Bug 134462 Opened 23 years ago Closed 22 years ago

Preserving HTML source in mail composition

Categories

(Core :: DOM: Editor, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 126259

People

(Reporter: metrol, Assigned: kinmoz)

References

(Blocks 1 open bug)

Details

Every couple of weeks I put out a manaully put together HTML newsletter to my company's customers. This is normally put together with NS 4.7x as it still does a pretty good job of this. With Moz as far along as it is I thought I'd try this out on Moz instead. In short, had to go back to NS before I could send that mail out. First problem, Moz's composer insists on inserting a line feed between the end of an img tag and the closing anchor tag. This, of course, leaves an underscore next to every image as a part of the link in NS 4.7x clients at least. To attempt to work around this, I then took the mail in progress on into Composer with "Retain original source formatting" on. Thought I was home free until I copied the page from Composer to the mail composition and sent a test. Sure enough, the mail client reformatted the HTML once again! No matter how I approached this problem my img links continued to have that darn underscore next to it. This exposes 2 bugs in my mind. First off, the mail composition should respect the Composer settings. Secondly, Composer itself should always close out linked images with no white space between it and the closing anchor tag. Minor stuff I know, but very annoying. Worse yet, it turned into a major show stopper for something that I would have thought to have been pretty straight forward.
Michael Collette--what version of mozilla did you test?
this is an editor problem. Reassign
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Product: MailNews → Browser
QA Contact: esther → sujay
*** This bug has been marked as a duplicate of 126259 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.