@nergal @matt @hund @dirtycommo @tzycce apparently APNG still had smaller sized files without quality loss: http://littlesvr.ca/apng/gif_apng_webp.html sources from https://en.wikipedia.org/wiki/WebP
@RyuKurisu @nergal @matt @hund@linuxrocks.online @dirtycommo @tzycce@linuxrocks.online The problem is, APNG violates the PNG spec, so Mozilla has to maintain their own fork of libpng.
Having learned from the mess with static vs. animated GIF, the PNG spec says:
> The first eight bytes of a PNG datastream always contain the following (decimal) values:
>
> 137 80 78 71 13 10 26 10
>
> This signature indicates that the remainder of the datastream contains a single PNG image
@RyuKurisu @nergal @matt @hund@linuxrocks.online @dirtycommo @tzycce@linuxrocks.online
Partly because I sympathize, partly because I respect the PNG spec, and partly because there's no CSS directive to disallow animation in things loaded via <img> tags, I design any software which treats images as more than just application/octet-stream to treat APNG as corruption and and inform the uploader that corruption was detected and an attempt to repair the file was made.
(ie. load and save the file to discard all but the first frame at the cost of also discarding any unrecognized chunk types that declare themselves as "ancillary, unsafe to copy" ...also in accordance with the PNG spec.)
