- From: chcunningham via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Apr 2021 20:53:24 +0000
- To: public-web-security@w3.org
chcunningham has just labeled an issue for https://github.com/w3c/security-request as "REVIEW REQUESTED": == WebCodecs 2021-04-14 == - name of spec to be reviewed: WebCodecs - URL of spec: https://w3c.github.io/webcodecs - Does your document have an in-line Security Considerations section, separate from Privacy Considerations? https://w3c.github.io/webcodecs/#security-considerations - Do you need a reply by a particular date? ASAP. Chromium is planning to ship this feature in mid July 2021, with code freeze occuring in late May. This doesn't close the door to changes (and certainly not additions), but providing feedback quickly gives us more opportunity to incorporate it without breaking sites. - Please point to the results of your own self-review (see https://w3ctag.github.io/security-questionnaire/) https://github.com/w3c/webcodecs/blob/main/security-privacy-questionnaire.md - Where and how to file issues arising? Please file as new issues in https://github.com/w3c/webcodecs/issues - Pointer to any explainer for the spec? https://github.com/w3c/webcodecs/blob/main/explainer.md Other comments: - Please reach out to me via email (chcunningham@chromium.org) ASAP to setup a virtual meeting (I'll loop in co-editors). The spec is dense with media domain knowledge and I expect a fair bit of in depth discussion. - 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)) FYI co-editors: @padenot (Mozilla) and @aboba (Microsoft) See https://github.com/w3c/security-request/issues/1 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 April 2021 20:53:26 UTC