Chinese IME input disrupted by cursor jumping and text displacement

Bear Web
1

Operation system: Windows

Web Browser: Firefox

Bug report

What were you doing: Using the Microsoft Traditional Chinese Input Method Editor (IME) to type Chinese characters in the editor

What feature did you use: Editor

What happened: When typing Chinese characters (which requires a sequence of keystrokes per character), the input is sometimes interrupted mid-character. The cursor unexpectedly jumps to the start of the line, and text from the next line moves to the end of current line. The screencast shows two attempts at typing the same text - the first works correctly, while the second demonstrates this disruptive behavior.

What did you expect to happen: Complete character input without cursor disruption or text displacement.

Feedback: For reference, this issue does not occur in editors on other websites (e.g. Bear Community). While I’m reporting with Microsoft Changjie, this may affect other IME-based languages that require multiple keystrokes per character, which affects basic usability.

2

Thanks for the report! I will investigate.

3

We have improved IME input like Chinese pinyin, and now it should work correctly also on Windows. Let me know if you still have problems.

4

Thanks for your help. Unfortunately, the issue still persists. To clarify:

  1. It occurs even in Firefox’s troubleshoot mode
  2. This problem is specific to Bear Web in Firefox (most other web apps work correctly)
  3. It functions properly in Chrome

Hope this additional context helps. Thank you.

5

This surprises me. I was able to replicate the issue from your first report and fixed it. Try to reload the page (Ctrl+R), and if that doesn’t help, try a full reload (Shift+Ctrl+R). If this works, let me know which kind of reload that did the trick (we might need to adjust our caching strategy).

If the problem persists even after reload, then record a new video showing the issue and I will do my best to fix it.

6

A simple page reload (Ctrl+R) didn’t resolve the issue. However, performing a full reload (Shift+Ctrl+R) seems to have fixed the problem. I haven’t encountered any further issues so far. Thank you for your help!