SVG images cannot be copied when hovered

logseq / logseq

A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: http://trello.com/b/8txSM12G/roadmap

GNU Affero General Public License v3.0

30.26k stars 1.77k forks source link

Search first

[X] I searched and no similar issues were found

What Happened?

Adding an SVG image into Logseq works the same as a PNG or JPEG image.
However, when hovering the image, the 'Copy Image' button does not do anything.

Is this a bug or is it a feature ? I would find it extremely helpful in my workflow !

Reproduce the Bug

Add an SVG to a block
```
![image_name](../assets/image.svg)
```
hover the image
left click on the 'Copy Image' button
Paste (ex. Ctrl+V) in another software (ex. Inkscape)

Expected Behavior

I expect the same behavior as with PNG images : being able to copy/paste images from Logseq to another software like Inkscape.

Screenshots

No response

Desktop or Mobile Platform Information

I tried this on both :

Arch Linux, with this AUR package
Ubuntu 20.04.6 LTS, with Logseq-linux-x64-0.9.20.AppImage

and observed the same behavior.

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

[ ] I'm willing to submit a PR (Thank you!)

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!

logseq / logseq