Backslashes added when quoting a message containing markdown formatting

[anoadragon453]

Description

Quoting a message that contains some markdown will causing spurious backslashes to be added, escaping punctuation and parentheses etc.

I presume it's because we convert the HTML back to non-markdown or something? But we can just take the body which is perfectly fine:

"body": "This is a *message* containing markdown. Thanks for listening (<3)"

Might be related to #7324

Steps to reproduce

• Send a message with markdown such as This is (really) *great*.
• Quote the message
• Notice \ escape characters inserted

Version information

• Platform: web
• Browser: Chrome
• OS: Debian Linux
• URL: independent build of riot.im/develop

[t3chguy]

I presume it's because we convert the HTML back to non-markdown or something? But we can just take the body which is perfectly fine:

The body being correct markdown is just a riot-web thing, mobile clients don't match iirc and other clients probably don't either so this is definitely not a good approach.

[anoadragon453]

Ah, unfortunate :/

Well then perhaps just a second pass after the parser goes would work.

[ssokolow]

I've found that trying to escape *chuckle* so it doesn't get interpreted as italics results in the escape showing up in the output too (\*chuckle*).

Would this be the same bug or should I file a new one?

EDIT: To be clear, I'm on https://riot.im/app/ (freshly reloaded on 2020-02-14 at around 10:30PM EST to be sure I'm on the lastest version) and, if I type *chuckle*, it gets converted to _chuckle_ and interpreted as italics while, if I type \*chuckle*, it produces a literal \*chuckle*.

[jryans]

This does not seem to an issue with the current composer.