https://w3c.github.io/webcodecs/#dom-videoframe-videoframe could check origin-clean sooner
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
The VideoFrame constructor is first checking usability (and will throw as needed) and then check origin-clean.
Chrome apparently does it as per spec.
Safari checks origin-clean first then checks usability.
It seems slightly preferable to check origin-clean first, to prevent any potential information leak.
One edge case where it might be useful is if the image is not origin-clean and is only partially decodable or if its natural width or height is zero.
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 at the linked VideoFrame constructor section in the WebCodecs specification and compare the ordering of the usability and origin-clean checks described in the issue. Determine the intended normative behavior, including the partially decodable or zero-dimension edge case; done means the specification reflects an agreed ordering and its consequences are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100