Intent to Ship: windowAudio for getDisplayMedia()

[Chromestatus]

Contact emails

kr...@chromium.org, ol...@chromium.org, elad...@chromium.org

Explainer

https://github.com/drkron/explainers/blob/main/windowAudio_Explainer.md

Specification

https://w3c.github.io/mediacapture-screen-share/#displaymediastreamoptions

Summary

Extends DisplayMediaStreamOptions for getDisplayMedia() with a windowAudio option. This new option allows web applications to hint to the user agent whether the user should be offered the ability to share audio when a window is selected. windowAudio can be set to exclude, system, or window based on application preference. A web application that is configured for audio capture but wants to limit system audio capture when a window is selected should set windowAudio: "exclude".

Blink component

Blink>GetDisplayMedia

TAG review

https://github.com/w3ctag/design-reviews/issues/1110

TAG review status

Issues addressed

Risks

Interoperability and Compatibility

None

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1254)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/516)

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

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

Is this feature fully tested by web-platform-tests?

No

Flag name on about://flags

N/A

Finch feature name

GetDisplayMediaWindowAudioCapture

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Launch bug

https://launch.corp.google.com/launch/4406027

Adoption expectation

Feature is used by specific partner(s) to provide functionality within 12 months of launch in Chrome.

Estimated milestones

Shipping on desktop

141

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/5072779506089984?gate=5202913928151040

This intent message was generated by Chrome Platform Status.

[Alex Russell]

Not a vote either way, but we generally expect to see example code (rather than IDL) when introducing a proposed solution in an Explainer, and also it is generally good form to add example code for considered alternatives.

Best,

Alex

[Johannes Kron]

Hi Alex,

Thanks for the feedback. I've updated the explainer to move a code example to the beginning of the proposal and have also added examples for the considered alternatives.

Best,
Johannes

[Alex Russell]

Thank you! LGTM1.

[Yoav Weiss (@Shopify)]

LGTM2

--
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+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b41ea5a5-9058-48fa-ad8c-a6ac9cf44713n%40chromium.org.

[Dan Clark]

LGTM3

[Johannes Kron]

Thanks everyone for the LGTMs!