[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 dlh):

 I'd like to follow up on @Travel_girl's question:

 > Could we point to the template, where the widget is displayed?

 For those who have conducted user tests with the Customizer: Are there
 scenarios when it would be helpful to display a notification that includes
 something like "[#link-that-goes-to-the-page-in-the-customizer-preview
 Visit a page on your site where you can preview this setting]"?

 As a developer, a sketch of the technical workflow could be:

 1. I could tell the Customizer a URL where my control could be previewed
 (e.g., `sample_permalink_callback`).

 2. I also could tell the Customizer whether the link should display (e.g.,
 the preview is visible; no page exists; doesn't make sense to suggest a
 link...).

 3. The Customizer would use (1) and (2) to determine whether to display
 the notification, and it would navigate the preview to my sample URL if
 the user clicks the link.

 Perhaps this has already been suggested and rejected, or it's technically
 infeasible (or maybe it's already possible).

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