3 ms·
There is no reason clients can't encode a GIF or APNG to H.264, cache that, then use the hardware video decoder on the GPU to render it. Whether that would be a
by xenadu02 10y ago
There is no reason clients can't encode a GIF or APNG to H.264, cache that, then use the hardware video decoder on the GPU to render it. Whether that would be a win for performance or battery life probably depends on the exact hardware and how many of these things are displayed at the same time.
- bgirard 10y agoUsing the optimized video code paths for GIF was discussed by the Mozilla graphics team several times. Basically the conclusion is that it's a lot of work when there's a perfectly good alternative which is using a video element. Effort that can be better spent elsewhere.
- husky84 10y agomaybe let Mozilla know that it would be very helpful to their non-profit cause if they spent some time in rust making this work better. they spend a lot of time adding new milestones, but this is one which could improve the quality of the web. or they could design an extension which converts gifs to pdfs and we could continue to use their software for what it is: zero day gateway with attached subscribers to a non profit software engine company which spends a bunch of time doing what they feel could make their impact last any longer than it already has at least then the pdf would open in chrome :)
- untog 10y agoThat's a shame, because there is a hell of a lot of legacy content out there that's never going to get converted.
- samk117 10y agotranslucency