Fix Resolution Filter Showing 0 * 0#797
Merged
Merged
Conversation
Owner
|
Nice fix! 🛠️ This makes the solution way more robust. Merging it right now. Appreciate the contribution! 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem:
The resolution filter (Image Search / Size) incorrectly displays 0 * 0 for all of my images, which were generated by ComfyUI. This happens because the filter relies on Size-1 and Size-2 metadata fields, which ComfyUI doesn’t include.
Solution:
Replaced metadata-based resolution checks with direct image dimension extraction using Pillow. This makes it completely independent of metadata standards and the tools used to generate the image. It should be able to handle any image format (JPEG/PNG/WEBP) as long as Pillow supports it.