Hi Weston,
Thanks for your quick reply.
While I can understand why it was done, I don’t believe that its very good for usability or UX.
When you’re setting up a new theme, you usually have no idea of what Customizer options are available to you until you actually go into the Customizer and look around. I’ve never seen any theme documentation that specifically lists all the Customizer options available to you.
If the Customizer hides panels from you, how are you supposed to know they’re available? By hiding panels your forcing people to browse to every single page in their site, just so they can make sure that they haven’t missed any options in the Customizer.
When you’re setting up a site, a lot of the time you know what you want to appear in the sidebar. If there’s multiple sidebars, ones that only appear on Single Posts for example, even if you know that this sidebar exists, you’re making the whole process considerably slower as you’re forcing people to navigate to another page just so they can actually see that Customizer option. If people want to be able to add Widgets to a sidebar without bothering to preview them, why is that an issue? That’s entirely up to them. WordPress is now forcing you to only work a certain way. i.e. You MUST preview this page or I wont show you the option.
I’ll be interested to see where Ticket #39087 goes as this obviously raises the same issue.
In Ticket #33052 (which is now closed) you mention you mentioned that:
Customizer: Always show Widgets panel initially if sidebars are registered; show notice to users in panel if no widget areas are in current preview.
It also lists a ticket for the fix, but this doesn’t actually look like it’s been implemented. There’s no notification that a Sidebar is available, but nothing in the current view. The sidebar is simply hidden. If it was implemented, it seems like the fix has basically been overridden with the decision to hide the sidebars altogether, which seems like a step backwards.
Ticket #27405 seems to go hand-in-hand with ticket #39087, but it’s been opened for over 3yrs now. Is anything going to happen with this one?
I raised a similar issue on the beta forum when I was testing 4.7 and TwentySeventeen. I had a back-n-forth discussion with Mika and although nothing actually happened about it, it was some consolation when Mika said that this functionality was theme specific. I was disappointed when I noticed today that it’s not actually theme specific and that this functionality has actually been implemented in the core Customizer functions.
With all that said, at least there’s a filter that disables this functionality. So thanks for showing me that. I still question why hiding options is the default though as it makes it extremely confusing for the end user and also more time consuming when updating theme options, by forcing people to browse to different pages in their site.