DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43628>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43628 ------- Additional Comments From [EMAIL PROTECTED] 2007-10-25 07:22 ------- (In reply to comment #2) > this capability might be highly desirable for other editors, too. A big + > > maybe we could implement a generic onunload() handler that will run an > editor-specific callback if provided (similar to the way richard implemented > the > backspace catcher in an editor-agnostic way). another big + > > what does an onunload() handler need to do? > * catch the onunload event and prevent leaving the current page. > * provide a message that informs the user of unsaved data and allows to > "leave", > "save and leave", "return to editor". > > "leave" must remove the lock on the document and then execute the previously > caught navigation event. > "save and leave" will have to signal the editor (invoke its save callback) and > then navigate away. > "return" just eats the unload event and return to the editor. Another big + for the idea. The problem with document.onbeforeunload is, that it triggers a predefined screen that can only partially be modified. It would be very nice to have the three options you described - but I did not find a way to display and process a custom screen on an onbeforeunload event. Maybe there is a better way to do the event handling than using window.onbeforeunload. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
