#18195 closed enhancement (fixed)
libpng-1.6.40
Reported by: | Bruce Dubbs | Owned by: | Douglas R. Reno |
---|---|---|---|
Priority: | normal | Milestone: | 12.0 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New point version.
Change History (6)
follow-up: 2 comment:1 by , 22 months ago
comment:2 by , 21 months ago
Replying to Xi Ruoyao:
The apng patch for 1.6.39 still applies (with some offsets) but I'm not sure if it will be fine at runtime.
Works for me, in that I've rebuilt firefox-102.12.0 with it, and example apng files on web pages seem to move as expected. I've also built firefox-115.0b7 withit, and similar results. Using our current version of ImageMagick (not recompiled!) with plain png files seem ok.
From past experience, if a separate apng patch is going to be introduced, it might take a while.
As far as firefox is concerned they might ship their modified 1.6.39 in firefox-116. I've no idea if there is anything urgent about 1.6.40.
comment:3 by , 21 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 21 months ago
Changes from version 1.6.39 to version 1.6.40 --------------------------------------------- * Fixed the eXIf chunk multiplicity checks. * Fixed a memory leak in pCAL processing. * Corrected the validity report about tRNS inside png_get_valid(). * Fixed various build issues on *BSD, Mac and Windows. * Updated the configurations and the scripts for continuous integration. * Cleaned up the code, the build scripts, and the documentation.
comment:5 by , 21 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The apng patch for 1.6.39 still applies (with some offsets) but I'm not sure if it will be fine at runtime.