Closed Bug 96749 Opened 23 years ago Closed 23 years ago

Message source window has weird formatting when pasted

Categories

(MailNews Core :: Composition, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 98572

People

(Reporter: baffoni, Assigned: bugzilla)

Details

I do a lot of spammer complaints, and so what this requires is that I open the message source of a spam message, then paste it into the body of an email that I am sending to the servers that service the spammers, web servers, etc. When I paste the message source into a mail window, a couple of things happen: first the lines do not wrap when pasted into the message. What I expect to happen is that text pasted into a message window wrap to the bounds of the window border (even if a carriage return is not inserted - my default is wrapping at 99999 characters so that you can allow the recipient's email client to do proper wrapping of long lines). Second: when I try to copy some of the text from the message source to a different part of the message (say if I copy the Subject: line and put it at the top in my comments), then it adds a carriage return both before the snipped text and after the text. What I expect to happen is that the text I selected is inserted into the text area I select as JUST text, no formatting and no pre/post returns/characters. I noticed that all text inserted from "message source" says that it is of format "preformatted" rather than Body text, or other format.
Forgot to mention this is Build 2001082303 (too bad bugzilla doesn't pre-populate a field with the build information - which you can change if you are using a different browser) running on Windows 2000. This occurs in builds at least since .92.
confirming using 2001082806 build on win98
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: sheelar → esther
1. This applies to text from the source of a message *or* browser window pasted into a message compose window. This does not apply to text pasted from other sources: Emacs or Xterm. 2. If the message is in HTML, leading and trailing line breaks appear, as Michael said. If the message is in plain text, only trailing line breaks appear. 3. If the message is in HTML, these new line breaks are unkillable. Attempts to delete either the leading or trailing breaks, using forward or backward delete, act as if the break did not exist. Instead, characters on the other side of the break are deleted. This doesn't happen for plain text messages. I am using Mozilla 0.9.6 on Redhat 7.1, and reproduced it with Moz 0.9.6 on MacOS 9.1.
I don't know if this is related, but I grabbed text from news.cnet.com/news/0-1004-200-8060454.html?tag=lh and pasted it into a mail compose window. Then when I typed below the inserted text, the cursor moved ABOVE the text and characters started appearing. Funky.
copy/past message source into a message compose window works fine for me using 12/10/01 build. WFM
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
What did you do to test this? All I have to do is to copy the text from even a reply-to part of a replied email, paste the text (one word or a whole paragraph - it doesn't matter) into the new part of the email and it will automatically insert at least one CR/LF (whatever win2k uses) both before and after the inserted text. I'm seeing this on 12/13/2001 build (03) on Win2k.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
What you are seeing is another problem for which we have another bug report. I tested the main problem reported in this bug about copying the result of a view source into a message compose window. This case is working correclty for me! Let me find the bug number you are seeing...
Sorry, this bug is kind of confusing. Anyway, it's a dup of bug 98572 *** This bug has been marked as a duplicate of 98572 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
verified dup.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.