As a web application developer, I second the motion to officially thank the Chrome development team for this. "Backspace" triggering "back" is a usability disas

As a web application developer, I second the motion to officially thank the Chrome development team for this. "Backspace" triggering "back" is a usability disaster, and not only for inexperienced users. We recently had issues with a 3rd party editor widget losing focus due to a bug, which led to people accidentally triggering "back" and losing their data (it was a rich text field, so you can imagine how much of a problem that was). Sure, the problem here was the widget, but using such a commonly pressed key as the shortcut for a potentially destructive operation is a recipe for disaster. More advanced users have the option to use a custom extension, or even mouse gestures. Just develop an "Advanced Chrome" plugin and the problem will be solved. As a side note, it's interesting to see how such a small change (which, as mentioned above is even reversible) can trigger such an outcry. I've read stuff such as "I've been using this shortcut for 20 years" or "I don't want an extension"... are those even arguments? Yes, applications should be "user-centred" but the "user" here is a collective of thousands or millions of people with their own incompatible opinions. There is a (very good) reason for this change and I've seen zero achievable solutions that would not imply it.