[GH-ISSUE #199] Separate Auto Lossy and Lossless #88

Closed
opened 2026-02-25 22:34:19 +03:00 by kerem · 3 comments
Owner

Originally created by @TiKevin83 on GitHub (Nov 13, 2018).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/199

Right now a source png image will only be compressed in auto output mode if the browser supports webp, otherwise it will stay as a png. It would be useful either to have separate auto lossy and auto lossless output modes to change the fallback order to webp->jpg->png, or to have the auto output mode choose a fallback order depending on the presence and value of the quality setting (that is, if a user asks for q_85 assume that they want auto lossy mode).

Originally created by @TiKevin83 on GitHub (Nov 13, 2018). Original GitHub issue: https://github.com/flyimg/flyimg/issues/199 Right now a source png image will only be compressed in auto output mode if the browser supports webp, otherwise it will stay as a png. It would be useful either to have separate auto lossy and auto lossless output modes to change the fallback order to webp->jpg->png, or to have the auto output mode choose a fallback order depending on the presence and value of the quality setting (that is, if a user asks for q_85 assume that they want auto lossy mode).
kerem 2026-02-25 22:34:19 +03:00
Author
Owner

@baamenabar commented on GitHub (Nov 15, 2018):

Hello @TiKevin83 ! that's a quite useful use case.
I'll add it to 1.2 milestone
thanks for the feedback

<!-- gh-comment-id:438999287 --> @baamenabar commented on GitHub (Nov 15, 2018): Hello @TiKevin83 ! that's a quite useful use case. I'll add it to 1.2 milestone thanks for the feedback
Author
Owner

@github-actions[bot] commented on GitHub (Aug 15, 2023):

This issue is stale because it has been open for 30 days with no activity.

<!-- gh-comment-id:1678324181 --> @github-actions[bot] commented on GitHub (Aug 15, 2023): This issue is stale because it has been open for 30 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Aug 29, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

<!-- gh-comment-id:1696679344 --> @github-actions[bot] commented on GitHub (Aug 29, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/flyimg#88
No description provided.