[wp-trac] [WordPress Trac] #30251: Customizer inconsistent contextual behavior

[WordPress Trac]

#30251: Customizer inconsistent contextual behavior
--------------------------+-----------------------------
 Reporter:  dgwyer        |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Customize     |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When adding more than one contextual customizer control with I'm seeing
 inconsistent behavior.

 For example, I'm using the bare bones theme created by Otto available
 here:
 http://ottopress.com/2012/theme-customizer-part-deux-getting-rid-of-
 options-pages/

 All I've done in functions.php is to add two 'active_callback' lines, one
 for each customizer control:

 {{{
         'active_callback' => '__return_false'
         'active_callback' => '__return_true'
 }}}

 Using these core WordPress callbacks only one of the controls should be
 visible but when the customizer loads both controls are visible.

 If you remove one of the controls in functions.php then the remaining
 control is visible (or not) depending on the contextual callback return
 value, as expected.

 Note: In full themes this issue seems to be mainly when the customizer
 first loads. When clicking links inside the customizer preview window the
 customizer controls seem to respect their contextual settings, apart from
 the initial load.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30251>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform