[wp-trac] [WordPress Trac] #28979: Customizer panels should have the same priority hierarchy as Sections

WordPress Trac noreply at wordpress.org
Mon Jul 21 23:58:19 UTC 2014

#28979: Customizer panels should have the same priority hierarchy as Sections
 Reporter:  mattwiebe        |       Owner:
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Customize        |     Version:  trunk
 Severity:  normal           |  Resolution:  duplicate
 Keywords:                   |     Focuses:
Changes (by celloexpressions):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


 #27406 is still open so that we can decide whether or not to do this (and
 specifically, see [https://core.trac.wordpress.org/ticket/27406#comment:48
 #27406 comment:48]). I'm still against it for UX purposes, and I don't
 think the implementation would be as clean, but I may be in the minority
 there. You probably understand the implications of the subclassing
 approach here better than most; in terms of API, sections and panels are
 treated as fairly distinct entities with `add_panel` vs `add_section`,
 `get_panel`, `remove_panel`, etc. that make the separate sorting of
 sections and panels clearer. I think if we'd gone with `add_section` with
 a `parent` parameter instead of the panel terminology, your point would be
 more significant.

 If we don't end up doing this in 4.0 but want to consider it again in the
 future, we can re-open this ticket, but let's keep the discussion there
 for now. I think a proof-of-concept patch could be useful in making a
 final decision here.

Ticket URL: <https://core.trac.wordpress.org/ticket/28979#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list