Developer tools' Editor Keybindings setting doesn't work
Categories
(DevTools :: Console, defect)
Tracking
(Not tracked)
People
(Reporter: ryan.lue, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.230 Safari/537.36
Steps to reproduce:
- Open developer tools (<F12>)
- Go to Settings > Editor > Keybindings
- Select Emacs
- Return to JS console
- Try to use emacs keybindings
(FWIW, this is happening on version 60.5.1esr on debian Linux)
Actual results:
Various UNIX readline shortcuts (C-a, C-b, C-f, C-n, C-p) all perform their normal functions in firefox, as opposed to moving the cursor or navigating the command line.
- C-b opens bookmarks
- C-p opens print dialog
- C-a selects all text
- C-n opens a new window
- etc.
Expected results:
- C-b moves cursor back one character
- C-p navigates to previous command
- C-a moves cursor to beginning of line
- C-n navigates to next command
- etc.
|
||
Updated•6 years ago
|
Hello Ryan, the editor settings only affect the console input starting Firefox 62.
Could you try with a more recent firefox version and tell us if it works fine? (we know there's an issue with Ctrl-f , see Bug 14444498)
Hi Nicolas, thanks for the speedy feedback! Just tried on FF Developer Edition 66.0b10 and seeing the same results. I've verified that the devtools.editor.keymap config setting has been set to "emacs", but again, C-a selects all, C-b opens bookmarks, etc. etc.
Should I update the bug to reflect the fact that this issue is happening on v66?
Just a quick question, does the text in the console input is highlighted?
Because we only have a codemirror instance running if: 1. a given preference is on (devtools.webconsole.jsterm.codeMirror), 2. if you don't have accessibility features turned on (because codemirror isn't accessible at all).
If you do have a syntax highlighted input, then there must be something wrong, and I'll investigate.
Okay, yes, the accessibility features are absolutely the reason this wasn't working for me. I installed it on my laptop, and it works just fine.
But the really strange thing is, I can't turn off accessibility features on my desktop, so I just can't get the keybindings to work there. I saw this bit on the MDN docs:
Once the panel content loads, you can then turn it off again
using the Turn Off Accessibility Features button available
in the top-left corner, unless you have the accessibility
engine running previously to operate a screenreader, in
which case this button will be disabled.via https://developer.mozilla.org/en-US/docs/Tools/Accessibility_inspector
but I'm pretty sure I'm not operating a screen reader, and I don't know what else would be keeping the accessibility engine from closing.
So now I guess I have two concerns:
- shouldn't this link between the keybindings and the accessibility features be documented somewhere, like ideally in a tooltip or UI hint next to this setting?
- should I open a new bug for this can't-turn-off-accessibility-features problem I'm having?
Thanks again.
Description
•