Bug 531800 - runtime error "e.getKeys is not a function" occurs when showing keys for Emacs or vi
Summary: runtime error "e.getKeys is not a function" occurs when showing keys for Emac...
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Client (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: 18.0   Edit
Assignee: Silenio Quarti CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-02-28 11:09 EST by Grant Gayed CLA
Modified: 2018-03-01 09:26 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2018-02-28 11:09:07 EST 
- click on the wrench of an open editor and change the Keys>Key Bindings to either Emacs or vi
- invoke Tools > Show Keys
- keybindings are not shown, instead an error is spewed:

Uncaught TypeError: e.getKeys is not a function
    at Object.s [as getUserKeyString] (uiUtils.js:138)
    at a.createItem (keyAssist.js:122)
    at L.showKeyBindings (editorCommands.js:450)
    at a.createContents (keyAssist.js:116)
    at a.show (keyAssist.js:383)
    at a.callback (keyAssist.js:438)
    at p._collectAndInvoke (commandRegistry.js:486)
    at p._invoke (commandRegistry.js:426)
    at a.M (commandRegistry.js:1311)
    at HTMLSpanElement.<anonymous> (commands.js:541)
Comment 1 Grant Gayed CLA 2018-02-28 11:34:56 EST 
Comparing the "binding" objects that get processed by uiUtils.js:138, they look completely different between the "Default" and "Emacs/vi" cases, so not surprising that getKeys() is not defined in the latter case.