Forum Discussion
Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Brent Ellis (and others) - good news! We're finally pushing out a fix to support structured and managed navigation on modern pages/apps in classic sites.
With this update, if you have enabled publishing on a classic team site, your structured or managed navigation nodes will now render correctly in the modern pages (both global and current navigation), including any scoped or audience-targeted links. We haven’t pulled all the classic settings into the modern panels yet, so when you need to edit the navigation nodes the edit link will direct you back to the classic settings page (/areanavigationsettings.aspx).
We hope this unblocks folks who have been eager to move to the modern UX. Do try it out let us know if you have any questions. Thanks!
Great job ssquires and MS team for monitoring this thread. Lots of good info.
I have set my tenant to first release.
My issue: top nav in modern pages always opens in new tab. Does anyone see similar behavior? Can we set the top nav links to open in same window?
Thanks in advance
MicrosoftThanks kiran bellala - I missed your follow-up question. We are evaluating providing an affordance to specify the link opening behavior (yes, a departure from classic). Current design is links w/in same site path will open in same tab; links in a different path will open in a new tab. We're trying to minimize friction here, but can you elaborate on the business scenario to have more control over this behavior? Thanks!
People always have the simple option of right-clicking and opening a link in a new tab whenever they want. I would want to see the same default behavior as we see today in classic sites: any link in the global navigation should open in the same tab. Otherwise people will have the same maddening experience we see in O365 Groups, where navigating back and forth between the various functional parts of the Group ends up in a screen full of duplicate tabs.
This behavior (opening in same tab) should be observed when just the Publishing feature is turned on and also when Publishing is turned on *and* Managed Navigation is in use. (I use Managed Navigation in the global nav, and structured navigation in the local nav.)
If, in addition, you want to specify an option we can set to force opening in a new tab for a specific link, that would be fine; but the default should be as it is today - open in same tab for all links. It's easy for anyone to override and open in a new tab whenever they want, but there's no way for a person to override and open a link in the same tab.
Richard
Also, I have every site use the same global nav as the parent, so every site shows the same global nav as the top of the site collection.
- ssquiresThanks for the feedback, Richard. I agree that it's easy enough to right-click to open in new tab - and we are trying to be thoughtful about the potential proliferation of tabs. I should have added that there is on-going work here - across the workloads - to ensure a more thoughtful and consistent experience.
I'm not using structured navigation but for me the top and left controls are not working similarly. Left opens subsites in same tab, top menu opens subsites in new tab. This only occurs when the top link is on a mordern team site or page.
- Most often we want to provide easier navigation to subsites using top nav or quick launch. This enables us to highlight few sub sites out of several sub sites. It totally makes sense to open a lik from different domain in new tab. But I think it is kind of annoying to users to open subsite in a new tabs because in user's mind they are still in "SharePoint".
- ssquiresMakes sense. The current design should meet your needs as the top and left controls would work similarly and open subsites of the site in the same tab; but other workloads (like a group-connect site's shared mailbox) in a new tab.
