Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
Description
On latest versions of Chrome (>15) the Enter key generates a charCode(13) which is not as I expected (0) on the onKeyPress event.
Test this at: http://unixpapa.com/js/testkey.html
The code in the rt plugin takes into account in the onKeyPress listener every charCode which is not 0 thus generating an "Insert" operation for normal characters.(Following the assumption that charCode for special keys is 0. )
Obviously the "Enter" key was dealt with in the onKeyDown listener where it generates a "new paragraph" operation, but it's also handled after, on the onKeyPress event (charCode 13) thus resulting in desynchronization.
So the Enter key in real-time plugin is dealt twice when it should be handled only in the onKeyDown.