What I meant when I said
Quote:
Would be great if .current_page_parent and .current_page_ancestor could be introduced in a future revision of the theme.
|
was that it would be great if Atahualpa could automatically do that based on the style we chose for the parent item, without having to use CSS inserts.
We would define the "parent" CSS in WP and current-menu-ancestor would be used to apply that style to the parent elements at every level.
Regarding the bug you mention, I'm not experiencing it with the ata theme.
Here is my hierarchy:
A
-B
A
-B
-B
--C
--C
-B
A
A
And here are the classes I have (minus the menu/page-item-xxx):
Level A item, parent of level B and level C items
Code:
rMenu-expand menu-item menu-item-type-post_type current-menu-ancestor current_page_ancestor
Level B
Code:
menu-item menu-item-type-post_type
Level B item, parent of level C item
Code:
rMenu-expand menu-item menu-item-type-post_type current-menu-ancestor current-menu-parent current_page_parent current_page_ancestor
Level C item selected
Code:
menu-item menu-item-type-post_type current-menu-item page_item current_page_item
"current-menu-parent" cannot be used in this case, because it doesn't exist in level A.
"current-menu-ancestor" is placed exactly where it should and can be used to highlight the parents of the selected item.
The "problem" I'm having now is that Atahualpa highlights every sub-element of a chosen menu item using what we've defined in WP as the parent style and the same happens when using inserts for current-menu-ancestor. But I guess that's more of a CSS problem.