Issue metadata
Sign in to add a comment
|
1st input is English after switching IME to Chinese/Korean from "System tray" |
||||||||||||||||||||||
Issue descriptionChrome Version : 57.0.2984.0 Platform : 9199.0.0 - Minnie What steps will reproduce the problem? (1) set IME to English, enter "abc" on the omnibox (2) click the System tray and select & set IME to Korean (3) enter "gks" on the omnibox (4) set IME to English, enter "abc" on the omnibox (5) press "ctrl + shift + space" to set IME to Korean (6) enter "gks" on the omnibox What is the expected result? On step#3, ķ should be entered. 1st input should be Korean What happens instead? On step#3, "gė" is entered On step#6, "ķ" is entered. The input is properly entered. Please provide any additional information below. Attach a screenshot if possible. Reproduce the issue on chrome 56.0.2924.67/CrOS 9000.66.0 - paine Not reproduce the issue on Chrome 55.0.2883.105/CrOS 8872.76.0 - Daisy ======== Please feel free to remove the stable-block label if it isn't required
,
Jan 23 2017
Assigning to Albert. Please pass along to the right folks, thanks.
,
Jan 24 2017
,
Jan 25 2017
I can reproduce the issue with Korean IME, but cannot reproduce with Japanese IME. still investigating...
,
Jan 25 2017
+wuyingbing@ who may have some ideas about the extension code.
,
Jan 25 2017
I only see the issue Korean/Chinese ime, not Japanese IME. Ja ime works fine on M57/M56
,
Jan 25 2017
|onKeyEvent| is called with Ctrl+SPC when switching by the keyboard shortcut, but it's not called when switching by the system tray button. Could it be a cause?
,
Jan 25 2017
Do you mean that this issue only repros when switching to C/K IMEs by Ctrl+SPACE?
,
Jan 25 2017
There is no problem when switching by Ctrl+SPACE. Only if switching by system tray, this issue repros.
,
Jan 25 2017
Thanks for investigation. It is a weird issue, and the root cause seems in the extension. I will take it from here.
,
Jan 25 2017
Thank you for taking this.
,
Jan 25 2017
Root cause found & Azure is working on the fix.
,
Jan 25 2017
Any updates? We cut stable build today, thanks.
,
Jan 26 2017
Punting this to M57 RBS as fix is too risky to merge into M56 at this point
,
Jan 26 2017
Thanks for removing the M56 flag. The fix is in extension code, and the extension has some significant updates during M57. So the last minutes merge to M56 stable without sufficient testing is too risky.
,
Jan 26 2017
Btw, the cl https://chrome-internal-review.googlesource.com/#/c/321043/ will fix this issue.
,
Feb 6 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/f904763ee6f7aa83043b61f1fe99b9a1acf5639d commit f904763ee6f7aa83043b61f1fe99b9a1acf5639d Author: azurewei <azurewei@chromium.org> Date: Mon Feb 06 09:35:14 2017
,
Feb 6 2017
,
Feb 6 2017
Approving merge to M57 Chrome OS.
,
Feb 8 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/a03ddf012c212b13ca3987745ae9c5dd9176fd7b commit a03ddf012c212b13ca3987745ae9c5dd9176fd7b Author: azurewei <azurewei@chromium.org> Date: Wed Feb 08 02:33:41 2017
,
Feb 8 2017
,
Feb 10 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 11 2017
,
Aug 1 2017
,
Nov 9 2017
9901.66.0, 62.0.3202.82 stable channel |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yabinh@chromium.org
, Jan 20 2017