Repository navigation
Do not set TIFF dpi when resolution tags are missing - #10339
Merged
Merged
Conversation
brettdavies
force-pushed
the
tiff-no-resolution
branch
from
October 28, 2026 22:41
d0bb93f to
ab2bef6
Compare
radarhere
enabled auto-merge (squash)
October 29, 2026 06:38
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
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.
Fixes #10332.
Changes proposed in this pull request:
XResolutionnorYResolutionno longer reportsdpi == (1, 1)andresolution == (1, 1). It reports neither key, as a PNG or JPEG saved without a resolution does, and as BMP does since Ignore (0, 0) BMP DPI #10187._setup()clearsdpiandresolutionbefore reading each frame, so a frame without resolution tags does not keep the previous frame's values.