Repository navigation
"Up One Level" navigation goes up two hierarchy levels instead of one #8240
DescriptionThe automatically generated "Up One Level" navigation button does not navigate to the immediate parent page. Instead, it appears to skip one hierarchy level and navigates two levels up. Steps to reproduceI am using hierarchical pages with the navigation mode set to Inherit. Example 1Page structure: /network On
On
When I click "Up One Level" while on: /network/nat Expected behaviorIt should navigate to: /network Actual behaviorIt navigates to: / (the homepage) Example 2The same behavior can be reproduced with a deeper hierarchy: /network When I am on: /network/nat/snat and click "Up One Level": Expected behavior/network/nat Actual behavior/network ConclusionIt appears that the "Up One Level" navigation is calculating the parent path incorrectly and removes two path segments instead of one.
The issue is consistently reproducible with navigation set to Inherit. |
Replies: 1 comment 1 reply
|
I think the menu is doing what it was built to do, the label just reads differently. The browse menu opens on the folder that holds the current page, not on the page ( Up One Level goes up from that listing, not from the page ( If the menu should open on the current page's children instead, that's a reasonable feature request to file as an issue. |
|
Thanks for the explanation. That makes sense now and the current behavior is clear. From a user's perspective, however, I think it would be useful to enhance the Browse menu with an option to navigate to the current page's children. This would make navigating deeper page hierarchies more intuitive, while keeping the existing behavior intact. Thanks again for clarifying how it currently works. |
I think the menu is doing what it was built to do, the label just reads differently. The browse menu opens on the folder that holds the current page, not on the page (
onShow). On/network/natthat folder is/network, which is why you seenatand its siblings when it opens.Up One Level goes up from that listing, not from the page (
goUp). From the/networklisting, one level up is/, and thenetworkpage is a row there. That's why every row in your table lands one level higher than you expected.If the menu should open on the current page's children instead, that's a reasonable feature request to file as an issue.