Avatar for Username

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Text background becomes black after pressing space key with Japanese input keyboard

  • 1 respuesta
  • 1 tiene este problema
  • 1 visita
  • Última respuesta de Sylve

Sylve
Sylve
more options

Hello,

I use mozc (a Japanese input method editor) on Linux to type in Japanese. With this kind of input method, you can press on the space key to go from hiragana to kanji. For example you type ふるい, then press space, and it becomes 古い.

But I got this problem: when I press the space key the background becomes black and I can no longer read!

Please see the attached screenshots. I come across this behavior only with Firefox (not with any other GTK app such as Deluge or GIMP).

The problem is not resolved by making Firefox ignoring my GTK theme (see https://askubuntu.com/questions/8336/how-can-one-make-firefox-ignore-my-gtk-theme-entirely ).

Do you have any idea where my problem is coming from?

Best wishes,

Sylve

Hello, I use mozc (a Japanese input method editor) on Linux to type in Japanese. With this kind of input method, you can press on the space key to go from hiragana to kanji. For example you type ふるい, then press space, and it becomes 古い. But I got this problem: when I press the space key the background becomes black and I can no longer read! Please see the attached screenshots. I come across this behavior only with Firefox (not with any other GTK app such as Deluge or GIMP). The problem is not resolved by making Firefox ignoring my GTK theme (see https://askubuntu.com/questions/8336/how-can-one-make-firefox-ignore-my-gtk-theme-entirely ). Do you have any idea where my problem is coming from? Best wishes, Sylve
Capturas de pantalla adjuntas

Todas las respuestas (1)

Sylve
Sylve Autor de la pregunta
more options

Sorry for posting this. I think the problem is coming from mozc. See this issue: https://github.com/google/mozc/issues/455