3 ms·
I'd say Google has its own share of responsibility for the lack of adoption of APNGs. Chromium doesn't support them out of the box.
by aspensmonster 13y ago
I'd say Google has its own share of responsibility for the lack of adoption of APNGs. Chromium doesn't support them out of the box.
- TazeTSchnitzel 13y agoI suppose because that requires using libapng instead of libpng, maybe?
- maxst 13y agoAPNG support can be implemented on top of regular libpng. I have the working code.
- valarauca1 13y agoYou really shouldn't blame google, but blame KHTML (who's code base was forked to develop Webkit, and then Blink). KHTML didn't move to support apng until 2010-2011 which was a few years after the webkit fork.
- andyroid 13y agoSo to get this straight, we should blame the KHTML devs for adding a feature after Google forked it's code? While not blaming Google for never adding the feature?
- mpyne 13y agouh hwat? APNG was still years away when Webkit was forked from KHTML. Webkit was so long ago that Firefox didn't exist, nor did "Mozilla Firebird", and IIRC nor did Phoenix.