[wp-trac] [WordPress Trac] #40432: Customizer: Should we stop contextually hiding features?

[WordPress Trac]

#40432: Customizer: Should we stop contextually hiding features?
-------------------------+------------------------------
 Reporter:  melchoyce    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by westonruter):

 @dlh I think your second point is captured by the current
 `active_callback` API. The first point, introducing a callback function
 where a developer could indicate a URL where the control/section/panel
 could be managed seems like the primary new piece. For the third point, I
 think whether or not the control/section/panel is displayed even when not
 contextual would need (per my previous comment) to be an opt-in thing, and
 this opt-in could signal that a notification like you describe could be
 shown.

 My main concern with this is developer adoption. If the main use case is
 indeed widget area sections, then developers would have to work out a
 sample URL for where templates get chosen that render the given sidebar.
 That seems like it could be somewhat of a tedious task to ask of theme
 developers.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40432#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform