New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 751869 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All , Chrome
Pri: 2
Type: Bug


Participants' hotlists:
Fixing-touch


Sign in to add a comment

Chinese/Japanese IME doesn't start when switching from the other IMEs - Virtual keyboard

Project Member Reported by songsuk@chromium.org, Aug 2 2017

Issue description

Chrome Version       : 61.0.3163.20
Platform             : 9765.15.0  - Quawks

What steps will reproduce the problem?
(1) add Chinese- Pinyin IME or Google Japanese Input
(2) open chrome://md-settings/languages >>Input method
(3) enable the 'Show input options in the shelf' option
(4) focus on the omnibox, and click on Emoji in the Input icon in the shelf to bring up the virtual keyboard
(5) click on Keyboard button to get the US keyboard  
(6) switch IME to Pinyin from English, click on "tian"
(7) switch IME to English, and switch IME to Pinyin from English
(8) click on "tian"

What is the expected result?
On step#6, should be able to see the Chinese candidate lists and enter Chinese characters

What happens instead?
On step#6, "tian" is entered. Chinese candidate list doesn't show up on the Keyboard.

On step#8, able to enter Chinese characters
The issue happens when switching IME to Chinese/Japanese for the first time.

Please provide any additional information below. Attach a screenshot if
possible.
Reproduce the issue on 60.0.3112.80/9592.71.0 - Link
Will check the Issue on M59
 
Owner: yhanada@chromium.org
I check the latest google input tool package in M61. It's broken.
I remember it was fixed before. Maybe forgot to merge back M61.
Hi yhanada, Could you help to verify whether the bug repro in M62?
Able to reproduce the issue on Chrome 62.0.3174.0/CrOS 9801.0.0 - Quawks
Cc: yhanada@chromium.org
Owner: wuyingbing@chromium.org
Status: Assigned (was: Untriaged)
Sorry for the belated response. I confirmed that it happens on M-62.
This bug has a target milestone that has passed.  Please help bug cleanup: mark it closed or update/remove the milestone target. 
Status: WontFix (was: Assigned)
Unable to reproduce the issue on Chrome 68.0.3440.118/CrOS10718.88.0 -peppy

Sign in to add a comment