I have tested this item successfully on 0cb62a2

Back to the 2.5's

Works as described - Thanks

don't even remember how it was in 2.5.x :)

You forgot to check Hathor ;)

Joomla 2.5

if you want my honest opinion. i don't really like to make changes in hathor because IMHO is wasted time.

hathor can live perfectly good without the submenu ... hathor menus doesn't need to be like (and they aren't) isis menus.

yes just like 2.5. IMO in this case the 2.5 way is better

@andrepereiradasilva
I would say that everyone agrees with your about Hathor but as long as we don't have a real admin template respecting the a11y basics, we will have to deal with it.

and hathor with all the changes added still respects that a11y basics??

Anybody really tested?

Not what I said...
Just try to explain with my tarzan frenglish that as long as the goal of hathor was accessibility (not saying it reaches this goal) and as long as we have no other adequate response...
at least, that is what was explained to me

anyway, as i said this changes are not needed in hathor, as hathor doesn't have to add exactly the same menu as isis.

sorry, wrong button...

FYI just checked the admin control panel in a auto accessibility WCAG 2.0 test tool:

• Isis: 4 errors in WCAG 2.0
• Hathor: 2 errors in WCAG 2.0

Note: i know there are also manual tests there should be made and all pages need to be checked. just to prove the point.

no need to proove something known...

Ok then.

I have tested this item successfully on 0cb62a2

I am setting this to needs review so the maintainers can make a decision. I am assuming that there was a reason the behaviour changed from 2.5 and also a decision about it not being applied to hathor

is there a label "Needs review" to more clearly identity the PR that needs review by a mantainer so they don't go inside the black hole?

Right now the Needs Review is only in the issue tracker not github. (I will ask and see what they think about adding it on github as well.)

During the sprint next month I will be forcing the plt members there to make a decision on all the needs review issues ;)

gulp

I can add the label on github and manually update those issues there as well (if you want)

Ok I have no clue what the original intention was by the UX team in 3.x - but in my opinion less clicks (i.e. submenu's) is better. So I'd rather keep what we have and amend the language strings to be honest!

This kinda makes the hathor question redundant. But my opinion there is that Hathor is a separate template with different styling so it doesn't have to visually be exactly in sync with ISIS, however it does need to work..... so whatever makes sense - in this case I'd probably have applied it there as it's dead simple and it's easier to maintain them in parallel. But it doesn't mean as a rule of thumb every single change to ISIS must be applied to Hathor.

ok so this is a no go. fine.