w3c
APNG implementation
This issue is for tracking implementations, including patches to libpng, to various browsers, etc.
Reading/Displaying APNG
- Chromium Code Reviews, Issue 1567053002: Animated PNG implementation
- patched libpng 1.6.26
- older patches by Andrew Smith, useful history in there plus sample images for testing
Generating APNG
There is a list of various image editors and command line tools
Of those TweakPNG looks useful for creating WPT tests and the source is on GitHub which might allow adding support for new chunks.
APNG tests
- https://philip.html5.org/tests/apng/tests.html
- http://littlesvr.ca/apng/test.html
Should there be a "needs implementation" label? Is that what the "implementation" label means?
Previously, I was thinking each issue should have 1 "needs ___" label to indicate how to make progress. But this is sort of a meta issue, covering both implementation and tests.
Maybe we should file separate issues, keep the 1 "needs ____" alive, and add a "needs child issue fixed" label?
Pull request for APNG tests https://github.com/web-platform-tests/wpt/pull/42893
Web Platform Tests for png now have 28 tests for APNG. Chrome (and Edge, and other blink-based browsers) pass 28/28, as does Firefox. Safari passes 22/28.
More tests should be added for error handling (testing fallback to the static PNG image if the APNG is invalid) which depends on
- https://github.com/w3c/PNG-spec/issues/360
28/28 passes in two independent browsers (Chrome and Firefox) means that APNG meets the W3C criteria for interoperable implementation. Removing the blocking-exit tag, and leaving issue open to track implementation status for implementation report.
I see that the GIMP forum describes APNG as a deprecated format and encourages use of WebP instead. However there is a GIMP APNG plugin.
It requires a specific unofficial APNG patch to libpng (there are multiple patches that add APNG support, hindering interoperability)