Orion editor support is broken; modifications render but do not persist

[1ec5]

In an Eclipse Orion editor, such as the one here, typing chu+~ in VIQR gets you “chữ”, but as soon as you press any key or click anywhere, the word reverts to “chu”. Effectively, Orion support is just an illusion.

[1ec5]

The original Orion support, which I wrote years ago, assumed (correctly at the time) that the originalTarget would be div#clientDiv.editorContent. Orion’s frontend appears to have been rewritten since then, so now AVIM falls back on contenteditable support, which doesn’t touch Orion’s model.

[1ec5]

In fact, no IME extension on either Firefox or Chrome works with Orion. Google Input Tools comes the closest, allowing you to enter an entire word before the word disappears. On the Mac at least, even system IMEs have trouble with Orion: after committing a composition, you can no longer start a new composition.

[1ec5]

originalTarget is now div.textviewContent. Some Orion functionality can be accessed through window.orion and window.orion.editor, but everything else is neatly hidden away. It seems like most AVIM’s ordinary contenteditable support should be adequate, but Orion is listening for the obsolete textinput event instead of input (or compositionstart and compositionend in the case of system IMEs).