User tests: Successful: Unsuccessful:
Pull Request for Issue #46364 .
Replacement for #46397 (same code that is tested, but moved to previous branch)
Introduce a new class (nav-active-open) for the default menu, allowing control over whether submenus are opened automatically on page load for the active menu item.
Caution
This functionality should not be activated by default without an additional class for all default menus, as it may not be desirable in various other module positions.
Example - Cassiopeia menu position

Additionally updated the toggleSubMenu method to use optional chaining when setting the aria-expanded attribute, preventing errors if the target element is missing.
sidebar-rightDefaultStep 1
Help -> WorkflowsStep 2
nav-active-openHelp -> WorkflowsImportant
For this to test an update of the media asset is required, please use the prebuilt packages or run npm install.
Should always be collapsed - with and without the class.
Step 1
Submenu with menu entry Workflows should be always collapsed (without the class).
Step 2
Submenu with menu entry Workflows should stay open on new page load if Workflow is the current active item (with class set).
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | JavaScript Repository NPM Change |
| Labels |
Added:
NPM Resource Changed
PR-6.0-dev
|
||
| Labels |
Added:
RTC
|
||
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-11-10 23:18:48 |
| Closed_By | ⇒ | softforge | |
| Labels |
Removed:
RTC
|
||
This works for the active sub menu. We should have a fix to achieve all submenus open (as it behaved before Joomla 6). E.g. look at https://www.dgcsh.ch/dgcsh/sitemap.html . The first sub menu on top level (and it's childs) are open, the further sub menus on top level are closed.
Unfortunately, I only noticed this fundamental change now, as I mainly work with my own template overrides and therefore don't regularly use the default behaviour of mod_menu.
The new solution makes technical sense. However, making it the default and replacing the previous behaviour was, in my opinion, a poor architectural decision.
The traditional menu with permanently visible, nested lists is well-established, intuitive and follows common web standards. It has one particularly important advantage for vertical navigation: the navigation hierarchy remains visible even on subpages. Users can immediately see where they are within the website and which content belongs to the current section.
This type of navigation is mainly used on larger websites, which is probably why the problem doesn't become apparent immediately. We actually had discussions about this in the JWC recently, in the context of the documentation.
The new approach also introduces a UX issue: the menu item and the toggle button serve different purposes. One navigates to a page, while the other expands or collapses the submenu. In many modern navigation designs, clearly distinguishing these two elements visually is difficult. Underlining links in a navigation menu is hardly a desirable solution either.
The new behaviour makes sense for horizontal dropdown navigation. For vertical navigation, however, I consider it only partially suitable.
The old approach may not have been particularly sexy or modern, but it was robust, stable, intuitive and accessible. I find it a real shame that this proven option has now been removed. In my view, the new solution should have been introduced as an additional option, rather than replacing the existing default behaviour.
Thank you @LadySolveig and the testers from the previous PR