Markdown is now here: https://microsoftteams.uservoice.com/forums/555103-public-preview/suggestions/16911154-markdown-support (that's great).
However it would also be great if we could preview a message written in markdown before we post it
i love getting trapped in inescapable code blocks while writing a message, very cool, please get rid of this forced WYSIWYG garbage
Michel Albert commented
While I support the idea of having a preview, most importantly I want to have it *optional* like in GitHub for example.
The latest version of Teams has a quasi-WYSIWYG preview for this which is painful to use. A simple "Markdown/Preview" tab would be much appreciated.
Eric Peters commented
I had a similar question here: https://techcommunity.microsoft.com/t5/Microsoft-Teams/Disable-rich-editing/m-p/355836#M26716 I would like the message editing to only be in markdown before posting.
Harrison Kiang commented
This stems from
which attempts to address the poor implementation of
really, Markdown support should adhere to RFC 7763/7764. Maybe a Twitter post to @MicrosoftTeams might get their attention: https://twitter.com/hkiang01/status/1067628231715667968
Jon Nyman commented
Starting out with the rich text editor and then trying to force markdown to work with it just doesn't work. Maybe in the database you can put a flag that the comment is pure markdown then render it on the front end? And use Common Markdown standard please so we all don't get super frustrated!
I would say have two modes. Rich text editor or markdown. Let us choose are preference ideally in a setting up higher so we don't have to pick it every time we want to write a message.
Joel "Jaykul" Bennett commented
Yeah ... this isn't markdown. Markdown is something I write, AND EDIT. This is some newfangled WYSIWYG entry that ends up being the worst of both worlds, because you have to deal with stuff changing on you, AND with trying to edit rich text
Ilya Yablochnikov commented
Markdown support is very painful. For example:
* Type something put a ` then go to the beginning and put another backtick. Expected behavior: the message should render with code highlighting. Actual behavior: the message is sent surrounded by backticks.
* Type `abc`, it is rendered as code, then go back inside and modify "abc" to "abbc", go to the end of the line to continue typing. Everything is now formatted as code and it's impossible to go back to plain text formatting.
Please do not render markdown as we type it. Just render it when the message is sent. The whole point of Markdown is that it's easy to edit.
Matthew Petty commented
The Markdown support is weird and bad. Suggest a side-by-side preview, or a button you hold down as suggested below.
Prashant Pathak commented
The WYSIWYG markdown hybrid currently implemented is very fiddly to use to the point that I just avoid it altogether. It was ambitious but unfortunately a failure. Time to accept that and move on. The point of Markdown is that the raw syntax itself looks close enough to the desired output that you can edit in it directly. I suggest scrapping the in-line formatting and showing a side-by-side preview if the user adds any markdown to the message. I think this would more convenient than a separate preview tab (like on GitHub). Also acceptable would be a button (with a keyboard shorcut) that you hold down to see the preview.
Owen Scott commented
Please please please fix the buggy (non) Markdown support and do it properly! Right now it's worse than not having it at all...
[Deleted User] commented
The problem with Teams is that the "Markdown" support is actually a simple command guesser that captures just a minor subset of what Markdown actually offers. It works only if you type from left to right. It does not work if you copy-paste Markdown text from anywhere and it does not work if you break the "intended" typing sequence.
A simple example where the command guesser fails - try writing two backticks, then move the cursor back and then enter something within the backticks. Because you did not finish by typing the end backtick the command will not trigger and the part that should be formatted as an in-line code will not be formatted as such. This alone proves that there is no Markdown support. It is merely a formatting overlay on the text box that works only while you type. It is sad that Microsoft announces this as Markdown support.
Regarding preview, I would rather want to see no preview and correct rendering for at least the Markdown subset that other group Communication tools offer (e.g., Slack, Rocket.Chat, **********, etc.) rather than a ****** preview and broken rendering (i.e., what Teams offers now).
I like what GitHub does. Have a two tab approach: one that has the markup in it, and a Preview tab that shows what it looks like formatted. Right now Markdown in Teams is really twitchy, and it doesn't flow well. Getting ``` to work right all the time....it doesn't for me right now.
Jamie Thomson commented
Here's one reason why... I like to use markdown's [text](url) pattern. However I do it by writing
and then filli in in the text and url afterwards. This doesn't work using your live conversion feature, which assumes I type it in the order that it needs to finally appear. That's just not the way that people write markdown - they like to write it all out then go back and edit it. Can't do that with your live conversion.