It's inconceivable that this should require any maintenance. I don't need a "backspace key goes back" checkbox, I just need to be able to customize the keyboard bindings. Decoupling the actions a program can perform from the key combinations which trigger those actions is basic stuff.
From the maintainer's point-of-view, having the option to bind "backspace" to "window.history.back" shouldn't require any more maintenance than having the option to bind "alt-left" to "window.history.back" does.
It is Google's fault that they didn't make Chrome work this way. It also means I can't unbind "ctrl-shift-q" from "quit_immediately_without_asking", because Google refuse to add an option to make it so that I can't accidentally fat-finger a C-w into something that ends my entire session. All keyboard shortcut problems disappear instantly if key bindings are configurable, however, without adding new options for each command.
From the maintainer's point-of-view, having the option to bind "backspace" to "window.history.back" shouldn't require any more maintenance than having the option to bind "alt-left" to "window.history.back" does.
It is Google's fault that they didn't make Chrome work this way. It also means I can't unbind "ctrl-shift-q" from "quit_immediately_without_asking", because Google refuse to add an option to make it so that I can't accidentally fat-finger a C-w into something that ends my entire session. All keyboard shortcut problems disappear instantly if key bindings are configurable, however, without adding new options for each command.