From 33622d9179ad2e371ab56298ca42fcb17b6ccb80 Mon Sep 17 00:00:00 2001 From: Weston Ruter Date: Thu, 11 May 2017 06:41:25 +0000 Subject: [PATCH] Customize: Wait for `processing` state to clear before starting to `captureSettingModifiedDuringSave`. See #32941. Fixes #40729. git-svn-id: https://develop.svn.wordpress.org/trunk@40627 602fd350-edb4-49c9-b593-d223f7449a82 --- src/wp-admin/js/customize-controls.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/wp-admin/js/customize-controls.js b/src/wp-admin/js/customize-controls.js index d340a1ba04..f3210e8491 100644 --- a/src/wp-admin/js/customize-controls.js +++ b/src/wp-admin/js/customize-controls.js @@ -4420,11 +4420,12 @@ function captureSettingModifiedDuringSave( setting ) { modifiedWhileSaving[ setting.id ] = true; } - api.bind( 'change', captureSettingModifiedDuringSave ); submit = function () { var request, query, settingInvalidities = {}, latestRevision = api._latestRevision; + api.bind( 'change', captureSettingModifiedDuringSave ); + /* * Block saving if there are any settings that are marked as * invalid from the client (not from the server). Focus on