Should VideoEncoderConfig cloning remove parameters that are not useful for a given codec?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
According https://w3c.github.io/webcodecs/#clone-configuration, the configuration should be cloned, hence all members of VideoEncoderSupport should be copied.
Chrome in https://wpt.live/webcodecs/video-encoder-config.https.any.html assumes that the avc member will not be cloned if the codec is vp8. Safari simply clones all members it knows.
The note in https://w3c.github.io/webcodecs/#dom-videoencoder-isconfigsupported says that only recognised dictionary members will be copied. recognised could be interpreted both ways.
It would be good to clarify the intent here.
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 with the WebCodecs clone-configuration section and the VideoEncoderSupport and VideoEncoderIsConfigSupported definitions linked in the issue. Compare their wording with the referenced Web Platform Tests and the Chrome and Safari behaviors. Done means the specification clearly states whether codec-specific members such as avc are copied.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100