Steam client version (build number or date): June 14 2018
Distribution (e.g. Ubuntu): Ububtu 16.04
Opted into Steam client beta?: [Yes/No] yes
Have you checked for system updates?: [Yes/No] yes
Please describe your issue in as much detail as possible:
On steam beta, and public version of steam, the steam chat input refuses to take input from the Japanese keyboard iBus (mozc). I asked a friend of mine, who uses japanese keyboards frequently on steam to send me a screenshot of his chat window (he uses windows). I noticed that he had a white box saying "JP" in the lower right/upper right corner of the text input field, which I didn't have.
I can type in romanji (roman characters) fine, but when it comes to hiragana and katakana it comes as romanji (even tho I've selected it). I've tried a bunch of methods to try fix this like reinstall the keyboard package, etc. but it doesn't seem to get fixed.
The problem might lie in how the keyboard recognizes text fields, it might not be recognizing steam's chat input field as one.
I'll try looking for the screenshots, when I do, I'll link them here.
Your system information
Please describe your issue in as much detail as possible:
On steam beta, and public version of steam, the steam chat input refuses to take input from the Japanese keyboard iBus (mozc). I asked a friend of mine, who uses japanese keyboards frequently on steam to send me a screenshot of his chat window (he uses windows). I noticed that he had a white box saying "JP" in the lower right/upper right corner of the text input field, which I didn't have.
I can type in romanji (roman characters) fine, but when it comes to hiragana and katakana it comes as romanji (even tho I've selected it). I've tried a bunch of methods to try fix this like reinstall the keyboard package, etc. but it doesn't seem to get fixed.
The problem might lie in how the keyboard recognizes text fields, it might not be recognizing steam's chat input field as one.
I'll try looking for the screenshots, when I do, I'll link them here.
Steps for reproducing this issue: