Able to see the issue when switching IME from Korean to non-Korean, Chrome 60.0.3112.67/CrOS 9592.54.0-Cyan

Steps: 
1. set VK ime to Chinese(Simplified) - Pinyin input method
2. switch VK ime to Korean 
3. switch VK ime back to Chinese(Simplified) - Pinyin input method
Then, Korean VK is still seen.

wuyingbing@: Could someone in the IME team take a look?

Any luck with this fix?

We are really close to M60 promotion to stable 

CL is on submmiting.
see: https://chrome-internal-review.googlesource.com/c/417668/

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/3f1215f51b263ebba9281fb4a5d153faafcde531

commit 3f1215f51b263ebba9281fb4a5d153faafcde531
Author: Yingbing Wu <wuyingbing@google.com>
Date: Wed Jul 26 11:15:02 2017

[Auto-generated comment by a script] We noticed that this issue is targeted for M-60; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-60 label, otherwise remove Merge-TBD label. Thanks.

This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hi josafat@chromium.org,

Could you approve the merge ASAP.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/7e9c9004dc1af758b04754639acd6100752c1880

commit 7e9c9004dc1af758b04754639acd6100752c1880
Author: Yingbing Wu <wuyingbing@google.com>
Date: Wed Jul 26 21:02:51 2017

Able to reproduce the issue on Chrome 61.0.3163.13/ CrOS 9765.7.0 - Caroline.

Verified in Chrome OS 9592.71.0, 60.0.3112.80. 

Reproduce the issue on 61.0.3163.16/ CrOS 9765.9.0 - Cyan.   
Will verify the issue when the fix is in M61.

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

Verified on Chrome OS 9592.71.0, 60.0.3112.80 (stable build).

Hi. Was it OK to merge the change to M60?
I'm wondering because I suspect it caused  crbug.com/749953 .
Sorry if I'm wrong. Thanks.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/3417f04d0776118e257263a7db6525566ffa5830

commit 3417f04d0776118e257263a7db6525566ffa5830
Author: Yingbing Wu <wuyingbing@google.com>
Date: Tue Aug 01 00:46:20 2017

Hi oka,
The CL is already merged to M60 and M61.

So it's not a culprit for  crbug.com/749953 ?

No, it's not.
Already found the other root cause.

Verified on Chrome 61.0.3163.20/CrOS 9765.13.0 - Caroline