WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#7069 closed defect (bug) (fixed)

Autosave does not work in TinyMCE's fullscreen mode

Reported by: mdawaffe Owned by: azaozz
Milestone: 2.6 Priority: high
Severity: normal Version: 2.6
Component: General Keywords: has-patch
Focuses: Cc:

Description

When writing in TinyMCE's fullscreen mode, autosave does not work.

No matter what I type, the same post content is being read by autosave and sent to the server via AJAX every time.

I believe the issue is that tinyMCE.triggerSave() does not work correctly in fullscreen mode.

Attachments (1)

7069.patch (731 bytes) - added by azaozz 6 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 azaozz6 years ago

  • Status changed from new to assigned

Yes, fullscreen mode is actually another instance of TinyMCE that runs on top of the old one, so the content is not saved in the same textarea.

The patch copies the content from the fullscreen editor and inserts it in the old instance before triggerSave().

azaozz6 years ago

comment:2 azaozz6 years ago

  • Keywords has-patch added

comment:3 ryan6 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [8037]) Enable autosave for fullscreen mode. Props azaozz. fixes #7069

comment:4 zaneselvans5 years ago

I'm running WP 2.7 with Turbo/Google Gears enabled, and I just ran afoul of this, or another similar bug and lost an entire morning's worth of writing. During the editing session (in full screen mode) my network connection cut out, and I had to re-connect, potentially changing my DHCP address. When I attempted to return to normal editing mode (get out of full screen) I was asked to log back into WP, and found to my dismay that none of the changes which had been made in full-screen mode had been saved.

It would be very nice if the autosave process were more robust, and if, perhaps, one could get feedback in fullscreen mode as to whether autosaving is taking place (or failing), allowing one to take precautions before changing views (like, a quick ctrl-A, crtl-C just to be safe).

Note: See TracTickets for help on using tickets.