It is currently possible to make certain menu items appear as their own child item. This allows their pages to be navigated to without forcing the user to double-click on the parent item.

However, as the entire functionality of the module is disabled when the user does not use Javascript, this can be confusing: The extra menu item leads to the same page as its parent for no clear reason.

This could for example be solved by making the duplicated items invisible by default, and changing the visibility in Javascript. That way, they only show up when the menu is actually dynamic.

Comments

brmassa’s picture

Arancaytar,

This module depends on JS. Also, almost all new browsers (including mobile ones) have a very good support for JS.

So, we dont need to worry much about this extra menu items.

regards,

massa

brmassa’s picture

Status: Active » Closed (won't fix)

Arancaytar,

This module depends on JS. Also, almost all new browsers (including mobile ones) have a very good support for JS.

So, we dont need to worry much about this extra menu items.

regards,

massa

cburschka’s picture

Priority: Normal » Minor
Status: Closed (won't fix) » Active

If we can assume that all users support Javascript, then what is the point of graceful degradation? I would say that an ideally accessible site does not just "not break" without JS, but does not even display features that would not work. I'll readily admit that this is minor and a feature rather than a bugfix, but it shouldn't be discarded out of hand.

Especially since this is trivial to implement: display:none on the extra items, then do a collective display = block in the page-loading code.

If there is a valid concern with this, it would outweigh the minor benefit, but I don't see any right now. It's an improvement without side effects.

brmassa’s picture

Status: Active » Fixed

Arancaytar,

your right, sorry. implemented

regards,

massa

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.