Japanese Entry on reactJS based websites removes consonants before generating the kana output.
Reported by
kinoshit...@gmail.com,
Jan 15 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Install Linux Mint 18.1 Cinnamon 2. in terminal, install Japanese IME with following command: $ sudo apt install fcitx-mozc --install-recommends 3. Then activate by using: $ im-config -n fcitx 4. Log out, then log in your Linux user. 5. You will notice keyboard icon on system tray. 6. Ctrl + Space to enable Japanese input (Orange icon with japanese symbol in it) 7. Visit Facebook, and place cursor in any text box, enable Japanese input and type in saigo<spacebar>ni<enter> 8. Notice 最後い is shown instead of the actual proper 最後に (the kana is showing "i" instead of "ni") retry 7 and 8 using firefox on the same system and notice it will show 最後に properly. What is the expected behavior? Do not auto-remove consonants after pressing space bar to select a kanji combination. What went wrong? it looks like the normal HTML input tags are OK, but the special reactJS generated text input for writing something on your feed or writing a comment on someone else's post is broken with Japanese input on Chrome only. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: Mint 18.1 Flash Version: Shockwave Flash 24.0 r0
,
Jan 16 2017
,
Jan 19 2017
I tried to reproduce it on Ubuntu 14.04 with chrome version #55.0.2883.87, but didn't enable to reproduce the scenario, adding "TE-NeedsTriageHelp" label so that this issue can get addressed.
,
Feb 17 2017
Able to reproduce the issue on Chrome 58.0.3004.3/ 56.0.2924.87 - Ubuntu 14.04. I'm seeing "最後い" on facebook input field. On Chrome omnibox/Findinpage/gmail inbox, "最後に" appears. Will check the issue on win/mac/chromeos.
,
Feb 17 2017
I was also able to reproduce the issue in LINE messanger Windows app run through Wine. This seems to indicate to me that the issue is most likely upstream... as I highly doubt LINE messanger is using reactJS.
,
Dec 23 2017
This issue is still present, and the more people I try to get into Linux, the more people I have to tell NOT to use Chromium/Chrome, since Facebook will cause them headaches. (Most Japanese people now use Facebook frequently) Would love to see a permanent solution from Chromium.
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Dec 27
This problem is being observed as of Chrome 71, severely affecting broad spectrum of environment. Occurred with Ibus, fcitx running under KDE, Gnome and xfce. I tried to pinpoint this issue from multiple avenue including inspecting React code that's running in Facebook, etc., too but ultimately I had to stop using Chrome. This problem does not happen on Windows and seems to be only pertinent to Linux environment. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kinoshit...@gmail.com
, Jan 15 2017142 KB
142 KB View Download
94.0 KB
94.0 KB View Download