You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that issue #83 attempted to resolve this problem, but I am still encountering it. I am using Microsoft Input Method or Rime Input Method (Chinese).
Expected Result: The input method should be disabled in normal mode (or behave the same as in English input mode), and pressing keys such as a, o, j, k should not move the cursor or input characters (or should move the cursor correctly).
Actual Result: In normal mode, the behavior is random (varies depending on the input method used), such as h and l moving two characters, both j and k moving down, and a character behind the cursor being deleted or modified.
In command mode, when users input by IME, this plugin currently removes the DOM element and re-adds it, to cancel the IME after receiving the character users input. I suspect some internal state of the external IME doesn't update during this procedure.
I noticed that issue #83 attempted to resolve this problem, but I am still encountering it. I am using Microsoft Input Method or Rime Input Method (Chinese).
Expected Result: The input method should be disabled in normal mode (or behave the same as in English input mode), and pressing keys such as a, o, j, k should not move the cursor or input characters (or should move the cursor correctly).
Actual Result: In normal mode, the behavior is random (varies depending on the input method used), such as h and l moving two characters, both j and k moving down, and a character behind the cursor being deleted or modified.
I tested this on https://codemirror.net/5/demo/vim.html, and it behaves as expected. However, when I forked and ran the project at https://replit.com/@util/codemirror-vim, the issue still exists. The test page mentioned in issue #83, https://raw.githack.com/replit/codemirror-vim/github-demo/dev/web-demo.html, is now inaccessible.
The text was updated successfully, but these errors were encountered: