[wp-trac] [WordPress Trac] #28477: New Built-in Customizer Control Types

WordPress Trac noreply at wordpress.org
Mon Jun 9 19:19:08 UTC 2014

#28477: New Built-in Customizer Control Types
 Reporter:  celloexpressions        |       Owner:
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Appearance              |     Version:  3.4
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:  ui, administration
Changes (by celloexpressions):

 * keywords:  has-patch => has-patch dev-feedback


 [attachment:28477.diff] does pretty much everything I suggested in the
 ticket description. I'm not sure that we should do all of it (particularly
 the number & range parts), but it's all worth considering.

 The attached screenshot and test plugin demonstrate the purpose of the
 fallback type handler. This allows us to implicitly support all sorts of
 input types that devs can use with minimal effort. If, for example,
 someone needs a time or date field and only needs to support Chrome, they
 can do so quite easily and rely on the browser's support for that input
 type. Any of these input types is treated as a text input by browsers if
 the type is unrecognized.

 Currently, most developers would just create a text control for a url
 field, but with this proposal they could just as easily use `url`, taking
 advantage of potential improvements that the browser might implement for
 that specific input type (contextual on-screen keyboards, for example).

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

More information about the wp-trac mailing list