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
As we announced at Microsoft Ignite 2019 this morning, we are excited to confirm that Multi-window capabilities are coming to Microsoft Teams, and will start rolling out to the public ring early next year!
Alex & the Teams team
3 votes0 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →
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.
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.
This item remains on the backlog, while we work on other higher priority Meetings features. Thank you.
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.
This feature request is still being worked upon. No additional status to share
Items still in the works:
2), 4), 5) and 7)
Items we cannot repro:
6) and it doesn’t appear people are hitting it, but let me know
Items that are completed and in the public release:
1) and 3)
Also, don't forget that "Yellow highlighter" works great with the "default" black text on the default light theme, but turns the default white text on the dark theme invisible -- colors in this app are so bad for usability right now that we basically have to ask people not to use them...
And don't forget to add a "default" color button.
Currently, people are allowed to specify text colors, including BLACK (which is essentially invisible in the high-contrast theme, and hard to read on the dark theme), and light yellow and light blue (which are extremely difficult to read on the default light theme) ... but there is no way to go back to the "default" color. Although to someone using the light theme, it might seem that "Black" is just the default text, in reality, they're making their text invisible to people in Dark or High Visibility.
Text colors should be themed as in Microsoft Office like "accent1" and "accent2" etc. so that when you swap themes, the accent colors swap too, and everything is always readable.
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
This feature request is still on in the backlog. No new updates available at this time.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.