65615 - Characters getting inserted in the wrong place

Status: VERIFIED WORKSFORME

(Core :: DOM: Editor, defect, P1)

Description

[scottputterman]

Build 2001011604 NT

Once again, editing my status report. I'd noticed this a bunch but I thought it
was my fault but I actually caught this in action just now.

Part of my document had the words "some performance" in it.  I put the edit
cursor right before the 'p' in performance. I then typed "test" and ended up with

"somteste performance" which is unexpected. I would have expected "some test
performance"

Comment 1

[scottputterman]

Nominating for beta1 since I would like characters to show up where I think they
are going to show up.

Comment 2

[scottputterman]

I will attach a sample file for this.  In the file I'm going to attach, look at
the 2nd bullet that starts with "David".  In the very last sentence, look for
"And he did some performance".  Put the cursor right before the 'p' in
performance. Then type "test".  You should then see this bug.

Comment 3

[scottputterman]

Attachment: file that shows this bug

Comment 4

[rubydoo123]

assigning to joe -- joe, I think this is related to some of the whitespace 
issues. If you go to source mode and enter a character you'll see all sorts of 
weird whitespace issues. The docuemnt looks fine in wysiwyg mode as well, until 
you set the caret somewhere and hit the spacebar. In any event, I will leave 
this one up to you as to whether this is a whitespace issue or some other issue.

Comment 5

[Joe Francis]

This is a dup of some ws bug or other.  It will be fixed by my work in progress.

Comment 6

[Joe Francis]

hmm, wait a minute.  i think my comment in this bug was meaqnt to go in a 
different bug.  I'll look into this.

Comment 7

[Joe Francis]

i cant reproduce this, though i do get the bug of extra whitespace appearing
when you follow the directions to reproduce.  Scott, if you can get this to
happen in a new debug build please give me a ring.   

Comment 8

[scottputterman]

marking WORKSFORME.  In 2001012904 on NT this works for me now, but as Joe
writes, the extra spaces still occur, but that's a different bug. Even if you
didn't know you fixed this, thanks for fixing this :)

Comment 9

[sujay]

verified in 1/30 build.