[wp-trac] [WordPress Trac] #29572: Customizer: add a framework for rendering controls from JS templates
WordPress Trac
noreply at wordpress.org
Mon Sep 22 04:00:42 UTC 2014
#29572: Customizer: add a framework for rendering controls from JS templates
------------------------------------+-------------------------
Reporter: celloexpressions | Owner:
Type: feature request | Status: new
Priority: high | Milestone: 4.1
Component: Customize | Version: 3.4
Severity: normal | Resolution:
Keywords: has-patch dev-feedback | Focuses: javascript
------------------------------------+-------------------------
Changes (by celloexpressions):
* keywords: has-patch => has-patch dev-feedback
Comment:
Specific dev-feedback-y questions:
- How do we feel about the concept of "registered control types"?
- Should we go ahead and implement render-container logic, but leave it
unused in core, or is it okay to indicate that things will change a bit
here in the future to accommodate that? (again, that would be necessary
once we formalize the ability to dynamically render controls, and
eventually do that for all controls, via ajax for unsupported types).
- Can/should we always export all class variable to json, or should it
remain a whitelist, with the requirement of adding custom class variables
in subclasses (that's what [attachment:#29572.diff] does)?
- Should we check if the string passed is a WP_Customize_Control before
registering it, or okay to assume that it's fine?
I'd like to wait on further work on #21483 so that we can leverage this
there, hence high-priority. Would be ideal to get this in sooner rather
than later to facilitate additional feedback and further integrations in
various core and third-party controls. But not really reasonable to
demonstrate this outside of core via a plugin, much like how the Panels
API was introduced.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/29572#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list