[wp-trac] [WordPress Trac] #34391: Harden panel/section UI code by removing contents from being logically nested (read: goodbye margin-top hacks)

[WordPress Trac]

#34391: Harden panel/section UI code by removing contents from being logically
nested (read: goodbye margin-top hacks)
------------------------------+--------------------------------------------
 Reporter:  westonruter       |       Owner:  delawski
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  4.6
Component:  Customize         |     Version:  4.0
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  ui, accessibility, javascript
  4.6-early                   |
------------------------------+--------------------------------------------

Comment (by westonruter):

 @delawski thank you. Compatibility with Customizer extensions that
 directly interact with the DOM is truly going to be a challenge. This is
 partly why I wanted to add the `early` keyword for the 4.6, to give plenty
 of time for themes and plugins to fix their integrations. As backwards
 compatibility is important, the big question here is whether the
 restructuring of the DOM in this way is so important that backwards
 compatibility should be broken.

 @celloexpressions You've done quite a bit with custom panels and sections.
 What do you think about the changes?

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