[wp-trac] [WordPress Trac] #21413: Add Customizer to Appearance submenu as first item

WordPress Trac wp-trac at lists.automattic.com
Mon Jul 30 19:03:11 UTC 2012


#21413: Add Customizer to Appearance submenu as first item
-------------------------+------------------------------
 Reporter:  jane         |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  UI           |     Version:  3.4.1
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |
-------------------------+------------------------------

Comment (by nacin):

 Our current menu paradigm (beyond just the API) is that the top-level link
 must be the same as the first submenu item.

 Aside from being a well-established paradigm, this is also important for
 accessibility purposes. You click the first item to open the submenu (if
 you don't use the flyout), as an alternative to the old click-to-expand.

 A few issues with this. One, this means clicking "Appearance" will open
 the customizer — this isn't good, because it opens a completely different
 workflow. While assuming you want to customize your theme is a safe
 assumption more often than it is wrong, the separate workflow can be
 jarring if you did want to end up on themes.php.

 Two, the Customizer isn't always available. At the moment, this means you:
  1. have JS enabled, which we need to detect in the browser, client-side.
  2. you are not using IE7, which we *could* detect server-side, but
 currently use feature detection in JS, which is preferred.
  3. are not using IE8 or IE9 if you have a domain-mapped front-end (and
 your plugin doing the domain mapping does not un-map for the customizer).
 We currently detect this server-side (to check the URLs) and then feature
 detection in JS.

 That the Customizer isn't always available means "Appearance" will
 sometimes open up a regular window and other times the customizer, and it
 won't be easy to establish when exactly it should link to one or the
 other. ryanhellyer's code works around this to some extent, but overall
 the request ain't pretty to implement.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21413#comment:7>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list