From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) BuildID: 20011205 While running the Front-end tests for Copy and Pate, I noticed that when I ran the "Copy Text Indented" test that the format of the info copied was not retained when pasted into "Edit" or "Text Edit" on OpenVMS Reproducible: Always Steps to Reproduce: 1.follow steps in http://www.mozilla.org/quality/browser/front- end/testcases/copy-paste/copy-text-indented/copy-text-indented.html Actual Results: pasted text comes out as 1 long line Expected Results: text should retain format ( carriage returns and indentation ) I could NOT reproduce this on my version of Linux (I have 2001112013) and using "gEdit 0.6.1". I used "edit" on OpenVMS, which I got into by typing "edit" in a terminal window; and I also used "Text Editor" that I found in Desktop Apps.

I've done this test 5 times, and it passed once! The time it passed, I started to highlight the text in the white space above "The Mozilla" while the times it failed I started on the "T" in "The Mozilla". Also wanted to note that I did a serach in Bugzilla, and wanted to mention these other bugs: 42879 and 59849. I thought this was diff enoough to be it's own bug, but you might think otherwise.

I should mention that the test failed on Linux when I started to highlight the text on the "T" of "The Mozilla". Changing feilds that make this OpenVMS only, sorry about that.

I just noticed this problem report was assigned to me (I usually just look for ones where OS == OpenVMS). Reassigning to the owner of the selected component.

Really changing Platform/OS back to VMS as stated in comment 3

Why did Mr Aillon in comment 4 change the OS of this bug to OpenVMS when comment 2 clearly states that the problem is NOT OpenVMS specific. The convention is that if a problem is discovered on OpenVMS but also occurs on Linux then we mark the bug as Linux (that way developers aren't scared away from the bug because they know nothing about OpenVMS). Changing OS to Linux, and confirming the bug.

its actually a table. if you select the beginning of the table then the serializer realizes that you are in a table and white spaces/returns it properly to reflect format. If you select from one cell to the next it just treats it as more content. This was probably done to allow people to copy from articles ect that use tables instead of paragraphs. you could select from one cell/paragraph to the next and just get the text not the tab delimited/spaced text. At any rate this is in the serializer not in the selection code. I will let the owner of XP APPS decide if they need to fix this or not.

Copy and paste in win32 also exhibits the same behaviour. ie. copy from any html document that is in a table and paste it to another win32 app (ie. notepad, etc) does not preserve cr/lf.

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420