Handling of nested formatting markup is inconsistent between editor, preview, and final rendering of a comment.

[hobovsky]

Description

Handling of nested formatting markup is inconsistent between editor, preview, and final rendering of a comment. Editor and preview seems to handle markup correctly, while submitted comment seems to miss parts of its markup.

To Reproduce

Create a large paragraph of text marked as italics. Mark one word of this paragraph as bold. Try different markup variants: "_text *bold* text_" or "*text **bold** text*" or " _text **bold** text_" . All of these seem to be handled correctly in editor itself and in editor preview.

Expected Behavior

Text formatted as "text bold text" .

Screenshots

For "_text *bold* text_":
Editor:

Preview:

Rendered comment:

For "*text **bold** text*":
Preview:

Rendered comment:

Contexts

Win 10, Opera browser 56.0.3051.52.

[Voileexperiments]

#1441?

Also AFAIK lots of Markdown implementations are not up to spec with the GitHub flavor (which makes the most sense IMO). Like the one in StackOverflow...

[hobovsky]

My intention was to put more impact on the fact that markup itself seems to work for CW, because two on three cases it's handled correctly (or at least it seems so). For discourse editor it works ok, for editor preview it works ok, it's 'just' final result which looks off. That's what leads me to thinking that it's some smaller issue than implementation of markup being incorrect/'underimplemented' in general.

But you are probably right, comment editor and comment display are probably handled in two completely separate ways.

[kazk]

Closing as duplicate of #1640