Owen Scott

My feedback

  1. 573 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    49 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott supported this idea  · 
  2. 679 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    74 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott supported this idea  · 
  3. 45,861 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4831 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott supported this idea  · 
  4. 31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Owen Scott commented  · 

    This seems like a specific incident of the more general issue: Teams' on-the-fly Markdown parsing is really, really broken. Microsoft - could you please fix that, by stopping with automated parsing and leaving Markdown syntax in place, and then watch this entire long-tail of bugs melt away?

    Owen Scott supported this idea  · 
  5. 64 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Owen Scott commented  · 

    Markdown support on teams has to move away from on-the-fly parsing. The approach has SO many problems. Please move to in-line formatting but leave the Markdown syntax itself in place...

    Owen Scott supported this idea  · 
  6. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Owen Scott commented  · 

    Microsoft, what is happening here?!? You've had a completely broken product in the field for months, and there are like a half-dozen user voice posts about it. This isn't a request for improvement - you've literally shipped something that doesn't work.

    Try typing the following and tell me that I'm wrong:

    > The first variable is named `var1` and the second variable is named `var2`

    In examples like this you get an inline code span for "var1" (most of the time) but never for "var2". Please fix! I don't want to see any new features added to Teams before this basic issue is solved...

    Owen Scott supported this idea  · 
  7. 109 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Owen Scott commented  · 

    Please please please fix the buggy (non) Markdown support and do it properly! Right now it's worse than not having it at all...

    Owen Scott supported this idea  · 

Feedback and Knowledge Base