[wp-trac] [WordPress Trac] #23960: Trigger local autosave when full save is initiated

[WordPress Trac]

#23960: Trigger local autosave when full save is initiated
--------------------------+--------------------
 Reporter:  markjaquith   |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  high          |   Milestone:  3.6
Component:  Autosave      |     Version:  trunk
 Severity:  major         |  Resolution:
 Keywords:                |
--------------------------+--------------------

Comment (by azaozz):

 Trying to reproduce, may be missing something after step 3:

  1. Open the post.
  2. Kill the server.
  3. Immediately add text then save.

 At this point the browser tries to submit the form. As the server is not
 available, it fails and shows its "Unable to connect" or "Oops! Google
 Chrome could not connect..." screen.

 If the user clicks the browser's Back button, the Edit Post screen is
 shown again (from browser cache), local autosave kicks in, compares the
 content and shows the restore notice if different. However if the browser
 (tab/window) is closed, the local autosave data is removed as we use
 sessionStorage.

 Navigating away (to another site), restarting the server, then navigating
 back to the same post in the same browser tab/window also triggers the
 restore notice.

 Currently there is some debug logging to the browser console. When loading
 a post you can see the stored content (if any). When saving, you can see
 the saved content.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23960#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software