"Modern" Libraries Should Respect Navigation Settings
When in the "modern" pages, we see an entirely different set of navigation options in the top nav than when we are in "classic" SharePoint. These pages should all respect the same navigation settings.
This work to support structured and managed navigation in classic sites on “modern” pages is complete and has been rolled out. The team is investigating how to extend/support these navigation models in new sites. Please add your support to those suggestions to help drive prioritization of that capability.
6 commentsComments are closed
Donia Strand commented
We'd like to see this too - if we could use structural navigation, then we would be able to get back the "Open in New Tab" functionality.
I agree with Marc. We do not have a SharePoint developer in our organization and we heavily depend on using out-of-the box solutions, custom css and custom navigation only for our intranet sites. Having responsive template design for pages in Site Pages library is a huge progress but if they don't display our custom css and custom navigation (like Wiki Page template), we can't use them at all. I would like to encourage SP team to fix this issue as soon as possible, a lot of people will appreciate that. Thanks.
@ Anon: It sort of works for structured navigation. Append "/_layouts/15/quiklnch.aspx" and edit the navigation (including removing the Page Not Found link). There's still a bug in modern UI: if you make any edits to quick launch you have to re-do all the cleaning going to that URL. annoying as hell.
Oliver Bartholdson commented
So frustrating Marc! Thanks for suggesting this.
In particular please can the "Page not found" page be removed in publishing sites...This is really annoying for customers and I get tired of having to make excuses
Brent Ellis commented
Need same publishing features for modern nav too (such as audience targeting/permissions)