New issue
Advanced search Search tips

Issue 738172 link

Starred by 5 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

hterm: when using the virtual keyboard, cursor/input state is not tracked correctly

Project Member Reported by vapier@chromium.org, Jun 29 2017

Issue description

seems like in some cases, when using a virtual keyboard, the terminal cursor is not updated, nor is the input typed displayed at the correct location

to reproduce, load hterm in a web browser on an Android phone, and then just start typing.
 
Cc: briannorris@chromium.org
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.

Comment 3 by johnl...@gmail.com, Aug 25 2017

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.
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).

Project Member

Comment 5 by sheriffbot@chromium.org, Nov 12

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Sign in to add a comment