Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-76001

Editor cursor jumps back to the top of line when perform Japanese language conversion

XMLWordPrintable

      Issue Summary

      Editor cursor jumps back to the top of the line when performing Japanese language conversion

      Steps to Reproduce

      It depends on the OS environment.
      Windows OS with ATOK(IME)

      1. install ATOK (https://atok.com/)
      2. open browser
      3. create confluence page(new editor)
      4. input "Japanese" and perform Japanese language conversion
      5. cursor back to the top of line.
      6. If enter a word first, and input after a word, it works fine.(cursor doesn't back to the top of the line)

      OS platform: Windows 10 Pro & Windows 10 Enterprise
      Browser : Chrome(64bit 114.0.5735.110, 114.0.5735.119(Official Buil)), Firefox(114.0.1 64bit, 133.0.2)
      IME: ATOK (version 33.0.4)

      Linux

      1. OS > Language support > install 日本語(Japanese)
      2. OS setting > Keyboard > add "Japanese(Mozc)"
      3. open browser
      4. create confluence page(new editor)
      5. input "Japanese" and perform Japanese language conversion
      6. if enter [space] key, conversion is done.(can't select)
      7. cursor back to the top of the line.
      8. If enter a word first, and input after a word, it works fine. (cursor doesn't back to the top of the line)

      OS platform: Ubuntu 20.04, Ubuntu 22.04 LTS, Ubuntu 22.04.2 LTS, Ubuntu 20.04.6 LTS
      Browser: Chrome, Firefox
      IME: Japanese(IBus - Mozc)

      Mac OS
      Even if a user were to add ATOK, it would work fine.


      Expected Results

      cursor does not back to the top of the line, and select conversion from list.

      Actual Results

      cursor back to the top of the line. And if it's ATOK, unnecessary comments are also entered.

      Workaround

      Windows OS
      If a user uses Microsoft IME(OS default IME), it works fine .

      Linux OS
      Currently there is no known workaround for this behavior. A workaround will be added here when available

      If a user can use legacy editor, in legacy editor it works fine.

              Unassigned Unassigned
              38f0fdb790c2 K. Ariga
              Votes:
              70 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: