I've flipped all the reviews and will update this thread when they are all completed.
Thanks! On Wed, Mar 27, 2024 at 8:25 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > Hey! Can you flip on the various reviews (privacy, enterprise, etc) in the > chromestatus entry? > > On Tuesday, March 26, 2024 at 11:29:53 PM UTC+1 Thomas Guilbert wrote: > >> Contact emailstguilb...@chromium.org >> >> ExplainerNone >> >> Specification >> https://w3c.github.io/webcodecs/opus_codec_registration.html#dom-opusencoderconfig-signal >> >> Summary >> >> `OpusEncoderConfig.signal` and `OpusEncoderConfig.application` were >> recently added to the WebCodecs spec [1]. Both parameters are mapped >> directly to implementation specific encoder knobs. These allow web authors >> to provide hints as to what type of data is being encoded, and in which >> context the data is being used. `signal` can be one of {"auto", "music", >> "voice"}. It configures the encoder for the best performance in encoding >> the specified type of data. `application` can be one of {"voip", "audio", >> "lowdelay"}. It configures the encoder to favor speech intelligibility, >> faithful reproduction of the original input, or minimal latency. [1] : >> https://github.com/w3c/webcodecs/pull/777 >> >> >> Blink componentBlink>Media>WebCodecs >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMedia%3EWebCodecs> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: Positive (https://github.com/w3c/webcodecs/pull/777) Spec >> change approved by Mozilla representative. For an almost identical feature, >> Mozilla said the "request for standards position" was not warranted, as >> they were active spec participants: >> https://github.com/mozilla/standards-positions/issues/837#issuecomment-1614666364 >> >> *WebKit*: No signal. Review from WebKit was requested on the spec change. >> >> *Web developers*: No signals >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >> >> >> Debuggability >> >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, 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 >> >> Existing WPTs will be modified to cover this feature: >> https://wpt.fyi/results/webcodecs/audio-encoder-config.https.any.html >> >> >> Flag name on chrome://flagsNone >> >> Finch feature nameNone >> >> Non-finch justification >> >> Simple parameter changes. >> >> >> Requires code in //chrome?False >> >> Estimated milestones >> Shipping on desktop 125 >> Shipping on Android 125 >> >> Anticipated spec changes >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> None >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5165257615212544 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/> and edited by hand afterwards. >> > -- 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/CABrVPoaRikGovi9Se141CxF6Sk92r62HUZHMNj1%3DddYHHXnXVQ%40mail.gmail.com.
