Contact emailsfhernqv...@google.com, o...@google.com, hongc...@google.com, agpa...@google.com, gui...@google.com
Explainerhttps://github.com/WICG/web_audio_playout Specificationhttps://wicg.github.io/web_audio_playout Summary The AudioContext.playoutStats API allows an application to measure the quality and latency of audio playout using WebAudio. Blink componentBlink>WebAudio <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebAudio%22> TAG reviewEarly TAG review request: https://github.com/w3ctag/design-reviews/issues/939 TAG review statusIssues addressed Origin Trial NamePlayout Statistics API for WebAudio Chromium Trial NameAudioContextPlayoutStats Origin Trial documentation linkhttps://github.com/WICG/web_audio_playout WebFeature UseCounter namekAudioContextPlayoutStats Risks Interoperability and Compatibility None *Gecko*: No signal *WebKit*: No signal *Web developers*: Positive ( https://github.com/WICG/proposals/issues/142#issuecomment-1981012486) *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 Goals for experimentation Reason this experiment is being extended We need additional time to work with Privacy WG to address their concerns. Since the origin trial started, we have made the following progress: * The API was presented at TPAC, and got a positive reaction from Audio WG. However, they wanted to hear the Privacy WG's input, and that we should ask the internal privacy/security reviewers why the API is ok while the similar RenderCapacity API was not ok. ( https://docs.google.com/document/d/1QiBmVZb51ATyai_TTbkMnq25zaQOzVNxNIsPJZ8sdUE/edit?tab=t.0#heading=h.el9c5z4prh05 ) * We have presented the API to the Privacy WG and they have discussed it ( https://github.com/w3c/privacywg/blob/main/minutes/privacywg-20250417.md#webaudio) . We are now having an active discussion with them about how we can address their concerns. * Google-internal privacy/security reviewers have reaffirmed that the API is ok, and safer than the RenderCapacity API. * We have added wpt tests for the API. Ongoing technical constraints None. Debuggability Can be tested by creating an AudioContext and evaluating context.playoutStats in the console. 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/webaudio/the-audio-api/the-audiocontext-interface/audiocontext-playoutstats.html?label=experimental&label=master&aligned These will be updated if the API shape changes. Flag name on about://flagsNone Finch feature nameAudioContextPlayoutStats Requires code in //chrome?False Estimated milestones Origin trial desktop first 131 Origin trial desktop last 136 Origin trial extension 1 end milestone 139 DevTrial on desktop 129 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5172818344148992?gate=5074057867034624 Links to previous Intent discussionsIntent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACazmWW4MYVa_iGjN%3DK4O9B1DE3rt4_2Vkqnq6sKswHFjn6BzQ%40mail.gmail.com Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACazmWWV6S6Ba%3Dd%3DgvjhERm1OnPyBMRJx5fbkP%3Df9zb3k%3DrNDA%40mail.gmail.com 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACazmWVkWb8DJM_aCRGOFpskBs-7h%3DO_yggKc3YBUkiieEO-UA%40mail.gmail.com.
