36861 - paste removes whitespace from ends of lines

Status: VERIFIED WORKSFORME

(Core :: DOM: Serializers, defect, P3)

Description

[Dawn Endico]

Pasting from this document causes some adjacent words to run together.
For example: "Check Tinderboxto ensure tree is open..."

When lines end with html tags such as "</a>" all whitespace up
until the next word is deleted. This should all get translated into
a space.

For instance, the html "-\n-" prints "- -" and when you select this and
paste it into a document the pasted text, as expected is "- -".

But the html "<a href="">-</a>\n-" also prints "- -" but when you select
this, the pasted text is "--", with no spaces in between the dashes.

Comment 1

[Dawn Endico]

Attachment: test case

Comment 2

[rubydoo123]

assigning to akkanaa for debugging -- reassign as appropriate Akkana

Comment 3

[Akkana Peck]

Clarification: this is a problem when copying html and pasting plaintext.

I'll track it down.

Comment 4

[Akkana Peck]

Fixed.

Comment 5

[Akkana Peck]

Really marking fixed this time.

Comment 6

[sujay]

verified in 10/30 build.

Comment 7

[TucsonTester1]

I am still seeing this bug in Composer rev. 2001112603 on win 98 and win XP
(presumably it will happen on other OS'es too)

My steps to recreate:
1. Open an new page in composer
2. Type some text (the word "testing" for example)
3. Select the text and add rich text to it (bold, color, bigger, etc.)
4. Add a space to the end of the word then select all of it and copy.
5. Paste this elsewhere on the page.

Expected behavior: 
All characters will paste including the space at the end.

Actual behavior:
The pasted text will run together as the space is gone (e.g. testingtesting)
The space will be correctly retained if the text is left as default... it is
only after the text has rich features applied to it that it will not paste the
space added onto the end. 
If the text has a space added to it before rich text is applied, it will retain
the space when pasted... apparently the order of things is important. 

Comment 8

[Akkana Peck]

DOM to text conversion.

Comment 9

[harishd]

--> peterv

Comment 10

[Tanu Mutreja]

Could not reproduce it by following steps mentioned by Tucson.

Comment 11

[michael wendell]

I am also not able to reproduce this problem using the steps mentioned in
comment 7.  And even if I was, I don't think that it is related to the original
problem. The bug in comment 7 sounds more like a dupe of 105487 which I am still
able to reproduce.   

I am resolving this WORKSFORME since the original bug was verified FIXED on 10-30.

Comment 12

[sujay]

verified.