Attempting to configure an encoder with a bitrate of 0 should fail
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
https://w3c.github.io/webcodecs/#valid-videoencoderconfig
This errors out in Chromium, but not in Firefox, as things stand. Firefox considers 0 and not present as the same, Chrome rejects. I don't have a WebKit-based browser on this Linux desktop, so I'm not sure what it does.
Should it fail or no?
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
Read the WebCodecs valid-videoencoderconfig specification linked in the issue, then compare the stated bitrate=0 behavior in Chromium and Firefox. Done means resolving whether zero is invalid or equivalent to an omitted bitrate and recording the resulting specification or implementation direction; no repository files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, audio-video-rtc
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100