Bug 18995 – Text entries in Safari and other apps exhibit random dupe behavior

• Status: RESOLVED
• Resolution: WONTFIX
• Component: Text

[Dave Aton]

When I have WebKit nightly running (currently SVN-r32012, but also with some earlier builds), random text entry behavior problems will manifest in Safari as well as other apps. Typing text in TextEdit, for example, I may see the last 4 or 5 characters repeat as if I had just copied and pasted them, while I type. Or doing a copy/paste may paste two copies of the text from the clipboard. In fact, after I registered for WebKit Bugzilla and copied/pasted the password sent by e-mail, the system pasted it in duplicate.

[Mark Rowe (bdash)]

This seems unlikely to be due to WebKit.  WebKit has no effect on any other applications on the system.

[Dave Aton]

(In reply to comment #1)
> This seems unlikely to be due to WebKit.  WebKit has no effect on any other
> applications on the system.

It could be coincidence, but that behavior appeared after I started using WebKit, (for about a week), and ceased when I went back to using the standard Safari release.

[Dave Aton]

(In reply to comment #2)
> (In reply to comment #1)
> > This seems unlikely to be due to WebKit.  WebKit has no effect on any other
> > applications on the system.
> 
> It could be coincidence, but that behavior appeared after I started using
> WebKit, (for about a week), and ceased when I went back to using the standard
> Safari release.

I should add that when I was using the nightly WebKit, I did not thoroughly isolate it from third-party Safari plugins, so it's possible that the problem was caused by one of them.

[Ahmad Saleem]

In absence of reliable test to reproduce, it is difficult to reproduce this bug today and also as mentioned in earlier comments, TextEdit and WebKit might not interact with each other, it could be processor being stalled by process leading to slower inputs rather than WebKit influencing 'TextEdit' application directly.

I am going to mark this as 'RESOLVED WONTFIX' since it was never confirmed and it didn't had any test case.

[Dave Aton]

I haven't seen that bug in a few yrs, so appropriate to close it.