사진을 JPG/PNG/WebP로 저장에 대한 리뷰
사진을 JPG/PNG/WebP로 저장 제작자: D7OM
리뷰 9개
- 5점 만점에 1점Firefox 사용자 17682403 님, 한 달 전I saw the prompt requesting clipboard access and instantly removed it.
개발자 답글
한 달 전에 게시됨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.- This 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 man개발자 답글
2달 전에 게시됨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!