I'm not sure why it'd be hard. "If there's a dom element that's an input of any time, and the user has focused it at any point, ask for confirmation on page exit" would work fine. The only case where I can see it being an issue would be a site that uses a select element as a menu, but I've not seen any do that in years.
Re:Chrome removes Backspace to go back
by PunchTornado on Thursday May 19, 2016 @05:58PM
(#11734205)
I think it can easily get abused, just some hidden focused inputs
Browsers already have a pageUnload event that can block a user leaving until they confirm they want to. This would effectively be the same.
Or maybe like just disable it if there is something to lose ie there is a form and I entered something in it with the keyboard
That would be worse. Then the expected behavior (that backspace would navigate back) wouldn't occur because I'm filling in this form. Even though I've left the field (so backspace is captured by the tab and not the form field) and have decided to abandon the comment and go back to reading the thread.
you can just say "Cancel" or "Navigate away" in the dialog that comes up
if you have written a long paragraph it shouldn't just be lost because you accidentally pressed a key on your keyboard
I do wish they had mad a user configurable flag rather than forcing people to use plugins to re-acquire functionality they had before.