Display placeholders for images that didn't paste correctly from MS Word

[oleq]

📝 Provide a description of the improvement

Aside from documenting technical limitations of the integration, to improve the UX, we could implement some image placeholders in the editor content to notify users that their images couldn't be transferred (an why). This would look less like a bug and spare users some surprises. 

Related to #2493 (comment). cc @magda-chrzescian

---

If you'd like to see this improvement implemented, add a 👍 reaction to this post.

[oleq]

Some placeholder considerations:

• What would they look like?
• What would be there? (a text?)
• What would happen to them in data? (also copy&paste)
• What should happen to them in collaboration? Should collaborators see them?
• Can we offer users some easy way to replace the placeholder with an actual image?
  • Like for instance a button there to select the image from the disk (or something similar)?
• Wouldn't a toast notification be better considering the previous concerns?
  • It could be necessary anyway because the pasted content could be 100 pages long and there's no way the user will notice some images in the middle have been replaced by placeholders.
  • But would it be discoverable? If you dismiss it by accident, you don't know what happened.

[magda-chrzescian]

The placeholders could have ad additional function to maintain the layout of the pasted document. So it's something to be researched if we have enough data to set the positions and sizes of missing pictures correctly.

Wouldn't a toast notification be better considering the previous concerns?

I would keep both, the placeholders and the toast.

[oleq]

Related #8934.

[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).