you approach a bit confuse,
the function will display alert even nothing edited, can be annoying.
what about something like:

jQuery(document).ready(function() {
  var changed;
  jQuery('[name]').on('change input', function(){
    changed = true;
  });
  jQuery(window).on('beforeunload', function (event) {
   if(changed){
      return 'alert';
    }
  });
});

or around

I really appreciate the detailed work that has gone into this and for testing on multiple browsers. However personally I dont like this. IF it was only happening when some data was changed I might think differently but for it to happen all the time is just a pain

@Fedir @brianteeman Let’s say you try to edit an article. You click on the title in the list view and once you have the form you realize that this is NOT the one you want and you click the back button. Without throwing an alert (actually joomla is politely asking you to use save or cancel button) you will end up with a lock icon in the article, which means that you have to checkin that article (if you are allowed to do so!).
I hope this explains that this is not only for end users but also a way to keep Joomla admins out of the check in button!

You still get the lock icon with this popup if you click leave this page

@brianteeman Sadly thats true

@Fedik @brianteeman Implemented the check for changes! So the alert will NOT trigger if no changes made!

Just retested on a clean site and it didnt matter what I did I never got the popup

test
works good for me, now

but question about whether we need it,
maybe need some vote?

I still cant get it to work (but even if I did I would not be in favour of
this)

On 19 January 2015 at 13:38, Fedir Zinchuk notifications@github.com wrote:

test
works good for me, now

but question about whether we need it,
maybe need some vote? [image: ]

—
Reply to this email directly or view it on GitHub
#5815 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

@brianteeman Due to the way .change is defined in jQuery, this might not work in cases where the edited element hasn’t lost its focus (you have to click somewhere else in the page)

The change event is sent to an element when its value changes. This event is limited to elements, boxes and elements. For select boxes, checkboxes, and radio buttons, the event is fired immediately when the user makes a selection with the mouse, but for the other element types the event is deferred until the element loses focus.

From jQuery API

@dgt41 another suggestion use jQuery('form :input').on('changed input', function() { instead of .changed()
this will mark changes on input modification, not only when input lost focus

other thing I would use local variable instead of bother with form element, but like now also can be....

and for which reason you disable this feature if debug enabled ?

@brianteeman maybe you have debug enabled

@Fedik Disabled on debug was an old request from many PLT members, you can see the comments at #4773

@dgt41 so you know why it not very welcome feature?

@Fedik I think this is a welcome feature for average users. Advanced users, and devs dislike anything that gets in their way, I guess

I am setting this to needs review so that the CMS maintainers and PLT can decide if this concept is worth pursuing

Personally I like the concept (this isn't a formal PLT opinion ). However I'd make it much simpler. Just check if someone has altered the text in the textarea. I don't think changing other elements of the form is as annoying/time consuming to replace as the article itself.

I think that's a wonderful idea....however it does not work if you change text in the editor, category select (Chosen), or Publishing Dates (Calendars).

@anibalsanchez reading others people approach in the net, most of them serialize the form data on the page load and then compare the changes (if any). Also this will prevent another erratic behavior e.g. add a word and the delete it, right now this will count as changed form, although it isn’t. Maybe the best approach is to utilize some jquery plugin for this

#dgt41 From my humble experience, I have created this https://github.com/anibalsanchez/jquery.saveform.js/blob/master/jquery.xtsaveform.js, based on jquery.saveform.js. It can be tweaked to include hidden fields (.xtd-save-this class).

I am going to close this one, as there is little interest on improving UX.

As stated above, if it is activated with altered text I'm in favor of this.