Markdown plugin wraps the initial content in a code block

[Mgsy]

A follow-up of #7859 (comment).

📝 Provide detailed reproduction steps (if any)

1. Add the Markdown plugin to the all features manual test.
2. Open the test.

✔️ Expected result

❌ Actual result

---

If you'd like to see this fixed sooner, add a 👍 reaction to this post.

[Mgsy]

I wasn't able to reproduce it outside of the mentioned manual test, however, after adding the plugin to the online builder, our sample looks like this:

[Reinmar]

Could be due to the fact that the content of the element to be replaced is indented. Like this:

<div id=editor>
	Content
	Content
</div>

Instead of this:

<div id=editor>Content
Content</div>

The latter is correct – it's what a templating system / backend would usually output. The former is what you'd write by hand, though. Unfortunately, I can imagine more people stumbling upon this and it's also realistic for the backend to produce the former, indented form in some situations.

The right place to fix it (if I'm right about the issue) would be inside the function that reads HTML from the element to be replaced with the editor. However, it's not that obvious what it should do as whatever it trims... may be incorrect. This is – it may trim an indentation that was supposed to be there if the editor consisted only of a code block.

Therefore, documenting it somewhere that when using a markdown you probably shouldn't even use the "replace an element" form and instead promoting the config.initialData form should be safer.

[Mgsy]

You're right, this is the case. After removing indentation, it renders properly in the editor.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).