New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Require img
to be able to load the same video formats as video
supports
#7141
Comments
cc @whatwg/media |
As someone who works for CDN with animation conversion feature: animated WebP is bad. We would prefer not to use it. The animated WebP format has been designed to be conceptually similar to GIF, and work for the same use-cases that GIF does, but this made it inherit GIF's weaknesses. Content that makes GIF sizes balloon typically also compresses poorly in WebP. Both are especially inefficient for short video clips with camera motion — a use-case handled better even by ancient codecs like MPEG-1. WebP often fails to meaningfully reduce GIF file sizes, and can even end up making files larger than GIF. |
@eeeps on why GIF is still used: https://twitter.com/etportis/status/1442838357432700932
https://twitter.com/etportis/status/1443218535774253060
|
From an end-user perspective: the human doesn't really know the difference between a gif and an mp4 except perhaps the length of play. They are all 'gifs' to most humans. |
A few considerations that should be defined:
|
gif's can technically be streamed, so I think video streams should be allowed as well.
This would be hard to set, because I know it's possible with with at least VP8 to actually change the size of the video with each frame. |
A concern I have about the current Chrome approach of allowing AV1 wrapped in AVIF in an img tag, but not AV1 wrapped in any other container, is the following: What about Nokia's patent claims on HEIF? AV1 is designed to be royalty-free, but the HEIF container that AVIF uses may not actually be royalty-free — at least Nokia does not give a patent grant, except for non-commercial purposes. See also: https://news.ycombinator.com/item?id=19874121 If we could use AV1 in any video container (in particular, in a non-patent-encumbered one), and not be forced to wrap it specifically in AVIF (which is based on HEIF), I would consider that a lot safer regarding potential patent trolling when adoption becomes larger and Nokia smells money. It would make perfect sense for them to lay low now and wait for more adoption before they start demanding royalties. These patents will only expire around 2035-2036, so they could be a problem. |
For accessibility purposes, there are probably scenarios where you'll have to offer a way to pause the video. Will From WCAG 2.1, potential friction point if an image can't be paused: 2.2.2 Pause, Stop, Hide. |
@Sheraff This problem already exists for GIF. The difference is not in user-visible behavior (which I agree should be improved!), but in allowing smaller file sizes. |
@kornelski this solution is being debated as
|
Why would So I think all of the following would be good, and they are imo orthogonal issues:
|
@jonsneyers the So in my opinion, this change should either land with accessibility in mind, or land at the same time as some changes to the |
This issue is not about the |
@Sheraff can you file a new issue about the ability to pause animated images in |
Related to #6363
Regardless of what changes are made or not made to
video
, the question of which formatsimg
should support remains. That's this issue.WebKit supports video formats in
img
, while Gecko and Chromium do not.In https://bugs.chromium.org/p/chromium/issues/detail?id=791658 it was requested that Chromium support MP4/h.264 in
img
. The issue was closed asWontFix
:For the last point,
video
today doesn't have the same capabilities asimg
(e.g.srcset
,media
).For AVIF, I asked on Twitter if there are reasons why it would still make sense to support other video formats assuming
img
can load AVIF: https://twitter.com/zcorpan/status/1428459457407864836@jonsneyers
@kornelski
@jernoble
@zcorpan replied
@othermaciej replied
The text was updated successfully, but these errors were encountered: