Vscode: Google Japanese Input (IME) on Mac - Suggestions Overlap w/ Text

Created on 13 Mar 2018  ·  19Comments  ·  Source: microsoft/vscode

  • VSCode Version: 1.21.0
  • OS Version: macOS 10.13.1

Steps to Reproduce:

  1. Install Google Japanese Input https://www.google.co.jp/intl/ja/ime/
  2. Activate it
  3. Open a new VSCode instance
  4. Type konnnichiha on keyboard, then hit enter, and do it again a few times
  5. Expected: the suggestions should never overlap w/ text. Actual: the suggestions overlap w/ text.

See the GIF:

screen recording 2018-03-12 at 08 03 pm

Does this issue occur when all extensions are disabled?: Yes

Notes:

This is not an issue with the default Japanese IME that comes w/ macOS.


Update (Sep 27, 2018): Workaround

This setting seems to fix the issue. (You'll lose some functionalities)

*question editor-input-IME help wanted mac

Most helpful comment

Same Here

All 19 comments

Same Here

same here

Same Here

@jrieken The suggestion box that shows up in this case is not the one for suggestWidget. This seems like a native control which I dont believe VS Code controls

cc @rebornix @octref

@chibicode @Yamotty @mashriq @CM-Kajiwara Is this a regression? Did this work as expected in earlier versions of VS Code and stopped working recently?

I think it is probably caused by the position adjustment of the textarea, Google IME tries to put the candidate list at the proper position, but I don't have a stable reproduce yet.

Sorry, I am a new user to VSCode so not sure if this is a regression.

@rebornix I can repro it consistently.

image

Not just VSCode but Adobe Brackets seems to have the same issue as well - and for that, apparently, the issue is on CodeMirror:
https://github.com/codemirror/CodeMirror/issues/4089

If it's an Electron issue not sure if upgrading Electron to 2.x or 3.x fixes it. https://github.com/Microsoft/vscode/issues/45542

This was not an issue on Atom (even when Atom was using Electron 1.x).

I also searched through Twitter, and people have been reporting this since April 2015. Definitely not a regression. @ramya-rao-a @rebornix

https://twitter.com/shohaga/status/593568407301193728
https://twitter.com/hiedar83/status/593676327665860608
https://twitter.com/tyamaz/status/593728561392984064

Same Here

@rebornix

2018-08-24 12 03 06
2018-08-24 12 03 35

@rebornix @octref Is there anything I can do to help?

Also saw this reported on Teratail, a Japanese Stackoverflow clone, about a week ago.
https://teratail.com/questions/143100

※日本語で失礼します。

暫定的(temporary)な回避策(workaround)ですが、「Google 日本語入力 環境設定」の「サジェスト」タブの
・入力履歴からのサジェスト自動表示を有効にする
・リアルタイム変換を有効にする
のチェックを外せば被らなくなりました。(上記機能は失われますが…)
2018-09-26 11 51 35

Translating what @hiramatsu said:

Temporary workaround: go to Google Japanese Input preferences,

screen shot 2018-09-26 at 6 58 30 pm

go to サジェスト ("suggest") and uncheck

  • 入力履歴からのサジェスト自動表示を有効にする (disable suggestion from input history)
  • リアルタイム変換を有効にする (disable live conversion)

Then click 適用 button at the bottom.

Then it no longer overlaps.

@hiramatsu @chibicode thanks for your help. This issue was caused by how we implement our editor (virtualize everything but has a tiny textarea around the virtual cursor) and Google IME doesn't work the same as the OS builtin IME. I don't have a good idea how to hint Google IME about the position but your solution works perfectly for this issue.

For anyone who is using English as system language, the preference with the workaround will look like below:

image

@rebornix thanks for the follow-up!

Just for completeness: Google maintains "a subset of Google Japanese Input in the form of source code under OSS license without any warranty nor user support" at google/mozc (more explanation), though they're not accepting pull requests at the moment.

Same here

same here

same here
OS: windows 10
Language: Chinese
IME: Sogou Pinyin, Baidu Pinyin
无标题

Please ask your question on StackOverflow. We have a great community over there. They have already answered thousands of questions and are happy to answer yours as well. See also our issue reporting guidelines.

Happy Coding!

Was this page helpful?
0 / 5 - 0 ratings