LGTM3 On 6/11/25 11:24 AM, Yoav Weiss (@Shopify) wrote:
LGTM2On Wednesday, June 11, 2025 at 5:24:05 PM UTC+2 Chris Harrelson wrote: LGTM1 On Mon, Jun 9, 2025 at 10:29 AM Chromestatus <ad...@cr-status.appspotmail.com <mailto:ad...@cr-status.appspotmail.com>> wrote: Contact emails gui...@chromium.org Explainer https://github.com/guidou/webrtc-encoded-transform/blob/master/audio_level.md <https://github.com/guidou/webrtc-encoded-transform/blob/master/audio_level.md> Specification https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedaudioframemetadata-audiolevel <https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedaudioframemetadata-audiolevel> Summary This feature consists in exposing to the Web the audio level of an encoded frame transmitted via RTCPeerConnection and exposed using WebRTC Encoded Transform. Blink component Blink>WebRTC>PeerConnection <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebRTC%3EPeerConnection%22> TAG review https://github.com/w3ctag/design-reviews/issues/1096 <https://github.com/w3ctag/design-reviews/issues/1096> TAG review status Pending Risks Interoperability and Compatibility The interoperability risk is low as all major browsers have consensus around it. The main risk is that some browsers take a long time to implement it. The compatibility risk is zero, as this is a strictly additive feature that does not interfere with existing features. /Gecko/: Positive (https://github.com/mozilla/standards-positions/issues/1232 <https://github.com/mozilla/standards-positions/issues/1232>) The official position has not yet been answered, but Mozilla's representative (and co-chair) in the WebRTC WG approved adding this to the spec. https://github.com/w3c/webrtc-encoded-transform/pull/253#pullrequestreview-2825299429 <https://github.com/w3c/webrtc-encoded-transform/pull/253#pullrequestreview-2825299429> /WebKit/: Positive (https://github.com/WebKit/standards-positions/issues/496 <https://github.com/WebKit/standards-positions/issues/496>) The official position has not yet been answered, but Apple's representative (and co-chair) in the WebRTC WG approved adding this to the spec. https://github.com/w3c/webrtc-encoded-transform/pull/253#pullrequestreview-2844026129 <https://github.com/w3c/webrtc-encoded-transform/pull/253#pullrequestreview-2844026129> /Web developers/: No signals /Other signals/: Ergonomics None Activation None Security None 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 None 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 https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCEncodedAudioFrame-audiolevel.html?label=experimental&label=master&aligned <https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCEncodedAudioFrame-audiolevel.html?label=experimental&label=master&aligned> https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCEncodedAudioFrame-metadata.https.html?label=experimental&label=master&aligned <https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCEncodedAudioFrame-metadata.https.html?label=experimental&label=master&aligned> Flag name on about://flags None Finch feature name RTCEncodedFrameAudioLevel Rollout plan Will ship enabled for all users Requires code in //chrome? False Tracking bug https://crbug.com/418116079 Availability expectation Feature is available on Web Platform Baseline eventually. Adoption expectation Feature is used by specific partner(s) to provide functionality within 12 months of launch in Chrome Estimated milestones Shipping on desktop 139 Shipping on Android 139 Shipping on WebView 139 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/5206106602995712?gate=5185213466148864 <https://chromestatus.com/feature/5206106602995712?gate=5185213466148864> This intent message was generated by Chrome Platform Status <https://chromestatus.com>.-- You received this message because you are subscribed to theGoogle Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org <mailto:blink-dev+unsubscr...@chromium.org>. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68469b40.710a0220.d824b.047a.GAE%40google.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68469b40.710a0220.d824b.047a.GAE%40google.com?utm_medium=email&utm_source=footer>. --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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ffeaefc9-54aa-402b-91d9-b813de336aedn%40chromium.org <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ffeaefc9-54aa-402b-91d9-b813de336aedn%40chromium.org?utm_medium=email&utm_source=footer>.
-- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2092a81c-2641-4466-a519-01a958996b3d%40chromium.org.
