another way to reproduce: enable an IME (like Japanese), then click anywhere in the terminal, then start typing.  the temporary IME input will show up where you clicked (not where the terminal cursor is), and once you hit enter to select the ideogram, the temporary IME input stays stuck.

When I use an IME to reproduce the above problem, I can see the temporary IME inputs show up in both at where I clicked AND at the terminal cursor as the attachment shows.

Deleted: both.png 92.9 KB

	both.png 92.9 KB View Download

In chrome web browser on android phone, it appears that the input is not being sent to the actual IO object, it's staying in the (now content editable) div. Result: typing using the Android keyboard doesn't actually have any effect. (tested using Wetty which uses hterm UI).

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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