Anonymous
My feedback
-
135 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
108 votesAnonymous
supported this idea
·
-
220 votesAnonymous
supported this idea
·
-
20 votesAnonymous
shared this idea
·
-
9 votesAnonymous
shared this idea
·
-
76 votesAnonymous
supported this idea
·
-
6 votesAnonymous
shared this idea
·
-
1 voteAnonymous
shared this idea
·
-
178 votes
Thanks for your feedback! We’re reviewing your suggestion.
Anonymous
supported this idea
·
-
1,891 votes
In modern pages, we open links within SharePoint in the same tab by default, and external links in a new tab. In the text web part, users can specify to open links in a new tab, but that isn’t the default behavior. Similarly, for navigation links, they follow the same rule (within SharePoint, same tab, external to SharePoint in a new tab). This is true of the modern web parts that support linking as well (hero, quick links, images, etc.) This is the pattern we’ve adopted for consistency.
After reviewing other areas of modern sites, like the site pages library, document libraries, lists, site contents, etc. we did find some different opening behaviors which we’ll review and resolve.
Can you help us understand if this pattern isn’t meeting your expectation, if we have some inconsistencies within modern pages we’ve missed, or if it’s the other areas of modern sites where…
Anonymous
supported this idea
·
-
13 votes1 comment · SharePoint Hybrid And Migration » SharePoint Insights · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
38 votes3 comments · SharePoint Hybrid And Migration » SharePoint Insights · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
54 votes
Thanks for your feedback! Just a note to let you know that we’re building your suggestion now.
Anonymous
supported this idea
·
-
62 votesAnonymous
supported this idea
·
-
84 votesAnonymous
supported this idea
·
we tried using a custom SPFx footer to solve this problem, however found that it was not appropriate as it displays fixed at the bottom of the page and not in the scrollable section.
We used the OOTB footer and ended up writing powershell to replicate the footer across all sites in the hub as a stop gap.
Having a 'Hub footer' would be awesome which behaves the same as the Hub navigation. The key is the footer needs to be at the bottom of the scrollable section.