3 ms·
"But generally, applications that accept user input and cannot save it for some reason ask for confirmation to lose it, so users won't lose it accidentally." Y
by galacticpony 10y ago
"But generally, applications that accept user input and cannot save it for some reason ask for confirmation to lose it, so users won't lose it accidentally."
You'd think they do, but they don't, at least not all of them. The problem isn't the properly designed webapps, it's the improperly designed ones. That's what you somehow don't understand/recognize.
Also, the problem with the redirect happens on a certain popular bulletin board software that works without Javascript (and therefore doesn't provide such a prompt in the first place).
- zzzcpan 10y agoI was talking about desktop applications, not webapps, because web browser is a desktop application and is expected to behave like one. Webapps don't have to do anything.
- galacticpony 10y agoI don't understand your point, then. We are talking about web apps. Is Chrome supposed to alarm you when navigating away from any site with form input? How would it know if your changes are unsaved or not? (It can't)
- zzzcpan 10y agoIt can and they know how to implement it. There is a pretty clean distinction of where the user can input some data.
- galacticpony 10y agoThe only thing it could do is alarm you for navigating away from any webpage that has any form that has ever had input put into it. Also, the website could intercept the "go back" event for some purpose. Should the browser fire an alarm then, as well? Either way, it would be a terrible user experience. There's no notion of "unsaved" changes. There's the notion of form data that hasn't been submitted, which is entirely different. Many web apps don't use "submit" at all, ever.
- another-dave 10y agoChrome might not be able to, but the website can, surely? Why not leave it to developers to properly handle state within their application (e.g. by using history and 'beforeunload' functionality) rather than second-guessing it at a browser level?
- DonHopkins 10y agoThen the problem would ALREADY be solved, because all developers would already be properly handling state within their application instead of second-guessing it at a browser level. But they don't.