[wp-trac] [WordPress Trac] #39335: Twenty Seventeen: customize-controls.js incorrectly assumes theme_options section is always present

[WordPress Trac]

#39335: Twenty Seventeen: customize-controls.js incorrectly assumes theme_options
section is always present
-----------------------------------+----------------------------
 Reporter:  westonruter            |       Owner:  davidakennedy
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  4.7.1
Component:  Bundled Theme          |     Version:  4.7
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+----------------------------

Comment (by ujxacoboh):

 What are the consequences of the customize-controls.js script in the
 Twenty Seventeen theme incorrectly assuming that the theme_options section
 is always present, especially in the context of plugins being able to de-
 register panels, sections, controls, and settings? How can the deferred
 pattern be used to address this issue, and what steps should theme
 developers consider to ensure compatibility and flexibility in handling
 customizer constructs when themes interact with plugins that modify
 default core constructs?

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