Forum Discussion
MicrosoftRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Thanks Abhimanyu Singh - yes, the intended design pattern of modern nav where nesting is used is for the parent header to have an expand/collapse target and a link target. Currently, if the parent/header doesn't have a link it gets treated like a self-referencing link (in this case to the root site collection). Let me discuss w/ the team to see whether there are other options.
2 Replies
ssquires wrote:Thanks Abhimanyu Singh - yes, the intended design pattern of modern nav where nesting is used is for the parent header to have an expand/collapse target and a link target. Currently, if the parent/header doesn't have a link it gets treated like a self-referencing link (in this case to the root site collection). Let me discuss w/ the team to see whether there are other options.
ssquires what has been the outcome of your discussion with your team on this? This is a no-go for us. We carefully crafted the navigation for all our sites, and now suddenly the headers start pointing to the root. This is awful. Please make the headers with no links, behave like headers and nothing else.
One way to solve this would be to NOT use those as self-referencing links at all. I mean do not use anchor element for such headers at all. Alternatively, use JavaScript to preventDefault on such headers.
Please get this out already. It is ruining our experience.
- ssquiresAbhimanyu - thanks for bump - yes, the controls team is looking at options to make the behavior more flexible. As it is used in the nav we are looking to correct the arbitrary, self-referencing link that gets assigned to a node acting as a "header" (no link) and get a fix out. Thanks.
