To reproduce...
You need at least 2 menus with nodes.
(use navigation + 1 custom menu for example)

Put both jquery blocks wherever on page.

Now navigate in the first menu (most leftside and upper).
The selected page stays OPEN in the menu.. active_trail is on every element correctly.

Now navigate in the second menu (most rightside or below first menu)
The selected page does not stay opened. The first parent has no active_trail.

So only fist menu always gets correct active trail class.. and no other jquery menu gets them correct.

Do it on garland an ull see.
I dont know it the 6.20 core is broken or the module, but i think its the module because regular menus work in whatever order they are.

Comments

Pat Redmond’s picture

Pat Redmond CreditAttribution: Pat Redmond commented
Status: Active » Postponed (maintainer needs more info)

Can you confirm that this still happens with the latest dev release?

finedesign’s picture

finedesign CreditAttribution: finedesign commented

I don't know if we're dealing with the same issue, but only see an "active" class for the menu item associated with the current page. I have three levels in my menu and when on the bottom child level, both parents do not contain "active" classes. Isn't jQuery menu supposed to add an active class to the whole trail?
Ah, sorry. I'm in Drupal 7.20.