Weston Ruter 89f49aad80 Customize: Ensure that a setting (especially a multidimensional one) can still be previewed when the post value to preview is set after preview() is invoked. ... * Introduce `customize_post_value_set_{$setting_id}` and `customize_post_value_set` actions which are done when `WP_Customize_Manager::set_post_value()` is called. * Clear the `preview_applied` flag for aggregated multidimensional settings when a post value is set. This ensures the new value is used instead of a previously-cached previewed value. * Move `$is_preview` property from subclasses to `WP_Customize_Setting` parent class. * Deferred preview: Ensure that when `preview()` short-circuits due to not being applicable that it will be called again later when the post value is set. * Populate post value for updated-widget with the (unsanitized) JS-value in `WP_Customize_Widgets::call_widget_update()` so that value will be properly sanitized when accessed in `WP_Customize_Manager::post_value()`. Includes unit tests with assertions to check the reported issues and validate the fixes. Fixes defect introduced in [35007]. See #32103. Fixes #34738. git-svn-id: https://develop.svn.wordpress.org/trunk@35724 602fd350-edb4-49c9-b593-d223f7449a82		2015-11-21 02:51:57 +00:00
..
phpunit	Customize: Ensure that a setting (especially a multidimensional one) can still be previewed when the post value to preview is set after preview() is invoked.	2015-11-21 02:51:57 +00:00
qunit	TinyMCE: update to 4.2.7. Changelog: http://www.tinymce.com/develop/changelog/?ctrl=version&act=view&pr_id=1&vr_id=888	2015-11-08 02:31:31 +00:00