Return to Answer

feature-request status-planned

Bug report opened on GH

I wholeheartedly support the requests to, in some form, allow simultaneous viewing of the Markdown and the preview. If at all possible, I'd rather that be done in some way instead of this. However, if that can't be done...

Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action

As one of the CMs noted:

I literally do not preview my posts on Teams because I can not take the risk of the RT mucking with my MD

If the user only toggles between Markdown and rich text (for example, to see the preview) without making any changes, then toggling back should remember and restore the exact previous state. It’s understandable that there can’t be a 1:1 correspondence between the two, and that editing something in the rich text view may result in different Markdown upon returning.

However, it should be possible to special-case “not changing anything” and return the user back to the previous state upon return, allowing the rich text editor to serve as a preview of the Markdown.

feature-request status-completed

Bug report opened on GH

I wholeheartedly support the requests to, in some form, allow simultaneous viewing of the Markdown and the preview. If at all possible, I'd rather that be done in some way instead of this. However, if that can't be done...

Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action

As one of the CMs noted:

I literally do not preview my posts on Teams because I can not take the risk of the RT mucking with my MD

If the user only toggles between Markdown and rich text (for example, to see the preview) without making any changes, then toggling back should remember and restore the exact previous state. It’s understandable that there can’t be a 1:1 correspondence between the two, and that editing something in the rich text view may result in different Markdown upon returning.

However, it should be possible to special-case “not changing anything” and return the user back to the previous state upon return, allowing the rich text editor to serve as a preview of the Markdown.

feature-request status-planned

I wholeheartedly support the requests to, in some form, allow simultaneous viewing of the Markdown and the preview. If at all possible, I'd rather that be done in some way instead of this. However, if that can't be done...

Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action

As one of the CMs noted:

I literally do not preview my posts on Teams because I can not take the risk of the RT mucking with my MD

If the user only toggles between Markdown and rich text (for example, to see the preview) without making any changes, then toggling back should remember and restore the exact previous state. It’s understandable that there can’t be a 1:1 correspondence between the two, and that editing something in the rich text view may result in different Markdown upon returning.

However, it should be possible to special-case “not changing anything” and return the user back to the previous state upon return, allowing the rich text editor to serve as a preview of the Markdown.

feature-request status-planned

Bug report opened on GH

I wholeheartedly support the requests to, in some form, allow simultaneous viewing of the Markdown and the preview. If at all possible, I'd rather that be done in some way instead of this. However, if that can't be done...

Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action

As one of the CMs noted:

I literally do not preview my posts on Teams because I can not take the risk of the RT mucking with my MD

If the user only toggles between Markdown and rich text (for example, to see the preview) without making any changes, then toggling back should remember and restore the exact previous state. It’s understandable that there can’t be a 1:1 correspondence between the two, and that editing something in the rich text view may result in different Markdown upon returning.

However, it should be possible to special-case “not changing anything” and return the user back to the previous state upon return, allowing the rich text editor to serve as a preview of the Markdown.

feature-request

I wholeheartedly support the requests to, in some form, allow simultaneous viewing of the Markdown and the preview. If at all possible, I'd rather that be done in some way instead of this. However, if that can't be done...

Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action

As one of the CMs noted:

I literally do not preview my posts on Teams because I can not take the risk of the RT mucking with my MD

If the user only toggles between Markdown and rich text (for example, to see the preview) without making any changes, then toggling back should remember and restore the exact previous state. It’s understandable that there can’t be a 1:1 correspondence between the two, and that editing something in the rich text view may result in different Markdown upon returning.

However, it should be possible to special-case “not changing anything” and return the user back to the previous state upon return, allowing the rich text editor to serve as a preview of the Markdown.

feature-request status-planned

I wholeheartedly support the requests to, in some form, allow simultaneous viewing of the Markdown and the preview. If at all possible, I'd rather that be done in some way instead of this. However, if that can't be done...

Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action

As one of the CMs noted:

I literally do not preview my posts on Teams because I can not take the risk of the RT mucking with my MD

If the user only toggles between Markdown and rich text (for example, to see the preview) without making any changes, then toggling back should remember and restore the exact previous state. It’s understandable that there can’t be a 1:1 correspondence between the two, and that editing something in the rich text view may result in different Markdown upon returning.

However, it should be possible to special-case “not changing anything” and return the user back to the previous state upon return, allowing the rich text editor to serve as a preview of the Markdown.