[wp-trac] [WordPress Trac] #40432: Customizer: Should we stop contextually hiding features?
WordPress Trac
noreply at wordpress.org
Mon Oct 2 05:55:36 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: 4.0
Severity: normal | Resolution:
Keywords: | Focuses: ui
-------------------------+------------------------------
Comment (by westonruter):
Only if the things hidden are limited specifically to //sidebar
sections//. The active API is specifically defined to be about
hiding/showing things that are not contextually relevant to the current
URL being previewed, or for any other condition. For example, the new
Publish Settings has an `active` state that is tied to whether theme
previewing is being done and whether or not there are unsaved changes.
Additionally, in Homepage Settings, the homepage and page for posts are
contextual based on the choice for what to show on front. So if we wanted
to override the behavior of contextually hiding panels, sections, and
controls then this would have to be done on a case-by-case basis.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/40432#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list