UI.Web - Show a confirmation dialog when a user leaves a page with modified data or changes the current object

Thanks for this useful feature.
Is this a Javascript dialog box, or a embedded popup window?
I'm asking this because Chrome/Firefox may ask users to ignore consequent Javascript dialog boxes.

@James: This is a native browser dialog shown via the 'confirm' JavaScript  function.

Thanks Dennis for your confirmation! That is good, because Outlook.com uses the same technology to prompt users (although Chrome will still show a checkbox to prevent consequent confirmations).

It would be fantastic to have it part of 12.2. Would request you guys to squeeze in this highly requested suggestion.

The solution provided by Q362121 which Dennis linked above is… limited. Please implement a real solution soon! Users have come to expect such behavior from web sites.

I agree with Steve. Few of my users find solution of Q362121 little annoying. I guess many like me would prefer to have a proper user friendly solution. Thanks

Sometime after my last post it occurred to me that two things should be clarified.
First, Anatol commented on the first post some 4 years ago that the customer was requesting inconsistent behavior for just the prev/next buttons. Generally we customers are not requesting inconsistent behavior. We want the user to be asked if they want to save changes when leaving the current page in any way that would lose changes.
Second, over the past several years a growing distinction has come about between a couple of different types of websites. For sites with little data entry (shopping, news, some forums) it might be acceptable to take the "you left the page, you lost your changes, don't do that again" attitude. However, it is increasingly common for users to be using line-of-business web sites where they spend an extended amount of time and where at least some of them put a lot of effort into data entry. XAF is very suited to the development of such sites. EXCEPT for this glaring shortcoming. It is not acceptable to brush this off with internal customers who invest a large amount of time in data entry.
At the vary least, could DevExpress support develop a better Controller than the one in Q362121?

I agree with Steve Curry. Hope a 'CTP' version (if it's not mature enough to be 'beta') can be available in v13.1, such that we can provide feedback to DevExpress XAF Team.

We're using XAF for over a year now and implemented several LOB applications that are now in productive use, a next one is on the way. The missing "unsaved Changes Warning" has always been a feature customers requested after the first few clicks. Of course they did, it is a basic principle in data entry application to warn the user before he loses all his changes by mistake.
However, I don't think DX will ever implement this feature. It has been requested from the very beginning (YEARS AGO) and it just does not seem to be somewherere near "top priority". It looks like a lot of refactoring work was done for the new 12.2 realease but no "unsaved changes" feature…
@Steve: I like the "glaring shortcoming" bit !!!

Hi guys,
I'm the OP in Q362121. First off, I'm well aware of the solution I've provided is more of a kludge, instead of a proper solution. But, I had to have something to prevent my users from losing their edits. So, I've put together that controller as a stopgap measure.
If you click show all comments link under the solution, there is a slightly better version which also handles the aggregated details.
Like you guys, I'm also awaiting a solution from DX.
Regards,
Hakan Çelik

Is it possible that this functionality isn't vital to anyone else and it's not implemented for 6 years now?
I believe I just can't find where it's implemented. The solution in eXpand Framework doesn't seem to be complete nor does it have to be imho. For me it doesn't check changes of collection objects and it doesn't check if the browser window is closed by means of javascript. One could expect such things to be handled by the framework.
Regards,
Andreas Fasching

+1 vote for this feature

It is must-have feature.

This is six years old; it will never come, we have to live without it

Indeed it's a must have feature for anyone who cares about data loss and wants to operate a professional web application.
I suppose every Devexpress Web-XAF customer in the aforementioned group "lives with" some home-brewed solution. In my case the solution is a combination of javascript and the suggestion mentioned above but this doesn't work in a very nice way. I like to deliver high quality software, that's why I've choosen Devexpress components for nearly all my projects. You promise to deliver high quality software and stunning support which proves true most of the time. That's why I sometimes wonder about tickets that are very old, highly requested and seem to be "forgotten" even if quite a lot of people vote them up. I don't mean to offend anybody here but I still wonder why Devexpress doesn't pay too much attention to the basics of it's products. Is there something we as customers do wrong with reporting an issue or is this issue not requested enough compared to the other ones?