SharePoint
Feedback by UserVoice

Hugo

My feedback

  1. 345 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Hugo commented  · 

    While I appreciate the effort with the Graph Toolkit, it is absolutely going in the wrong direction. We want to use a COMMON control to make all our solutions look and behave consistently, not introduce a new control that works differently.

    This is especially going to become a relevant conversation with the eventual release of Project Cortex.

    Hugo supported this idea  · 
  2. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo shared this idea  · 
  3. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo supported this idea  · 
    An error occurred while saving the comment
    Hugo commented  · 
  4. 73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo supported this idea  · 
    An error occurred while saving the comment
    Hugo commented  · 

    Here is an example of a scenario I'd like to implement: When a user edits a page, I want the extension to verify the page before they save it.

    This could be used for custom spell checkers, verifying content against DLP policies, or testing for accessibility issues BEFORE user saves the page.

    An error occurred while saving the comment
    Hugo commented  · 
  5. 29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. 142 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  7. 69 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Hugo commented  · 

    While I disagree with the "ridiculous" statement (the team works hard to constantly improve this product), I agree that this is a feature that should be available. Synology's web-based user interface has been supporting this function for many many years.

  8. 1,118 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    201 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo supported this idea  · 
  9. 1,015 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    96 comments  ·  Sites and Collaboration » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →

    This request is still in our web part backlog, but we’d love some more information. As some replies to this request have pointed out, when hovering over a person in SharePoint, Teams, or Outlook, you do see an Org Chart displayed. When we’ve spoken with customers in the past, our feeling was that more customization was required to display this on a page. Help us understand your needs. If we gave you the option to display this auto generated Org Chart on a page, with no customization options is that enough? If not, what customizations do you need? E.g. I need to be able to hide some of the people in the team, even though they’re in AAD. I need to rearrange and put some people in different physical locations on the layout to show their relationships better. I need to change their title from what’s in AAD,…

    Hugo supported this idea  · 
  10. 3,635 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    351 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo supported this idea  · 
  11. 345 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Sites and Collaboration » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo supported this idea  · 
  12. 1,734 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    295 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →

    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…

    Hugo supported this idea  · 
  13. 5,533 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    697 comments  ·  Sites and Collaboration » Sites Management  ·  Flag idea as inappropriate…  ·  Admin →

    Providing the ability to scale from renaming individual sites, to all sites within a SharePoint tenant, while ensuring a consistent user experience across M365 is a complex problem. We have been working hard on this long-awaited feature and are currently validating this with a subset of customers in a closed (no longer accepting nominations) Private Preview Program. As we consolidate their feedback, we will provide another update in the next few months.

    Hugo supported this idea  · 

Feedback and Knowledge Base