able-bio / suggestion-box

A place to submit issues for bugs, feature requests and other ideas related to Able.
https://able.bio
4 stars 0 forks source link

Copy/Paste of Images from Clipboard in Safari doesn't consistently work #50

Open kerrishotts opened 4 years ago

kerrishotts commented 4 years ago

Describe the bug In my last post I was using the screen capture tool in macOS and only capturing a portion of my screen to the clipboard, and then was pasting it into my post. This worked the first time, but the second time it would keep insert the first thing I pasted, regardless of what I had just copied.

This was in Safari, on macOS Catalina 10.15.5.

To Reproduce Steps to reproduce the behavior:

  1. Take a screenshot to your clipboard (although any image in the clipboard should do the trick)
  2. Paste into a blog post
  3. Take another screenshot/put another image on the clipboard
  4. Paste

Expected behavior The correct image from the clipboard to be inserted.

Screenshots If it helps, here's a draft post that demonstrates the issue: https://able.bio/kerrishotts/testing-a-pasting-bug--a2d4b7a0

Desktop (please complete the following information):

Additional context I've not tried this in any other browser (Safari's my daily driver) or OS.

Also of note -- sometimes I see it inserting in both the expected content and the original, but I can't repro this reliably. When it does so, however, the results are typically not saved correctly.

drenther commented 4 years ago

Thanks for reporting this. Will look into this. And update the thread as we go.

drenther commented 4 years ago

Hey, apologies for a bit of delayed update! I was able to reproduce it with the base screenshot app in macOS but was not able to reproduce with third party screenshot tools like lightshot. Maybe it's something to do with how the clipboard gets updated with the built-in screenshot app. I checked what we get in the files in JS and it seems like it's getting passed the old image. Making it difficult to be fixed on the editor side.

Will keep this issue open until we can either fix it or have some workaround! Thanks again.