From d67109800359d0c36d4a4b65708b15d44a7c862f Mon Sep 17 00:00:00 2001 From: Weston Ruter Date: Thu, 9 Nov 2017 04:14:46 +0000 Subject: [PATCH] Customize: Ensure `autosaving` message gets sent to preview after initial change when `saved` state is first dirty. Amends [41667]. Fixes #42475 for trunk. git-svn-id: https://develop.svn.wordpress.org/trunk@42136 602fd350-edb4-49c9-b593-d223f7449a82 --- src/wp-admin/js/customize-controls.js | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/wp-admin/js/customize-controls.js b/src/wp-admin/js/customize-controls.js index 5ff47c4998..0e4e5d0238 100644 --- a/src/wp-admin/js/customize-controls.js +++ b/src/wp-admin/js/customize-controls.js @@ -9191,12 +9191,14 @@ api.unbind( 'change', startAutosaving ); // Ensure startAutosaving only fires once. - api.state( 'saved' ).bind( function( isSaved ) { + function onChangeSaved( isSaved ) { if ( ! isSaved && ! api.settings.changeset.autosaved ) { api.settings.changeset.autosaved = true; // Once a change is made then autosaving kicks in. api.previewer.send( 'autosaving' ); } - } ); + } + api.state( 'saved' ).bind( onChangeSaved ); + onChangeSaved( api.state( 'saved' ).get() ); /** * Request changeset update and then re-schedule the next changeset update time.