IMPROVED Markdown Support
IMPROVE actual markdown:
Disable auto-formatting of markdown
*italic* not *bold* or _italic_
Make it the SAME as GITHUB
which is closer to DaringFireball
IMPROVE for mobile:
Please add markdown support for Android client.
IMPROVE for other languages:
Currently the code formatting doesn't work for german keyboard users due to the system expecting another character after the `
Due to that, Teams does not recognize the ` and interprets it as any other character.
I think that needs to change.
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.
I also consider the current version broken. Please don't try to guess the desired formatting because you are doing it wrong 80% of the times. Please just let my type markdown and handle the formatting
a) when sending
b) with a dedicated preview button
This is the single most annoying feature of MS Teams.
John Olsen commented
Markdown is working really bad. And code blocks are apparently not supported in the chat. I am really struggling to get our employees, and in particular the developers, to use Teams, but they just laugh and ask if Markdown has been fixed...
Eskild Diderichsen commented
Please reopen this. The WYSIWYG editor is just straight up broken! It almost always does the wrong thing and makes edit flipping impossible because the WYSIWYG editor is so ******** BAD!
A WYSIWYG editor works great when you're dealing with non-technical people. But programmers and the like will HATE it. Because it always does the wrong thing, and makes editing so hard!
I urge you to reconsider as Teams will never be considered a Slack alternative until you at least give us an option to turn that garbage OFF!
It just doesn't work.
Now that Microsoft employees are forced to use Teams, they themselves will realize that the Markdown support is horrendous.
Just reopen this feature request now, and save your other employees the time to find it themselves or create a duplicate.
@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 !!
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?
Dan LaBar commented
This perfectly encapsulates my hatred for Microsoft. Their products don't ever "just work". They don't really care about making it work because they already sold it to your employer who is forcing you to use it. To top if off, the broken feature is supposed to be an "automation" that makes your life easier by "improving" on a great OSS solution but actually just makes you want to scream into the void of the corporate abyss.
Reminds me of Grapes of Wrath...
> We're sorry. It's not us. It's the monster. The bank isn't like a man.
> Yes, but the bank is only made of men.
> No, you're wrong there- quite wrong there. The bank is something else than men. It happens that every man in a bank hates what the bank does, and yet the bank does it. The bank is something more than men, I tell you. It's the monster. Men made it, but they can't control it.
Martin Beaudet commented
I cannot end a preformatted text block! I try shift-enter, enter enter follow by a couple of backspace, trying to change font size, etc... but nothing work. This is a non sens.
At least, why not create a keyboard shortcut to reset style from current position ?
Every time I go to edit a Wiki page I'm reminded how awful the experience is. Half the time it doesn't know when I'm trying to edit, trying to copy and paste from other sources results in clicking in and out of the section multiple times before it decides to respond, formatting is limited and frustrating, code syntax highlighting is nonexistent...
There really doesn't seem to be a good reason to keep the editor version over swapping in actual Markdown support. PLEASE reconsider.
@Suphatra Is this denied because other things are deemed more important or because proper markdown support is not something Microsoft want?
Wrestling with the wysiwyg editor is a nightmare and not something I ever wish to do
Please reconsider, mark down was designed to be human readable and editable without any issues, forcing a fancy WYSIWYG ontop just makes formatting a pain when all we want is to do simple things like bold, and inline code.
This is an example of trying to fix something that isn't broken, Many many sites utilise markdown for their post formatting without issue.
Owen Scott commented
I'm a Teams power-user, from one of the first large companies to use Teams. I still can't believe this has been marked as "won't fix" - to the point that I just come back to this thread routinely to post.
The auto-parsing of Markdown (and the associated elimination of the formatting syntax) ruins all of the things that Markdown is good for, and makes using Teams into an incredibly frustrating experience. This is not what anyone wanted when they asked for Markdown support :(
Please note the years of frustrated comments from otherwise happy users and re-open this issue.
Wow, nearly 2 years of negative feedback and it's still completely broken. I can't even get *bold* to work reliably, sometimes it works better if you double-up on the *s but that contradicts Microsoft's own documentation (https://support.office.com/en-us/article/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772). As a new Teams user I'm baffled by this 'functionality'...
Steve Gibson commented
This is an incredibly important feature for a development team using Teams to communicate. We just switched from Mattermost to Teams and this is one of the worst hangups of the platform yet.
I think this should be reopened. Your goals should align with your clients.
There should be a RAW-Markdown-Editor ideally with support for latex-math. The advantage would be also in an equally formatted text for every user who uses the raw editor. Currently, if you copy & paste Text from multiple sources the result is hard to read.
Jean-François Corbett commented
This roundabout way of pseudo-supporting markdown ends up giving a confusing and janky UX. You've created a bunch of edge cases for yourselves.
Ilya Yablochnikov commented
This is my number one source of frustration with Teams. Everyday I curse it because the formatting is total garbage.
1) Type `something` and send
2) Edit your message and try to add something after "something" (that is now formatted as code). The text you are adding gets formatted as code too and there's no way (that I know of) to reset formatting.
Or try this:
Type "something", now type a backtick, now hit the Home key and put a backtick at the beginning. You would expect that when you send it (or right away) it would get formatted as code. But no, it just sits there with backticks.
Or try pasting anything, it will paste with formatting but if you want to add more text to it that isn't formatted the same way, you can't reset formatting.
This is total **** and if I wasn't forced by work to use this terrible product (there are many other frustrations, this just the most frequent for me) I would never use it.
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.
This being declined is not a good sign for the future of Teams. Microsoft pretends to be open and willing to accept feedback, but only if it aligns with their current plans. The current "Markdown Support" is easily the most frustrating thing I've used in Teams, and the number of votes on this request show I'm far from alone. It would be far simpler to implement actual markdown support than continue to fix issues with the current editor, and yet, here we are.