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.
SuphatraSean Amos supported this idea ·Sean Amos commented
I wrestle with the markdown "support" in Teams daily.
You cannot copy and paste markdown from another editor into Teams and have it just work, common if you need to prepare a larger message. You need to paste the message in teams, then reformat it inside teams.
No syntax highlighting, nor would the current approach ever support the broadly used syntax:
It's absurd that to get correctly formatted, syntax highlighted code you need at least 3 mouse clicks: Click formatting button (Or Cmd + Shift + X) -> Click Code Snippet -> Click to select language -> Paste/type code -> Click Insert.......
Aside from the big usability steps backward compared to competitors because of this poor design, there's bugs! The most annoying being not being able to get back out of markdown mode once the editor has auto-formatted it.
If any software developers at MS were using Teams as their daily chat app, I could confidently say this WYSIWYG markdown magic would have gotten thrown out very quickly.