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

Issue 218382 link

Starred by 45 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Jul 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Sign in to add a comment

hterm: IME's don't work

Project Member Reported by, Nov 12 2012

Issue description

From the chromium-hterm mailing list:

1. Under chrome://chrome/settings/languages, add Japanese as an input language, and select "Google Japanese Input (for US keyboard)".
2. Open up secure shell and create a connection
3. Select the Japanese IME (left alt + shift)
4. Type in a few vowels ("aaa" should do it)

You should get an over-the-spot editor to select between (at least) "あああ" and "アアア". What I see in secure shell is three a's.

I've tried in screen, vim in screen, vim outside of screen, and just a plain bash prompt; they all get the same results.

Comment 1 by, Nov 13 2012

This is an ugly area. Take a look at and . 
Cc:  was an issue internal to Aura: an ui::KeyEvent converted from an X11 XKeyEvent was sometimes broken.

The hterm issue looks unrelated to the Aura issue. My guess is that hterm has to handle DOM3 composition events to receive texts from an IME.

 Issue chromium:127260  has been merged into this issue.

Comment 4 Deleted

Comment 5 Deleted

Comment 6 Deleted

Comment 7 by, Feb 16 2014

Labels: Cr-UI-Input-Text-IME
Status: Untriaged
Could you triage this again?  Is this still reproducible?  Does this affect our on-screen keyboard effort near future? (e.g.  Emoji palette).

Comment 8 by, Feb 16 2014

I think I have the same problem. In a Crosh Window, if I type åäö I get åäö instead.

I'm on stable channel on an ARM chromebook. Swedish keyboard layout.

Please fix this.
Status: Assigned
Buld edit: assigning back to Xiangye for triage.

Comment 11 Deleted

Comment 12 by, Aug 11 2014

Seems to be the same as  Issue chromium:125888 

Comment 13 by Deleted ...@, Sep 4 2014

I can confirm that the issue is present in i3 and Chrome 37.0.2062.94 and gone in Chrome 39.0.2138.3. Thanks for fixing.

Comment 14 Deleted

Comment 15 by, Apr 17 2015

Secure Shell 0.8.33 continues to not support Japanese IME.

Chrome 42.0.2311.90 m on Windows 8.1; IME shows status "Disabled" when attempting to repro.

Comment 16 by Deleted ...@, Jun 20 2015

I confirm this bug. Chinese IME is not supported either.

Comment 17 by Deleted ...@, Jul 6 2015

Chrome 版本 43.0.2357.130 m, confirm this bug.
 Issue 125888  has been merged into this issue.
This issue has existed for three years. 

As a non-English software engineer, I have to handle many projects with Chinese language. 

The issue will slow down my efficiency that this plugin disallowes me to enter Chinese characters. Therefore, I have to change the SSH tool.

Finally, I cloned the source code from the Chrome extension: Secure Shell and modified it to support ime-mode for non-English characters typing.

Here is my hack:

It can temporarily solve my problem but I really hope this bug will be fixed quickly.

Potential downstream users at this repo

Comment 21 Deleted

Summary: hterm: IME's don't work (was: hterm: incorrect handling of utf-8 input)
i'm not familiar with how IME is implemented in Chrome.  does the hterm method of accepting input not jive with Chrome's detection of when to show the IME ?
 Issue 662701  has been merged into this issue.

Comment 24 Deleted

Status: Fixed (was: Assigned)
as part of the work for  issue 402972 , this seems to work now

although there are still some rough edges (e.g. issue 738172)

Comment 27 by, Jan 22 2018

Status: Archived (was: Fixed)
Status: Fixed (was: Archived)

Sign in to add a comment