I replied to 3 comments adressing this...

Fair concern, permission prompts should never be silent surprises. Fully on me for not flagging it in the changelog.

Context: v1.3.0 added a "Copy image to clipboard" context-menu item (commit 2f9a5ec, P) to close issue #4. The
extension is open-source so the full diff is public. The actual clipboard code only writes an image — it never reads:

// src/offscreen/offscreen.js
const clipboardItem = new ClipboardItem({ [mimeType]: blob });
await navigator.clipboard.write([clipboardItem]);

Search the repo for clipboard.read or readText, you won't find a single call. The clipboardRead permission in the manifest was a mistake on my part (copy-pasted
alongside clipboardWrite) and was never used by any code path.

Since the feature is also unreliable on Firefox and is making people reasonably uneasy, I'm removing it entirely in the next release, both the feature and both clipboard permissions. The next version will ask for strictly fewer permissions than before. Sorry for the scare.

Fair concern, permission prompts should never be silent surprises. Fully on me for not flagging it in the changelog.

Context: v1.3.0 added a "Copy image to clipboard" context-menu item (commit 2f9a5ec, P) to close issue #4. The
extension is open-source so the full diff is public. The actual clipboard code only writes an image — it never reads:

// src/offscreen/offscreen.js
const clipboardItem = new ClipboardItem({ [mimeType]: blob });
await navigator.clipboard.write([clipboardItem]);

Search the repo for clipboard.read or readText, you won't find a single call. The clipboardRead permission in the manifest was a mistake on my part (copy-pasted
alongside clipboardWrite) and was never used by any code path.

Since the feature is also unreliable on Firefox and is making people reasonably uneasy, I'm removing it entirely in the next release, both the feature and both clipboard permissions. The next version will ask for strictly fewer permissions than before. Sorry for the scare.

Fair concern, permission prompts should never be silent surprises. Fully on me for not flagging it in the changelog.

Context: v1.3.0 added a "Copy image to clipboard" context-menu item (commit 2f9a5ec, P) to close issue #4. The
extension is open-source so the full diff is public. The actual clipboard code only writes an image — it never reads:

// src/offscreen/offscreen.js
const clipboardItem = new ClipboardItem({ [mimeType]: blob });
await navigator.clipboard.write([clipboardItem]);

Search the repo for clipboard.read or readText, you won't find a single call. The clipboardRead permission in the manifest was a mistake on my part (copy-pasted
alongside clipboardWrite) and was never used by any code path.

Since the feature is also unreliable on Firefox and is making people reasonably uneasy, I'm removing it entirely in the next release, both the feature and both clipboard permissions. The next version will ask for strictly fewer permissions than before. Sorry for the scare.

Hey, thanks for the report, you were right, it was broken. Just pushed a fix, update the extension and it should properly convert the files again. Sorry about that!