[w3ctag/design-reviews] WebCodecs (again!) (#612)

Ya ya yawm TAG!

I'm requesting a TAG review of WebCodecs.

An early review was conducted in #433. The API has changed *a lot* since then and we now have a draft specification. Please see discussion of deadlines (relatively soon) and and "you should also know that" below (upcoming work, open questions). 

Thank you for reviewing!

  - Explainer: https://github.com/WICG/web-codecs/blob/master/explainer.md

  - Specification URL: https://wicg.github.io/web-codecs/

  - Tests: https://github.com/web-platform-tests/wpt/tree/master/webcodecs

  - Security and Privacy self-review²: https://github.com/WICG/web-codecs/blob/master/security-privacy-questionnaire.md

  - GitHub repo (if you prefer feedback filed there): https://github.com/WICG/web-codecs/issues

  - Primary contacts (and their relationship to the specification):
      - Co-editor: Chris Cunningham (@chcunningham), Google
      - Co-editor: Paul Adenot (@padenot), Mozilla
      - Media WG co-chair: Mounir Lamouri (@mounirlamouri), Google
      - Media WG co-chair:  Jer Noble (@jernoble), Apple
  - Organization(s)/project(s) driving the specification: Google, Mozilla.
  - Key pieces of existing multi-stakeholder review or discussion of this specification: Co-editors meet regularly one-on-one and biweekly with with representatives from Intel and Microsoft and with members of WebRTC WG (all supportive). Artifacts of these meetings are mostly issues filed in our Github. 
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):
  https://www.chromestatus.com/feature/5669293909868544


Further details:
  -  [x] I have reviewed the TAG's [Web Platform Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: Chrome would like to ship this API version 91, which is anticipated to release May 25, 2021. The code freeze for this release will occur around April 14, 2021. 
  - The group where the work on this specification is currently being done: WICG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): [Migrating](https://github.com/WICG/web-codecs/issues/130) to Media WG
  - Major unresolved issues with or opposition to this specification: There are no major objections. Our Github tracks a number of open design questions. The most pressing are tagged with milestones.
  - This work is being funded by: Google/Mozilla (as employers of it's editors/implementers). 

You should also know that...
- Author feedback from the Chrome origin trial has been very positive and these users are eager to see it ship. This API has generated considerable user excitement ([twitter](https://twitter.com/search?q=webcodecs&src=typed_query&f=live), [discourse](https://discourse.wicg.io/t/webcodecs-proposal/3662))
- The API is no longer coupled to WhatWG Streams. Rationale [here](https://github.com/WICG/web-codecs/blob/master/explainer.md#integrating-with-whatwg-streams).
- We are particularly interested in input on this issue concerning transfer of BufferSource inputs: https://github.com/WICG/web-codecs/issues/104

- The previous tag review mentioned ImageDecoding. I will send a PR shortly to add this to the spec: https://github.com/dalecurtis/image-decoder-api


We'd prefer the TAG provide feedback as (please delete all but the desired option):
  🐛 open issues in our GitHub repo for **each point of feedback**

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/612