Opened 3 years ago
Closed 3 years ago
#14027 closed defect (bug) (duplicate)
Inconsistent menu markup makes styling very difficult
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Menus | Version: | 3.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
When inserting a menu like so:
<?php wp_nav_menu(array( 'theme_location' => 'header', 'container_class' => 'header-menu', 'container_id' => 'header-menu', 'depth' => 1, )); ?>
The result markup looks like this:
<div id="header-menu" class="header-menu"><ul id="menu-header-nav-menu" class="menu"><li id="menu-item-66" class="menu-item menu-item-type-post_type">...
Unless the menu is empty/undefined... In this case, you get the following:
<div class="menu"><ul><li class="page_item page-item-60 current_page_parent">...
This makes menu styling overly complicated...
In addition, the container parameter gets ignored if an empty string is entered. So there is no means to get rid of the useless div.
Change History (4)
Cool! It doesn't get rid of the latter, let alone insert the similar classes, when the menu is not configured however.
- Milestone Future Release deleted
- Resolution set to duplicate
- Status changed from new to closed
Seems so
Note: See
TracTickets for help on using
tickets.

container = false will rid the container.