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

WordPress Trac noreply at wordpress.org
Thu Apr 13 07:32:43 UTC 2017


#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 Travel_girl):

 > > This is tricky one. I have had also other feedback when not using
 contextually hiding widgets for example: "I'm adding a widgets but I can't
 see them on the preview. Theme is broken".

 This was my concern as well. So we should not display the non available
 Widget-Areas and Settings like the available ones.

 So what about grey then out and write the note, that this setting has be
 edit on an other view. I think it would be better also to point to the
 site, where you can edit, but if this is not possible the grey out would
 at least help to understand how the customizer works.

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

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


More information about the wp-trac mailing list