UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
0. Configure your Linux machine to use MacOS/Emacs keystrokes for input boxes.  One of more of these will do the trick:

Put this in your .gtkrc-2.0:

    gtk-key-theme-name = "Emacs"

Run these commands:

    $ gconftool-2 --set /desktop/gnome/interface/gtk_key_theme Emacs --type string
    $ gsettings set org.gnome.desktop.interface gtk-key-theme "Emacs"
    $ gsettings set org.cinnamon.desktop.interface gtk-key-theme "Emacs"

1. Upgrade from 58.0.3029.110 to 59.0.3071.86.  The bug begins somewhere between those versions (left side exclusive, right side inclusive).

2. Type any of the following in input boxes:

Ctrl-A (should go to beginning of line, instead selects all)
Ctrl-E (should go to end of line, instead triggers the useless "Search Google" behavior)
Ctrl-F (should go forward one character, instead opens a "Find in this page" box)
Ctrl-B (should go backward one character, instead does nothing)

What is the expected behavior?

Chrome has respected the system configuration for these keystrokes for the better part of a decade, if not since it was released in 2008; this is a major behavioral regression from my perspective.

What went wrong?
I don't know.  Chrome just stopped respecting the configuration of system input boxes.

Did this work before? Yes 58.0.3029.110 (latest known)

Chrome version: 59.0.3071.86  Channel: n/a
OS Version: Goobuntu
Flash Version: ?