[wp-trac] [WordPress Trac] #33687: Customizer: Widgets x Menu inconsistencies

WordPress Trac noreply at wordpress.org
Sat Apr 16 20:18:07 UTC 2016


#33687: Customizer: Widgets x Menu inconsistencies
-------------------------------+-----------------------------
 Reporter:  pavelevap          |       Owner:  SergeyBiryukov
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Customize          |     Version:  4.3
 Severity:  normal             |  Resolution:  worksforme
 Keywords:  needs-patch close  |     Focuses:
-------------------------------+-----------------------------
Changes (by celloexpressions):

 * status:  accepted => closed
 * resolution:   => worksforme
 * milestone:  Awaiting Review =>


Comment:

 To summarize:
 > Button: Add a Widget (singular)
 > New section title: Add a Widget (same string)
 > Customizer Menu:
 > Button: Add Items (plural)
 > New section title: Add Menu Items (different string)
 > I would change "Add a Widget" to "Add Widgets" and maybe use two
 different contexts (button x title can be different in some languages and
 for menu we have two different strings).
 The singular vs. plural is because menus add multiple at a time, while
 widgets add one at a time.

 > I also do not understand why new panels with widgets and menu items have
 title section when they are not visible?
 This is used for the mobile view, and provides back-navigation. The main
 panel header is visible on larger screens, so we don't need an additional
 header in the add- panels.

 > And one more glitch, everytime I open Customizer, Widgets panel is
 loaded a little bit later. I tested some other websites and it looks like
 it is waiting for something (Menu panel works well).
 See #33052.

 > Add Widget vs. Add a Widget
 I think this is because the "Add Widget" button is used with respect to a
 specific widget, while "Add a Widget" is to open the panel where a widget
 can be selected, then added (also with the "Add Widget" text for screen
 readers, I think). If this needs translator contexts for clarity, let's do
 a new ticket for that since this one is getting a bit confusing.

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


More information about the wp-trac mailing list