Anthony

My feedback

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

    We’ll send you updates on this idea

    89 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Suphatra responded

    We’re fixing bugs identified in the comments, and other user reports we’ve received around markdown, but we’ve decided we’re not going to fundamentally change our markdown support.

    This is the first time we’ve declined a request, and it didn’t come easily. We weighed this against other important features we’re working on to deliver and we had to make some tough choices.

    Really appreciate your understanding on this, and please feel free to ping me if you have any questions, complaints, or need to rant.

    Suphatra

    Anthony commented  · 

    @Suphatra - it has been 2 years since you Declined this. But I think we both know the Markdown feature is still broken. The people still want proper markdown formatting!

    THIS FEATURE REQUEST NEEDS TO BE REASSESSED !!

    Anthony supported this idea  · 
    Anthony commented  · 

    This is the most frustrating thing about Teams, especially for developers. I am constantly fighting Teams to try to get it to format the message the way I want.

    In Slack, it was simple. You just create the correct markdown and press send. If you made a mistake, you can just edit you message.

    In Teams, it is a nightmare. The parser is constantly trying to guess what markdown to apply and where you want to start and end markdown. You cannot paste markdown into the chat. There is a high latency (lag) that prevents markdown from apply if you're not typing slowly and your cursor ends up getting stuck inside inline code blocks.

    What the heck Microsoft?

    Everybody else: Implements actual markdown parsing after message is posted
    Microsoft: Let's implement a real-time markdown guesser!! Yeah but make sure it is laggy, frustrating and only works 25% of the time!!!

    If I had any say, I would be moving the company to Slack or Hipchat ASAP.

    Who the **** is working on Teams anyway? A bunch of grad students? Can you guys hire some professionals maybe?

  2. 50 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Anthony supported this idea  · 
  3. 43 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anthony commented  · 

    This is the most frustrating thing about Teams, especially for developers. I am constantly fighting Teams to try to get it to format the message the way I want.

    In Slack, it was simple. You just create the correct markdown and press send. If you made a mistake, you can just edit you message.

    In Teams, it is a nightmare. The parser is constantly trying to guess what markdown to apply and where you want to start and end markdown. You cannot paste markdown into the chat. There is a high latency (lag) that prevents markdown from apply if you're not typing slowly and your cursor ends up getting stuck inside inline code blocks.

    What the heck Microsoft?

    Everybody else: Implements actual markdown parsing after message is posted
    Microsoft: Let's implement a real-time markdown guesser!! Yeah but make sure it is laggy, frustrating and only works 25% of the time!!!

    If I had any say, I would be moving the company to Slack or Hipchat ASAP.

    Anthony supported this idea  · 

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.