Treat frame durations <= 10 ms as if they were 100 ms #108
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.
The behavior of JPEGView differs from the major web browsers when displaying animated images with frame durations <= 10.
Currently, JPEGView displays all 0ms GIF frames as 100ms, and all <10ms frames (for other formats) as 10ms.
Most web browsers display all <=10ms frames as 100ms:
Some examples that display differently in JPEGView:
0-delay APNG
1-delay GIF (centiseconds)
Some relevant posts:
The Fastest GIF Does Not Exist
Animated GIF Minimum Frame Delay Browser Compatibility Study