Adding images after spaces wraps image markdown in code block

[buddh4]

When adding spaces before an image in the wysiwyg the image markdown will be wrapped in a code block. How could we escape such a case?

[marijnh]

Could you describe more precisely what you are doing? Adding an image after a space to the document in the ProseMirror editor on https://prosemirror.net/examples/markdown/ and then switching to markdown doesn't do anything unexpected.

[buddh4]

Sorry, here some infos how to reproduce:

• Go to https://prosemirror.net/examples/markdown/
• Change to WYSIWYM
• Enter a new paragraph
• Add 4 spaces
• Click Insert -> Image
• Add location e.g. https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png
• Switch to Markdown and Back to WYSIWYM

The result in my screenshot above (with the ``` block) happens only if you again switch back to Markdown. The problem is that 4+ spaces at the beginning of a line will be interpreted as code block which is normal markdown syntax, but breaks wysiwyg in this case.

[marijnh]

Ah, okay, that doesn't appear to be related to images, since the same thing happens with text. It seems Markdown doesn't provide a way to escape spaces, and requires parsers to strip leading spaces. So there's not much this serializer can do to preserve those.

More generally, having spaces at the start of a paragraph like that suggests you're trying to do layout with spaces, which is rarely a good idea anyway (HTML will collapse them, for example).

[buddh4]

Yeah, just thought there maybe was an easy way of escaping such cases. Its not me who wants to use spaces for layouting, but for normal users this is rather unexpected.

I thought about following solutions:

• Implement additional code block input rule.
• Detect such cases and somehow replace spaces with  
• Least favorite: Remove this markdown syntax and only allow ``` blocks.

Anyways, thanks for your feedback.

[marijnh]

Markdown, unfortunately, turns out to be somewhat problematic as a serialization format when users aren't directly writing it, since it has a bunch of these corner cases that make some documents unrepresentable.

I don't think I'll be able to address this one at in this module, so I'm closing this issue.