Keyboard shortcuts are broken in DevTools Console
Reported by
ckm...@gmail.com,
Feb 4 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.13 Safari/537.36 Steps to reproduce the problem: Steps to reproduce the problem: 1. Open DevTools -> Console 2. Start typing some Javascript into the console. 3. Try to use alt+b/alt+f to jump words forward or backward What is the expected behavior? All OS configured shortcuts should work as intended. What went wrong? Upgraded Chrome to latest version. Did this work before? N/A Chrome version: 57.0.2987.13 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 24.0 r0 Opening this issue by request from Chrome dev. For more notes on the original issue and problem see this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=683532
,
Feb 6 2017
,
Feb 8 2017
#1, #3: Open the issue 683532 linked in this bug report and read comments #3-4 by ligim...@chromium.org
,
Feb 8 2017
My bad. Didn't check the link in the report!
,
Feb 13 2017
I'm not familiar with these shortcuts, but alt-b and alt-f enter the 'integral' and 'function' symbols on my Mac. I tried to do control-alt-b and control-alt-f on Mac Canary 58.0.3010.0 and they seem to jump the cursor to the last/next word group. Could you please check on the latest Canary?
,
Feb 27 2017
Assigned this issue based on Issue 683532 #c1 and 683532#c2. einbinder@: Could you please take a look into this.
,
Feb 27 2017
@luoe
You're right that by default the alt+{key} binding normally inserta special unicode symbols in the default OSX setup.
However, if you rebind alt+f/b as follows:
====
"~f"="moveWordForward:";
"~b"="moveWordBackward:";
====
in your systems keybindings.dict, you will have the same functionality as alt+left/right which jumps words forwards and backwards. This works correctly in any textarea, textbox or any other keyboard input area.
Looking at the code, the change of the Console widget to CodeMirror broke this support because CodeMirror binds listeners to all keys and only executes those for which it has a configured binding. This means that any user who modified their OS keyboard config to replace the defaults will no longer be able to use those keys in Console unless CodeMirror has those exact bindings with the same functionality.
,
Mar 17 2017
,
Oct 31
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kkaluri@chromium.org
, Feb 6 2017Labels: Needs-Feedback
656 KB
656 KB View Download