13 ms·
Safari already accepts MP4 in an <img> tag and it is autoplayed, muted and looped [1]. Sadly, Chrome doesn't want to implement it [2]. [1] https://developer.ap
by gardaani 5y ago
Safari already accepts MP4 in an <img> tag and it is autoplayed, muted and looped [1]. Sadly, Chrome doesn't want to implement it [2].
[1] https://developer.apple.com/documentation/webkit/delivering_video_content_for_safari#3030249 https://developer.apple.com/documentation/webkit/delivering_...
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=791658#c36 https://bugs.chromium.org/p/chromium/issues/detail?id=791658...
- acdha 5y agoThis is a great example for the “Chrome is the new IE” debate: that’s a feature which would immediately make the web better but they held back support for a standard, hardware-accelerated format trying to force mainstream adoption of their own format which had limited tool support and never performed enough better than JPEG/PNG to be worth the trouble for most sites.
- pwdisswordfish8 5y agos/better/worse/
- acdha 5y agoYou think it's good that people keep using gigantic GIF files rather than smaller videos? There's no technical reason to prefer the GIF format — it burns data transfer, requires more CPU, and has terrible quality.
- pwdisswordfish8 5y agoI prefer <img> elements never to animate at all, regardless of format. Animations should use <video>.