My feedback

  1. 462 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    kmcginnes commented  · 

    I see what you are going for. You want a WYSIWYG editor that also supports some of the syntax of Markdown. But these ideas are fundamentally opposed to each other.

    Markdown was created as a rebuke of WYSIWYG editors for many reasons, but the one that resonates with me is that formatting text after the fact is tedious. It's much easier to indicate the formatting as you type and let the computer figure out rendering later.

    But a WYSIWYG editor does not allow for Markdown syntax to exist in the editor, since that is not what the rendered output would look like. If the editor does not match the rendered output you can not have a WYSIWYG editor.

    So you've tried to split the difference. But the result is neither truly WYSIWYG nor truly Markdown. The editor rendering is very similar to the final rendered result, but there are plenty of differences that mean this is not a WYSIWYG editor. And once the markdown syntax is deleted you are not using markdown any more.

    And while we're talking about editors, no text editor in any form should ever automatically delete characters as you type. However, this is how MS Teams "markdown" support works. If you type an asterisk, then a character, then an asterisk the application will delete the asterisks that the user typed. This, in my opinion, is user hostile.

    kmcginnes supported this idea  · 

Feedback and Knowledge Base