WordPress.org

Make WordPress Core

Opened 11 months ago

Last modified 4 months ago

#38077 accepted enhancement

Facilitating embedding customizer controls outside of sections

Reported by: westonruter Owned by: westonruter
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Customize Keywords: needs-patch
Focuses: Cc:

Description (last modified by westonruter)

Controls are currently assumed to be always contained within sections in the customizer. This makes it difficult to reuse the controls in other contexts, such as embedding multiple controls inside another control or embedding a control outside the context of the customizer entirely. This will facilitate embedding customize controls on the frontend for contextual editing without having to have the customizer sidebar open or even having to go into customize.php at all.

Some of the hacks required to get controls to appear outside of the customizer can be seen in https://github.com/xwp/standalone-customizer-controls

The Media control in particular needs to be updated to remove the logic resize the player controls when the section is expanded. The embed method (used by widgets) also needs to not wait generally for a contained section to expand.

Key dependency for #29071 (Make it easier to include an instance of the Customizer outside of customize.php)

Depends on or is closely related to #37964 (Allow customizer controls to be encapsulated by accepting pre-instantiated settings)

Change History (8)

#1 @westonruter
11 months ago

  • Owner set to westonruter
  • Status changed from new to accepted

This ticket was mentioned in Slack in #core-customize by celloexpressions. View the logs.


11 months ago

#3 @celloexpressions
11 months ago

  • Priority changed from normal to low

This is low priority for 4.7, but will be needed eventually and should switch back to normal priority if we punt it.

This ticket was mentioned in Slack in #core by chriscct7. View the logs.


11 months ago

#5 @chriscct7
11 months ago

  • Milestone changed from 4.7 to Future Release
  • Priority changed from low to normal

Punting per bugscrub discussion

#6 @westonruter
7 months ago

  • Description modified (diff)
  • Milestone changed from Future Release to 4.8

This ticket was mentioned in Slack in #core by jeffpaul. View the logs.


4 months ago

#8 @jbpaul17
4 months ago

  • Milestone changed from 4.8 to Future Release

Per yesterday's bug scrub, we're going to punt this to Future Release.

Note: See TracTickets for help on using tickets.