Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 1 resposta
  • 1 tem este problema
  • 1 exibição
  • Última resposta de 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 tela anexadas

Todas as respostas (1)

more options

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