Prashant Pathak

My feedback

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

    We’ll send you updates on this idea

    76 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This item is still under review by the feature team. I have no details as to when a decision might happen.

    -Warren

    Prashant Pathak supported this idea  · 
  2. 12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Prashant Pathak supported this idea  · 
  3. 55 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Prashant Pathak supported this idea  · 
  4. 550 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    91 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

    Prashant Pathak commented  · 

    Please reconsider your declining of this request. The inline markdown formatting was an ambitious failure. Getting that right (if it is even a good idea) would be a huge undertaking well beyond the scope of MS Teams. Please now be brave enough to take it back and provide simple and functioning markdown support. Don't think about the sunk cost. Teams would be a better product without inline markdown formatting.

    Or consider this alternative: Format markdown inline but don't remove any of the syntax characters. I think this would still make it a lot simpler and easier to use, especially when changing existing formatting, and hopefully also simpler to implement.

    Prashant Pathak supported this idea  · 
  5. 54 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Prashant Pathak supported this idea  · 
  6. 68 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Prashant Pathak commented  · 

    The WYSIWYG markdown hybrid currently implemented is very fiddly to use to the point that I just avoid it altogether. It was ambitious but unfortunately a failure. Time to accept that and move on. The point of Markdown is that the raw syntax itself looks close enough to the desired output that you can edit in it directly. I suggest scrapping the in-line formatting and showing a side-by-side preview if the user adds any markdown to the message. I think this would more convenient than a separate preview tab (like on GitHub). Also acceptable would be a button (with a keyboard shorcut) that you hold down to see the preview.

    Prashant Pathak supported this idea  · 

Feedback and Knowledge Base