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

 In observing this conversation, it seems like there are two viewpoints:

 1. Customizer controls should always be shown, because it's confusing to
 new users when they're sometimes missing.
 2. Customizer controls should be contextually shown, because they're
 distracting when they're not relevant to the current view.

 I'd suggest that both viewpoints are correct, ''depending on the use
 case''.

 If you're a new user, of course it's going to be confusing to have some
 settings conditionally displayed, because it assumes you know how/why/when
 they're shown vs. hidden.

 If you're an enterprise client, of course it's going to be distracting to
 have 50+ sidebars shown when they don't need to be. You use WordPress on a
 daily basis, and only want to see the controls you need to see because
 everything else is mental overhead.

 In this discussion, it seems like it'd be helpful to present a point of
 view based on the use case you'd like to optimize for, and acknowledge how
 your solution might solve the other use case too.

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