**actual** markdown support
The current markdown implementation is simply bad as it's not actual markdown. Instead it's some kind of in-line format guesser that changes what you type on enter.
- it doesn't work in the client
- it doesn't apply to messages submitted via webhook integrations
- it doesn't work on cut-n-pasted text
- it's not complete (tons of markdown syntax missing)
- it doesn't allow simple shortcuts via "/extension" (looking at you, /giphy)
in-line reformatting is slow and often unpredictable in the way it responds as you type, making for a poor experience, especially as you attempt to reformat a message you started typing.
Remember Teams has risen as a response to Slack, which is a collaboration of developers first. A lack of solid markdown is simply alienating the very group that made this tool popular ... which is short sighted. Teams should be fast from the keyboard, predictable in what it outputs ... and basically comfortable. The current markdown mess fails on all these fronts.
Elijah Rose commented
I go to UAB and we were deciding between Discord, MS Teams, and Slack. I've used all 3. I do like Teams organization of files, however it has some annoying features and feels overally somewhat lackluster. However, I can deal.
However, I used MarkDown extensively -- everything from writing notes to brainstorms. The fact that I cannot paste MarkDown into a post is teeth-gratingly frustrating. It's enough that I barely even open MS Teams anymore, as I know for sure that I do not want to type in it (I have VS Code setup perfectly for all of my editing). It's gotten to the point where I'm advocating switching the entire club to Discord. Discord isn't even that great and has some bare minimum MD and no real file management, but with all of its slice of life features and such its preferable at this point.
Please, if you want this to be a real tool, then give us real tools. As the OP said, it feels extremely half-baked atm, a weird attempt at MD via a WYSIWYG lens.
absolutely ridiculous. what were they thinking??
I'm genuinely surprised at how far down I had to go to find this, given the constant griping I hear about it around the office. It truly is infuriating; just enclosing code in backticks - my most common formatting use - is not just awkward, it's plainly broken. It simply doesn't work right.
The kicker is that this is a solved problem. In fact, the solution is simpler than what they have in place. This shouldn't be difficult!
This is the most annoying and bug ridden "feature" I've ever seen in such widely adopted commercial software. I just don't get it.
Isn't Microsoft embarrassed about this horrible design decision? Why hasn't anyone higher up at Microsoft demand they change the way this feature works?
Obviously the markdown should be applied **after** a message has been sent. This is how every other piece of software handles markdown and they do so for a reason!
Not only this, but the markdown doesn't even work most of the time. A lot of the time my cursor will get "stuck" inside markdown blocks and there is no way I can get my cursor out, unless I delete the whole message. It's just really bad... C'mon Microsoft! What the heck are you guys thinking?! (or maybe they're not thinking at all)
PLEASE APPLY MARKDOWN AFTER MESSAGE IS SENT!
Thomas Williams commented
Yet another place where Teams tries to emulate Slack and fails. At the very least, provide an option to turn of the live preview feature. Incredibly annoying.
Kris Mackintosh commented
I am forced to use Teams beacuse where I work uses it.
I have come from a Slack environment and this is probably my bigest annoyance, especially no propper back tick support for code
Tim McLaughlin commented
I echo this, 100%. Markdown rendering should be applied _after_ I submit the message. Add a preview option if you must, but editing should be done in plaintext. That is the point and the power of markdown, and it's why MD has been adopted by so many developer-focused things across the internet.
I can suffer through the animated smileys that I can't disable. I can bear the horrible gif/giphy support. I can even make peace with the fact that I can never use any emoji starting with ":s" because that constipated smiley shows up.
But without being able to use markdown in a sensible way to communicate with fellow devs and techs -- a purpose for which Slack was very well-suited -- I basically avoid using Teams altogether, which is a real shame and has been difficult to work around, productivity-wise.
After using Slack and now being forced to use Teams, I can say that there is literally NOTHING that Teams does better than slack.Markdown support is yet another disappointment.
I think that it would be wise to shy away from any company that uses Teams over Slack. It's a sure indicator that they don't care about using good technology.
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.
Add to the gripes above that the inconsistent application of markdown is a pita as well. Sometimes it works, sometimes it doesn't, forget it if you want to add markdown to a message after the fact, etc. Seems like personal chat vs. a group chat impacts this as well.