Brian Mair
My feedback
-
16 votesBrian Mair
supported this idea
·
-
1 voteBrian Mair
shared this idea
·
-
1 voteBrian Mair
shared this idea
·
-
630 votes84 comments · Sites and Collaboration » App bar & navigation · Flag idea as inappropriate… · Admin →Brian Mair
supported this idea
·
-
13 votesBrian Mair
supported this idea
·
-
21 votesBrian Mair
supported this idea
·
-
192 votesBrian Mair
supported this idea
·
-
48 votesBrian Mair
supported this idea
·
-
2,455 votes67 comments · SharePoint Dev Platform » SharePoint Framework · Flag idea as inappropriate… · Admin →
Thanks for your feedback! We’re reviewing your suggestion.
Brian Mair
supported this idea
·
-
1 voteBrian Mair
shared this idea
·
-
7 votesBrian Mair
shared this idea
·
-
153 votesBrian Mair
supported this idea
·
-
363 votes
We are thinking about a plan for editing the highlighted content display fields, but do not currently have a timeline for this feature
Brian Mair
supported this idea
·
-
1,955 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…
Brian Mair
supported this idea
·
-
5 votesBrian Mair
shared this idea
·
-
156 votesBrian Mair
supported this idea
·
-
361 votes
SharePoint Hybrid and Migration Team
responded
Thank you for bringing this suggestion to our attention. While the SharePoint migration investments have been focused on helping the on-prem customer transition to OneDrive and SharePoint in Office 365 using the SharePoint migration tool, we acknowledge that there are additional scenarios like the ones explained in this suggestion that are not covered yet. We are currently considering various options to solve those scenarios, but we cannot commit to anything at this point. Please continue bringing great suggestions to our attention like this one.
Brian Mair
supported this idea
·
-
2 votesBrian Mair
supported this idea
·
-
91 votesBrian Mair
supported this idea
·
An error occurred while saving the comment -
43 votesBrian Mair
supported this idea
·
This is my #1 show-stopper when it comes to building real-life application solutions with SharePoint Online. I understand the rational behind the LVT, and appreciate the workarounds provided such as the use of indexed columns with filtered list views, but the same workarounds should be available with lookup columns that would also work well with a filtered list of items. A people-picker style selection method would surely enable smart queries on the data.