Apologies, the tracking and launch bugs in the original email are interchanged. The correct details are:
*Tracking bug* https://crbug.com/1216187 *Launch bug* https://crbug.com/1355977 On Tuesday, August 30, 2022 at 10:02:18 AM UTC-7 Ajay Rahatekar wrote: > Contact emails > > hong...@chromium.org, alv...@chromium.org, mjwi...@chromium.org > > Explainer > > None > > Specification > > https://github.com/WebAudio/web-audio-api/pull/2498 > > Summary > > AudioContext.setSinkId sets the ID of the audio device to use for output. > This allows the AudioElement to route audio to a connected output device of > user's choosing. > > > Blink component > > Blink>WebAudio > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebAudio> > > TAG review > > This is a small API change within Web Audio API. The WG was advised that > this is too small for the TAG review. > > TAG review status > > Not applicable > > Risks > > Interoperability and Compatibility > > Gecko: Positive (https://github.com/WebAudio/web-audio-api/issues/2400) > Mozilla is co-developing the spec change. > > WebKit: No signal > > Web developers: Positive ( > https://github.com/WebAudio/web-audio-api/issues/2400) Many developers > chimed in the spec issue and the implementation crbug entry ( > crbug.com/1216187). Also several partners expressed the need for this > API. We have not seen any negative feedback on this. > > 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? > > > Debuggability > > This adds a new method to AudioContext; the WebIDL change will be > addressed by the DevTools automatically. > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > Yes > > This is a part of Web Audio API, which is available on all platforms. > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > Yes. The WPT will be added for this feature. > > Flag name > > –enable-blink-features=AudioContextSetSinkId > > Requires code in //chrome? > > False > > Tracking bug > > https://crbug.com/1355977 > > Launch bug > > https://crbug.com/1216187 > > Estimated milestones > > 108 > > > 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/5190163462881280 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > > -- > Ajay Rahatekar | Technical Program Manager | ajayra...@google.com | > 650-797-1279 <(650)%20650-797-1279> > -- 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/34425811-7d74-4b1d-ad7a-cddeb7a0aadcn%40chromium.org.
