[wp-trac] [WordPress Trac] #14701: HTML markup inconsistency in menus

WordPress Trac wp-trac at lists.automattic.com
Thu Aug 26 07:00:48 UTC 2010


#14701: HTML markup inconsistency in menus
--------------------------+-------------------------------------------------
 Reporter:  jneuenhaus    |       Owner:                                                                                   
     Type:  defect (bug)  |      Status:  new                                                                              
 Priority:  normal        |   Milestone:  Awaiting Review                                                                  
Component:  Menus         |     Version:  3.0.1                                                                            
 Severity:  trivial       |    Keywords:  markup, html, css, menus, drop down, current-page-ancestor, current_page_ancestor
--------------------------+-------------------------------------------------
 Just a heads up on a minor inconsistency with the menu HTML classes.


 == Summary ==

 In the source, menus have the following markup:

 {{{
 With a dropdown: li.current_page_ancestor
 With no dropdown: li.current-page-ancestor

 }}}


 == Detail (Steps to Reproduce) ==

 One menu exists with two top-level pages, called A and B. Both have child
 pages, but only page A will display a drop-down menu. When you are on a
 child of page A, you will find:
 {{{
 li.current_page_ancestor
 }}}
 But when you are on a child of page B, you will get this:
 {{{
 li.current-page-ancestor
 }}}


 == Commentary ==

 This currently requires you to target both versions to get consistent
 styling, JavaScript functionality. Could be a "feature", if you wanted to
 identify the list item without a drop down menu, but semantically, it
 could be done in a cleaner way.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14701>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list