Simpler editor without formatting (WYSIWYG)
As a developer, we share a lot of code snippets and logs information. Would be great to have a simpler text editor, with no formatting (pasting something from the web is often painful) for composing messages.
It could use markdown for formatting, keeping it user-friendly.
Maybe an option in the settings to use the simpler editor would fit better for all types of users.
An Angry Ape commented
Please Microsoft, it's 2021, can you please address all these issues regarding your terrible editor inside of a bloody chat program?
Bruno Saboia de Albuquerque commented
You can do the same as you did with Azure Pipelines pull requests: we have a WYSIWYG bar _below_ the text area. Please also make this optional: I myself and many other coders would rather have this disabled.
PLEASE DISABLE RANDOM ******** MODE
Michel Albert commented
To be fair, Teams is a MASSIVE improvement to our current in-house communication platform.And being able to do some text formatting is just amazing.
Granted, we currently live in the stone-age over here and pretty much anything is an improvement.
*but*, as a developer, using markdown is pretty much ingrained as it is supported on so many platforms (github, gitlab, ...) and it would be great if it was supported in Teams as well. Everything else in the chat-part of teams works pretty well.
But the support of markdown would definitely make it miles better. Not the quasi-WYSIWYG implementation we have today though. I don't mind seeing the raw markdown while I am writing the message and it only being converted on submission. In fact, that's the way everyone in our team would prefer it. We regularly hear the odd "HRRrnnnng" sound from people or the occasional swearing at Teams for this exact reason :) We deal with it though as it is much better as our current platform.
It remains a pain-point though.
Primarily because the auto-WYSIWYG-formatting sometimes works, and sometimes not. For example, a very common occurrence is copy/pasting a line from a CLI or code which you want to inline-format as monospaced-text.
I usually type my message, start with the first backtick, then paste the code and close the backtick. If done like this the formatting won't work. Instead, you have to first paste the code, then navigate back to the beginning of the code, enter the first backtick, then to the end and add the second back-tick. This jumping-around feels unnatural.
Miguel Pérez commented
Teams is a chat program that has excellent collaboration, document embedding, shared calendar notifications, calls, etc., it just lacks a good chat program.
Seriously, the chat UI is dismayingly awful. A buggy rich text editor for developers? No, thank you. Process Markdown on submission, not keystroke, and give me a raw TEXTAREA, not a fussy buggy fickly box.
The chat UI wastes screen estate and is very difficult to look at, it tries to mimic WhatsApp (poorly) instead of Slack, margins in the screen are outrageous, code formatting doesn't show up on mobile, etc. We tested Teams but went back to Slack because of this; developers can't use this thing.
WYSIWYG? Not a chance. Not minimalistic IRC-like? Not a chance. Fix those two and we'll reconsider.
Eskild Diderichsen commented
Either completely remove the WYSIWYG editor, or give us an option to disable it and only use markdown for formatting.
Currently writing "technical" messages is a PAIN.
Currently editing "technical" messages is BROKEN! It easier to delete the message and start over! It's beyond bad!
Stéphane Daviet commented
In Slack, this is the case and it's much more easier to enter code samples for instance. StackOverflow also do a great job with this. The WYSIWYM way should really be considered, perhaps through a user setting. Big source of complains from my teammates when migrating from Slack to Teams.
The example with x = a*b*c should not be a problem as backquoting it (e.g. `x = a*b*c`) usually disable the formatting inside backquotes.
Patrick Hallisey commented
Nothing? There are many requests to fix markdown support. Is there any plan to address these?
Yeah, the current editor is almost impossible to write anything but simple text. Most of the time the formatting just does the wrong thing and it's impossible to get it to do what you want. A raw text editor that formats the markdown only *after* the message is sent (and of course allows you to edit as raw text again if you'd like) is really what this application needs. (See Slack for example)
Sean Ellis commented
Markdown-type formatting is a bugbear of mine specifically for this use case. Code such as x = a*b*c is mangled into x=abc (with b in bold). If this is added, it must be an option.