Recenzje dodatku Save image as Type
Save image as Type Autor: D7OM
9 recenzji
- Ocena: 1/5Autor: Użytkownik Firefoksa 17682403, 2 miesiące temuI saw the prompt requesting clipboard access and instantly removed it.
- Ocena: 1/5Autor: Nox, 2 miesiące temuAlways sus when a browser extension suddenly wants extra permissions.
Odpowiedź autora
Data: 2 miesiące temuFair 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. - Ocena: 1/5Autor: Madison, 2 miesiące temuuntil an actual explanation is given as to why something like this needs access to your clipboard, you should probably stay away from this addon, might have been compromised or sold
Odpowiedź autora
Data: 2 miesiące temuFair 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. - Ocena: 1/5Autor: SnakeCRO, 2 miesiące temuWhy do you suddenly need data from the clipboard? Makes no sense.
Odpowiedź autora
Data: 2 miesiące temuFair 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. - Ocena: 1/5Autor: AziSlays, 3 miesiące temuThis add-on used to work. It used to actually download the files as the type you select. As of the last time I updated it, now it downloads them as whatever they are but just changes the file extension to the one you chose. For those unaware, that doesn't provide ANY of the benefits various file types would have. The big PNGs will still be just as big, the jpgs will still have artifacting, and the webps will still not function in many programs.
Literally all you had to do was make no changes to the add-on and it would have stayed good. wth manOdpowiedź autora
Data: 2 miesiące temuHey, 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! Odpowiedź autora
Data: 10 miesięcy temuPlease try again after updating. If the issue persists, kindly open a new issue at https://github.com/d7omdev/Save-Image-as-Type/issues with details of what’s happening.