[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:  4.0
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui
-------------------------+------------------------------

Comment (by joyously):

 This discussion includes most of the reasons why I do not like the
 Customizer.
 I review a lot of themes. The first thing I do after activation is set up
 widgets -- in the admin page, not the Customizer. It is easy to see all
 the widget areas and drag the widgets I want to the areas I want. One of
 the comments I give to theme authors is to improve their widget area
 descriptions so that the user can tell when and where they are shown (no
 preview needed and it's a requirement to document theme features). I also
 have told authors that I put widgets into an area, and visited all the
 pages and never saw those widgets, so they should not register the widget
 area until it is enabled, because that is confusing for the user to
 configure a widget area and not be able to see it on the site.

 At the end of my review testing, I go into the Customizer to test that all
 the options work and have default values. But I don't ever go to the
 Widgets section due to how it works (and I've already configured them).

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