Follow-ups from "Allow pasting raw content in content editor"
The following discussions from !116918 (merged) should be addressed:
-
@pedroms started a discussion: (+2 comments) @himkp issue: (non-blocking) When rich content is pasted, HTML elements and styles that are not supported by Markdown are rendered. When the content is saved, those unsupported elements and styles are not present. So what a user sees before submitting is not what is saved and rendered.
If I switch between editing modes, the rich text mode assumes the “correct” rendering.
This is non-blocking, as I don't know if it's directly related to this MR.
-
@pedroms started a discussion: (+1 comment) @himkp issue: (non-blocking) When rich content is pasted,
div
HTML elements persist even in markdown mode, rather than being removed. I think they should be removed as they are non-standard Markdown and don't change anything in the rendered content.This is non-blocking, as I don't know if it's directly related to this MR.
-
@pedroms started a discussion: (+1 comment) @himkp issue: When raw content is pasted, some it may be indented and that is not immediately represented in the editor. Only when the content is saved or the user switches between editing modes, they see what will be rendered. In this case, indented raw content should be immediately rendered inside code blocks, as that's how it will be rendered when saved.