[MINOR_ISSUE] Copying from MS Word spawns .png file

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ x ] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

When copying some content from Word, and pasting it into the default rich text editor in Squidex, an image with the same content as the copied content spawns below the paste.

Expected behavior

When copying text from MS Word and pasting it into Squidex rich text editor, only the text should appear, nothing more.
When copying image from MS Word and pasting it into Squidex rich text editor, the image should only be pasted once.

Minimal reproduction of the problem

I write some text in MS Word, which I then select and copy. I go to Squidex, where I have a rich text editor. When I paste, the text appear, but below it a png also appears. Its motive is the content of the clipboard. When an image is pasted, it appears twice in the rich text editor.

Environment

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ x ] Cloud version

Version: [VERSION]

Browser:

  • [ x ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:
The bug does not appear on Firefox desktop or Safari desktop.

Have you tried to paste with CTRL + Shift + V? WYSIWYG editors usually preserve the formatting from the clipboard

I think it is a Word feature to also put an image of the selection to the clipboard. Unfortunately I do not have word.

@marcus_hum I tried to reproduce your problem by opening my local Word from Office 365. I inserted some text, marked it as bold, copied everything and pasted it into the RichText editor. Upon viewing the source code, everything is correct.

If you don’t want to use the shortcut I pasted above, click on Edit -> Paste as text

Thank you guys for taking the time to look at this!

I will convince my editor to use Safari instead of Chrome. Sometimes it’s easier to work around a problem rather than nailing it down. To be honest, I reproduced the problem in Chrome yesterday, but today I am unable to do so.

1 Like