Contact emailschcunning...@chromium.org Explainerhttps://github.com/w3c/webcodecs/blob/main/explainer.md
Specificationhttps://w3c.github.io/webcodecs Summary This feature tracks adding a single event named "dequeue" and event handler to the audio and video encoder and decoder interfaces (e.g. AudioDecoder.ondequeue). Authors initially queue up encoding or decoding work by calling encode() or decode() respectively. The new "dequeue" event is fired to indicate when the underlying codec has ingested some/all of the queued work. The decrease in the queue size is already reflected by a lower value of encoder.encodeQueueSize and decoder.decodeQueueSize attributes. The new event eliminates the need for authors to setTimeout() poll to determine when the queue has decreased (i.e. when they should queue up more work). See mentions of "dequeue" in the WebCodecs specification https://w3c.github.io/webcodecs/#audiodecoder-event-summary Blink componentBlink>Media>WebCodecs <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMedia%3EWebCodecs> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/612 Note that TAG did not review this new "dequeue" event specifically. TAG review statusIssues addressed Risks Interoperability and Compatibility Low risk. At present Chromium is the only implementer of WebCodecs generally. This is a minor addition to WebCodecs APIs that should be straightforward for future implementers to incorporate. The spec change to add this event was approved by representatives from Edge and Firefox. https://github.com/w3c/webcodecs/pull/439 *Gecko*: Positive (https://github.com/mozilla/standards-positions/issues/209) Firefox is helping co-edit spec (Paul Adenot) *WebKit*: No signal Expressed mixed interest/concerns. https://lists.webkit.org/pipermail/webkit-dev/2020-May/031191.html https://lists.webkit.org/pipermail/webkit-dev/2021-February/031691.html *Web developers*: Strongly positive See blurbs from OT participants at the bottom of the I2S. https://groups.google.com/a/chromium.org/g/blink-dev/c/7UlTzFMbTFs *Other signals*: Edge: Positive, co-editing the spec (Bernard Aboba) Ergonomics No risks Activation No risks Security No risks WebView application risks No risks. Debuggability The event may be debugged in typical fashion by setting breakpoints or logging in the event handler. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes Requires code in //chrome?False Tracking bughttps://crbug.com/1341116 Non-OSS dependencies No dependencies. Estimated milestones 105 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5195706034290688 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALG6eSrkzPiW8tconoPnduyaY%3DZSPHSFE6djL6kcDWHsk%3DtnrA%40mail.gmail.com.
