579849 - Keyboard mapping not working anymore

Status: RESOLVED INVALID

(Skywriter Graveyard :: Key Bindings, defect)

Description

[Julian Viereck]

Reported by Irakli on the bespin-core mailing list:

> After investigation I solved some issues but did not managed to fix vim 
keyboard mapping. 
> I have an impression that modes don't work any more, at least not the way 
they used to.

I did a small debugging and it seems like this brakeage is caused in rev 1918: 
http://hg.mozilla.org/labs/bespinclient/rev/1918

Before this changeset, the `keyDown` event called the 
`keyboardManager.processKeyEvent` function, the `textInserted()` function the 
`keyboardManager.processKeyInput` function.

After the changeset, both input kinds (keyDown and textInserted) call the 
`editor.processKeyEvent`. This is okay for the `keyDown` event. The inserted 
text from the `textInserted()` function is now treated the same way as the 
keyDown event. This doesn't work out, as the textInserted() function passes a 
string of inserted characters and not an event to the `editor.processKeyEvent`, 
which then calls internal the `keyboardManager.processKeyEvent()` function.

@Patrick: What was the reason for this changeset? Could there be a 
EditorView.processKeyEvent() and EditorView.processTextInput()?

Comment 1

[Kevin Dangoor]

ACETRANSITION

The Skywriter project has merged with Ajax.org's Ace project (the full server part of which is their Cloud9 IDE project). Background on the change is here:

http://mozillalabs.com/skywriter/2011/01/18/mozilla-skywriter-has-been-merged-into-ace/

The bugs in the Skywriter product are not necessarily relevant for Ace and quite a bit of code has changed. For that reason, I'm closing all of these bugs. Problems that you have with Ace should be filed in the Ace issue tracker at GitHub:

https://github.com/ajaxorg/ace/issues