Did keybindings on macOS change in Chrome 55?

[Ryan K]

I use Chrome on macOS noticed that the dev tools text editing widgets no longer respect emacs/readline style keybindings to drive cursor movement. 

These keybindings are usually respected in Cocoa applications and they work in all other widgets in Chrome (including the URL/search input at the top of the browser and all other text inputs in actual pages).

For example, Ctrl-f moves the cursor one character forward, Ctrl-k deletes the text from the cursor to the end of the line, Alt-b moves the cursor backwards one word. A few still appear to work: Ctrl-a moves to the beginning of a line and Ctrl-e to the end. Also, Ctrl-n and Ctrl-p scroll the console history but have no effect in other input widgets.

Is there a way to reenable these keybindings?

Thanks.

[Doug Harris]

There's a reported issue for this: https://bugs.chromium.org/p/chromium/issues/detail?id=656251

Click the star near the bottom to vote for the issue (you'll need to log in with your google account). By doing so, you'll register your interest in this and also get email notifications whenever the ticket changes.

Doug

(not involved in Chrome development, just affected like Ryan K by this change in behavior)