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.
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.
Owen Scott commented
Hi. Just a question: if you've been fixing bugs since August 3, why as of November have we not see fixes? The Markdown implementation in Teams is *completely* broken.
Try typing the following and tell me that this is a product that Microsoft should have in the field:
> The first variable is named `var1` and the second variable is named `var2`
In examples like this you get an inline code span for "var1" (most of the time) but never for "var2". Please fix! Personally I don't want to see any new features added to Teams before this basic issue is solved... Fix bugs before shipping new features!
Nestor Diaz commented
I agree that Markdown support should be improved. The current implementation is buggy and pretty much unusable for anything longer than a couple of words. This makes the tool unwieldy for dev teams, to the point where many would rather switch to a different tool (as evidenced by this thread).
Sam Blowes commented
Partial support, is not support.
Please support Markdown! not just partially.
Prabal Ghosh commented
Cannot do multiple code blocks in one line... example: This is the `first` code block and this one is the `second`... the second one does not format correctly.
That's disappointing. I really dislike markdown features. I don't want to auto italicize, or auto emote. Maybe make a "post as code" without ANY formatting section?
Dave Gilbert commented
I'd like to add my voice to this issue. Replacing markdown code as-you-type is probably what makes this feature so broken. There might be a way to make it work, but if you can't, then please turn off the inline-replacement and spend the time fixing the parser instead.
Most (if not all) people familiar with Markdown expect to see the formatting marks while editing the text. That's the whole point: easy to read, formatted and unformatted.
I for one believe that support for markdown is more important than memes, giphies and emojis combined.
Maybe this markdown bug could be fixed?
I added markdown support to a 1 hour todo list hackathon. The entire hackathon was a hour, not just adding markdown support. Honestly, it would take 5 minutes to add proper markdown support, and I can prove it:
I seriously think it took me longer to find the best font icons for the buttons than it did to add markdown support. Unacceptable!
`I'd` say ~~this~~ is a `bug`, it's quite **obvious** that `markdown` doesn't work.
Julian Knight commented
Please reconsider this. So many tools are now using Github flavored Markdown that it is rapidly becoming the standard. It works really well with technical teams, is well understood by many people and is much more flexible than the original markdown.
Jamie Thomson commented
I echo all the comments made since this was declined on 2017-08-03. The markdown support right now is horrific. Prashant Pathak said "The inline markdown formatting was an ambitious failure" and he was spot on. People that write markdown do not like your "live conversion" feature that converts it on the fly. I urge you to reconsider this. If you're going to support markdown, do it properly.
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.
I really don't agree with the decline of this feature. Please stop styling my markdown as I type it, it all just is really cumbersome to use, for example when adding code snippets when compared to Slack.
At the time of this posting, this request has been declined, but I'd still like to voice my support for this idea. While I get that Teams is trying to emulate Slack's style of markdown, it's frustrating not being able to use the same markdown that I use in Github, Discord, Reddit, VS Code, and for my personal websites. I hope that you change your mind on this in the future, perhaps making it a configurable option to not break existing workflows for those migrating from Slack.
It's really strange, that the markdown support only is "partial"
why can I only use ## for a header but no further differentiation such as header1 or header2?
Joel "Jaykul" Bennett commented
The decision not to go back on this is, quite honestly, going to cost you.
Doing WYSIWYG markdown is a disaster for usability -- and not just because it completely breaks the ability to paste markdown.
Spencer Watson commented
It's really the parsing of markdown on keyup that ruins all of this. If we just had a separate preview, or no preview at all, it would be far better. No decent markdown editor replaces what the user is typing with a formatted version while they are typing.
Sébastien “scips” Barbieri commented
When I copy paste markdown from Github it doesn't work.
Worst! It randomly works! Some titles are changed others are changed and have pound signs in front (because they are level 3-4 headers.
Owen Scott commented
Adam's comment is spot on.
`foo` and `bar` only highlights the first
I also fine that once you create an autoformatted code block (e.g. using ```) it's impossible to uncreate it. This is a total dumpster fire and really should never have been shipped, especially to paying customers :(
Could you please please please:
1) Stop deleting formatting marks (e.g. "`", "*", etc.) during autoformatting. Just apply the formatting but leave the marks. Or don't auto-preview.
2) Fix the parser
This is our ability to collaborate on code.