3 ms·
> which is easily fixed with window.onbeforeunload prompt. It would be nice, but realistically, you can't expect every single website to get everything correct
by viraptor 10y ago
> which is easily fixed with window.onbeforeunload prompt.
It would be nice, but realistically, you can't expect every single website to get everything correct. If you could force it on people to implement a correct onbeforeunload behaviour, backspace wouldn't be a problem. But you can't force it, and you can't force it to be correct. (webapps are pretty complicated these days "are there any unsaved changes" is not always a trivial question)
This way a class of errors has been removed rather than forcing everyone to think of it in many places.
- another-dave 10y agoI think it's just provided less incentive for developers to handle 'unhappy paths' within their app — there are still plenty of ways that you'd want a webapp to handle unexpected closure (e.g. user accidentally closing a tab, browser crashing, network connection dropping before save takes place). If an app is handling these states fluidly they will likely get the 'accidental back' problem solved for free.