Non-leaf menu items not clickable in experimental navigation

PS: Would be super helpful to be able have a regular link for all menu items to be able to Crtl+Click or right-click for new tab.

I was going to create a new issue for this if you hadn't already.

Yes, this is very frustrating, actually. I've enabled the experimental nav on a couple of sites to see how well it works and this is one of the first things my colleagues pointed out.

Another example is that I frequently need to go to the top-level Views admin page. It's nice that all the views appear to click on when expanded, but that can get really long, so it's more convenient (and also a bit of a force of habit for me) to just go to the top level and look for the view from there. Part of the problem is because I use the admin toolbar module and admin toolbar tools to generate additional admin menu links that we like to have there as developers.

I don't seem to find any issues with the new Drupal Navigation in the Starshot protytpe project using core 10.3 beta, but it's not using the admin toolbar tools and thus only generating the standard core links for the admin menu. Will have to see how things work out with our sites once 10.3 is fully released and we start using the final version of the navigation sidebar.

Thank you for your reply @teknocat, I thought I was the only one with that heavy problem :)
Thanks for the confirmation.

This has been addressed in the navigation module which will be part of 10.3 and 11.0 👍

Once 10.3 is released we might remove the test integration from Gin and you can continue using the new version provided by Core.

Thank you @saschaeggi!

I'm closing this as fixed as we went a different route for the Core implementation and as a hotfix you can now use a modifier + Click to navigate to it. Thanks!

Sounds good all. In the meantime, I found the standard Gin sidebar works great until the new Navigation is available in core.

Please forgive me my ignorance, but what is meant by "you can now use a modifier + Click to navigate to it."?

@koosvdkolk In js/navigation/sidebar.js of the 8.x-3.x branch of the module, it's set up to work with (e.ctrlKey || e.shiftKey || e.altKey || e.metaKey), so I suppose you can use any of those 👍

@saschaeggi Will this code be added to the 4.x branch?

Mmm... that does not work on my installation, and even if it would work: it is just bad UX. No normal user would think of Ctrl+clicking menu items for that purpose.

@koosvdkolk I agree with the UX point, maybe open a new issue for that, referencing this one?

I think an issue already exists in the Core issue queue. Note that the navigation got included in the meantime into Core so all requirements regarding the new navigation should be placed in Core instead. We'll soon deprecate our "test" integration in Gin.

You can enable Core's experimental navigation module instead

PS: The change here is also included in 4.0.x

Cheers!