Add origin clean check on objects that support it.
Open
Nobody has claimed this yet.
editorial
privacy-needs-resolution
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
When HTMLCanvasElement is passed to the VideoFrame constructor, the 'origin-clean' concept isn't checked.
This should possibly be added to the step:
- If the origin of image’s image data is not same origin with the entry settings object's origin, then throw a SecurityError DOMException.
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 VideoFrame constructor algorithm and the HTML specification's origin-clean concept for HTMLCanvasElement image data. Check how the constructor currently handles canvas inputs and compare the proposed same-origin and SecurityError behavior with nearby steps. Done means the specification clearly covers origin-clean validation for supported objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100