Allowing decoupling of decoding and demuxing for images
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
There are a number of container formats that can hold a variety of different codecs’ coded data as well as the possibility of the same coded data appearing in a variety of containers.
If a demuxing API is later considered (as it's not infrequently brought up during calls and discussions with developers, https://github.com/w3c/webcodecs/issues/24 for tracking, certainly less urgent than decoders!), this could be handled by desugaring the image decoding API maybe ?
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
No files, tests, or implementation entry points are named. Start by reviewing the current image decoding API and the linked demuxing discussion in issue 24; done would require an agreed API design that cleanly separates decoding from demuxing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100