Add support data for image formats/codecs? (especially WebP) And media (video/audio) formats/codecs too?
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
As far as I can see we’re not yet storing support data in BCD for image formats/codecs.
The level of browser support for most image formats is the same across all browsers, so in general the data is arguably not something that web developers have a strong need for in practice.
But WebP at least seems like an exception to that; Apple only recently announced that they’d added support for it, in Safari 14 — but per https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types#WebP_image and https://wiki.developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types$compare?to=1647119&from=1643708 it seems that it’s not actually supported in desktop/macOS Safari yet but instead only on Mobile/iOS Safari.
https://caniuse.com/webp does have support data for WebP. So that’s further evidence that MDN probably should too.
And while the level of browser support for image formats in general may be the same across all browser, the level of browser support for video and audio formats and codecs is not — it’s much more complicated.
https://caniuse.com/?search=video%20format shows some relevant data.
Difficulties in being able to deliver video content in a format/codec that works across browser has been a pretty well-known pain point for developers — so having related support data for video and audio formats and codecs in BCD seems even more important and useful to developers than having it for image formats.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the WebP, image-format, video-format, and audio-format references linked in the issue, including the existing BCD context and Can I Use data. The issue does not name files or tests; first establish which formats and codecs are in scope and what support data should be added before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100