New issue
Advanced search Search tips

Issue 794617 link

Starred by 0 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

hterm: support keyboard mappings based on KeyboardEvent.code

Project Member Reported by vapier@chromium.org, Dec 13 2017

Issue description

currently we allow people to bind keys based on KeyboardEvent.keyCode (a number), or based on a static list of identifiers we maintain [1].  this largely works, but there's some scenarios where this doesn't work as well: if two different keys generate the same keyCode (such as the keys on the numpad like Enter/NumpadEnter and 7/Numpad7 and all the rest), there's no way to bind them separately.

KeyboardEvent.code provides a human readable string that is different: "Enter" vs "NumpadEnter".  we should allow people to bind to that like Ctrl-Shift-NumpadEnter.

https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code

this probably will take a bit of reworking, and make sure that we don't end up with ambiguous grammar between our existing parser identifiers and the browser table of "code" values.
 
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 14

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