Pasting HTML embed widget does not paste it's content

[niegowski]

📝 Provide detailed reproduction steps (if any)

1. https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html
2. Copy HTML widget
3. Paste HTML widget

✔️ Expected result

Widget is pasted with its content.

❌ Actual result

Content of HTML widget is empty.

📃 Other details

• Browser: …
• OS: …
• First affected CKEditor version: …
• Installed CKEditor plugins: …

---

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

[niegowski]

This is because HTML embed feature is registering rawContentMatcher on the editor.data.processor

ckeditor5/packages/ckeditor5-html-embed/src/htmlembedediting.js

Line 98 in ca58a3b

editor.data.processor.registerRawContentMatcher( {

but Clipboard plugin is using a separate instance of HTMLProcessor

ckeditor5/packages/ckeditor5-clipboard/src/clipboard.js

Line 61 in ca58a3b

this._htmlDataProcessor = new HtmlDataProcessor( viewDocument );

[maxbarnas]

I see that in both cases `HTMLDataProcessor` is initialized with the same Document view. Seems reasonable to use HTMLDataProcessor from the editor instance. Am I missing something? Surely, this fixes the problem when tested locally.

[niegowski]

Unfortunately, the editor.data.processor could be sth different than HTMLProcessor - i.e. it could be a markdown processor but for clipboard we need HTML processor. I was thinking about integrating it in a way that clipboard feature would be able to automatically use same matchers as those registered in data pipeline processor.

[maxbarnas]

Gotcha! To be clear, editor.data.processor can be something different, depending on the contents the editor wants to handle, but the clipboard, in its current form, always expects HTML or plain text, right? That's why we need those two processors decoupled?

[niegowski]

Gotcha! To be clear, editor.data.processor can be something different, depending on the contents the editor wants to handle, but the clipboard, in its current form, always expects HTML or plain text, right? That's why we need those two processors decoupled?

That's correct