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

 Nice work with those mockups @JoshuaWold

 My preference would be Option 4. I think those eyeball icons on Option 5
 make things confusing. I would've thought that if it had an eyeball icon,
 that means I can see/preview that widget, whereas the mockup seems to
 indicate the opposite.

 I wouldn't bother about italicising the Widget Area names (in Option 4) as
 they're almost indistinguishable from the non-italicised names anyway, so
 they don't add much benefit to the UI.

 @zoonini brings up a good point, which I've also mentioned before, it's
 important that you don't actually stop people from editing the widgets,
 just because they're not currently shown in the preview. Kathryn's
 suggestion of changing the wording is a great idea and makes it clearer
 that they can still edit the widgets, they just wont see it previewed
 until navigating to another page.

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