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.
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.
Axel Bock commented
it's a shame, first and foremost because you don't actually HAVE markdown support. you have "auto-formatting while typing", which is not the same at all.
markdown support would be if I paste markdown formatted text into the input field, and it would render correctly. hint: it does not :(
Harrison Kiang commented
@MicrosoftTeams please reconsider the following request. Developers all over the world would be more willing to adopt @MicrosoftTeams if it truly supports Markdown as per RFC 7763/7764. Maybe @daringfireball can give you some pointers.
Michael Grenier commented
Just convinced every member of my organisation to switch from Slack to Teams.
Received a few complains that the markdown seems broken. No one can work out the `inline code` or ```multi-line code``` (we use French keyboard, similar to German).
"Wont fix" is not acceptable response. At least tel us that you might in the future look to improve the Markdown...
John Mick commented
Can only agree with other commenters. Markdown is utterly broken in Teams, the live preview makes it impossible to use. Trying to do WYSIWYG is almost always a bad idea, and definitely in Teams.
Reilly Wood commented
I agree with the comment below that says "The Markdown formatting is quintessentially the most painful experience for me in Teams."
It's really, really bad.
Matthew Bungard commented
Can this issue be revisited?
The Markdown formatting is quintessentially the most painful experience for me in Teams.
Could the decision be explained (are non-tech users genuinely getting a better experience?, is there a performance benefit in the current system, etc).
Joseph Robichaud commented
How do I end a preformatted text block? I don't want to hit enter and send the text. I hit shift-enter and that inserts a newline into the text block. Then I type ``` to close the block but that just shows up as text. Also, is there syntax highlighting for code? It always displays in mono-chrome.
I am very used to the markdown syntax used in GitHub and other chat apps like Slack. Is there an option to enable a markdown mode in the editor?
Sean Amos commented
It's a huge pain to have to click the format button, then open the code snippet editor, then select a language from a dropdown. Lifting your hand from the keyboard for 3 clicks instead of doing:
I can't help but think the people who implemented the current markdown support haven't actually used other modern tools.
Sounds like a non-sense decision to me and one which doesn't show you are listening to your customer base.
What's wrong with you guys in Microsoft, aren't you able to accept and support a de-facto standard as it is? Why do you want to reinvent things that already work as they are?
Kris Avi commented
Current markdown is broken, it for code it only works once. In some cases you can get stuck in code mode when.
Matching existing standard seems like a good solutions and I believe there would not be a need for inventing another one. Afterall MS aquired Github, so even the GitHub Flavored Markdown should be kind of theirs to use without any problems...
Things that I have tried and are not working compared to slack, discord or even FB messenger:
* In single line multiple code tags
* Language choosing on multiline tags
* Non-english keyboard backticks down't start code block at all
* Getting stuck in code tag that you cannot end with back-tick any more
This inline rendering seems to bring a lot of problems. Probably the nonenglish back-ticks would work if the markdown processing would run after pressing send. Most likely it would detect the back-ticks.
People seem upset at the decision of "Wontfix", but I guess it is the way how MS works now. A bit off the topic but same happened with Skype. People asked for old features to be kept and reported them being missing as issues and answer was as well "wontfix", but adding new features most didn't even want was something that was done.
I guess it is visible that people want it fixed.
If you do not plan to fix those things then at least let users know of the issues, so they will know not to come from slack that supports those more and might be better environment for development teams as code is shared more and it's support is lacking in Teams.
Bruce Edge commented
Completely agree with the user-base comments here. Match an existing markdown standard. DO NOT re-invent your own, as you see it just ****** everyone off.
Hey, guys, just in case when you need to 'disable' markdown (formatting) in your MS Teams messages, use HTML encoding feature, I had a huge issue with MS Teams posting my messages in _italic_ because of underscores and when I got underscores replaced with '_' everything works just perfect
[Deleted User] commented
> we’ve decided we’re not going to fundamentally change our markdown support
This is actually *extremely* disappointing given that the **only** reason we're in this situation at all is because you guys chose to reinvent the wheel instead of using existing, popularly-supported-and-used markdown.
This is a complete showstopper for anyone trying to use Teams to "replace" Slack or any other collaboration app with real markdown support where they actually *use* the feature.
What's *really* frustrating is that Teams is (or was, at least) an Electron app, which means that the Teams devs have access to the plethora of markdown renderers available.
What's also frustrating is that the text input & formatter seems to be just the Outlook Webmail box but re-skinned, complete with "Tag as Important" button. The message box similarity to the webmail interface in terms of layout and available options, and the fact the most prominently-displayed "integration" option is a channel email address, makes me suspicious... Teams feels like a fancy frontend on an email system with "connectors" tacked on the side and a special renderer for message threads. If that's the case, then the "wontfix" response makes a *lot* more sense to me (you didn't "reinvent the wheel" but rather used an existing-but-"wrong" wheel) but I still don't agree with the decision.
Owen Scott commented
Can you please fix this feature? It's a daily source of pain. You've tried to do some clever inline stuff but no one asked for that :(. Can we not just type in markdown and have it render on send???
Please, don't continue on the Microsoft way of doing same stuff differently. There is existing and known Markdown syntax. Just reuse it with complete support and same syntax!
Tyler Benton commented
There's literally no reason to go off an reinvent the wheel. Why would you go off an create your own markdown parser and sketchy previewer when all the issues that everyone is having would go away completely if you just used an existing markdown lib that has actually done your work for you. All you have to do is use [marked](https://www.npmjs.com/package/marked) last month(Dec 2017) alone it it had 2,927,557 downloads so it's pretty obvious that they know what they're doing.
Ed Winn commented
This is also a blocker for our team of software devs. Teams has some really nice features, but the markdown support is maddening.
* Copy/Paste markdown doesn't work.
* Can't insert a gif from a ![gifhere](someurl) url
* If you make a mistake while typing a inline code block and go backwards the rest of your message becomes an inline code block
* emojis also don't work that well. :emoji: very few supported and they are all animated. just want plain full emoji set
I understand the various reasons why you would have the markdown support like it is, but would be nice to give the users a checkbox to enable/disable full markdown support.
Michael Herndon commented
Then many orgs will have to pass on teams, especially software companies.
Teams has a lot of promise. however, this is a blocking issue for adoption.
- tech org decision maker.