Make WordPress Core

Context Navigation

Changes between Version 6 and Version 10 of Ticket #35855

Timestamp:: 02/25/2016 06:01:53 PM (9 years ago)
Author:: westonruter
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #35855
- Property Status changed from assigned to accepted
- Property Keywords needs-patch added; dev-feedback removed
- Property Owner changed from DrewAPicture to westonruter
- Property Type changed from enhancement to task (blessed)

Ticket #35855 – Description

-                      v6
+                      v10
+(The following description is stale. Instead of adding a method to determine whether Selective Refresh is active, it can instead be always active but specific components can opt-in for support as required: specifically widgets.)
+Instead of adding a method to determine whether Selective Refresh (#27355) is active, it can instead be always active but specific components can opt-in for support as required: specifically widgets.
 The working ticket for the [https://make.wordpress.org/core/2016/02/16/selective-refresh-in-the-customizer/ proposed] Selective Refresh feature for the Customizer is #27355, where, once merged, a bunch of WET code will be merged that checks for selective refresh support.
+Currently `isset( $this->manager->selective_refresh )` is used to choose between the 'postMessage' and 'refresh' transports in a bunch of different places.
+Namely, `isset( $this->manager->selective_refresh )` is used to choose between the 'postMessage' and 'refresh' transports in a bunch of different places.
+In speaking with @westonruter, seems like a `WP_Customize_Manager::is_selective_refresh_enabled()` method or similar might be in order. I opted to create this ticket for discussion so as not to hold up the pending merge.
+Instead, there can be specific theme support and widget opt-in for selective refresh. See code in the original Widget Customizer plugin for reference: https://github.com/xwp/wp-widget-customizer/compare/without-partial-previews