w3c / w3c/webcodecs

Close and transfer (buffer stealing)

Open
#287 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

extension
Dominant language
HTML
Stars
1.3k
Forks
194
Avg merge
1d 13h
Merged PRs (30d)
3

Description

@padenot raised idea in editors call to frame.close() -> transfer cpu data immediately to ArrayBuffer. Tracking here to ponder it more.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the proposed frame.close() behavior and its transfer of CPU data to an ArrayBuffer. Determine the intended API semantics and scope for this idea, then record an agreed design or resolution in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.