> > Similar to other intents, this doesn't count as an official positive > signal. Let's wait a few days to see if one emerges.
Thanks. I've set a reminder to ping this thread in one week, as suggested in the other intent thread. On Wed, Jun 1, 2022 at 8:42 AM Yoav Weiss <[email protected]> wrote: > > > On Wednesday, May 25, 2022 at 2:44:01 PM UTC+2 Elad Alon wrote: > >> Contact [email protected] >> >> Explainer >> https://docs.google.com/document/d/1OmuV1W4f2UvToeNxUVGHv8NcFuL63r94gWwz9i_-VBc/edit?usp=sharing >> >> Specification >> https://github.com/w3c/mediacapture-screen-share/pull/164/files >> >> Summary >> >> Consider a Web application APP which is display-capturing a tab TAB. We >> add a mechanism by which APP may control whether the audio playing in TAB >> would be played out of the user’s local speakers. >> >> >> Blink componentBlink >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink> >> >> TAG reviewN/A. This is just an addition of a single flag to an existing >> dictionary, following well-known patterns. >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> *Gecko*: Positive ( >> https://github.com/mozilla/standards-positions/issues/641) Jan-Ivar >> Bruaroey from Mozilla, and Youenn Fablet from Apple, have both collaborated >> with us closely in shaping this PR. They have then approved merging this PR >> into w3c/mediacapture-screen-share. This is implicit support, so I'd >> consider it POSITIVE even though, as of the time of this writing, the >> official request for position has not yet been answered. >> >> *WebKit*: Positive ( >> https://lists.webkit.org/pipermail/webkit-dev/2022-May/032252.html) >> Jan-Ivar Bruaroey from Mozilla, and Youenn Fablet from Apple, have both >> collaborated with us closely in shaping this PR. They have then approved >> merging this PR into w3c/mediacapture-screen-share. This is implicit >> support, so I'd consider it POSITIVE even though, as of the time of this >> writing, the official request for position has not yet been answered. >> > > Similar to other intents, this doesn't count as an official positive > signal. Let's wait a few days to see if one emerges. > > >> >> *Web developers*: Positive >> >> - This was requested by multiple Web-dev teams inside of Google. >> - External developers have asked for a different change in Chrome, >> which we'll be able to uncontroversially affect only once this API surface >> is shipped - see crbug.com/1317964 for some details. >> >> > That's encouraging! > > >> >> *Other signals*: >> >> WebView application risks >> >> N/A >> >> >> >> Debuggability >> >> N/A >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)?No. Supported on all >> platforms that support getDisplayMedia. (Namely, all desktop platforms.) >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> Estimated milestones >> >> No milestones specified >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5201258309746688 >> >> Links to previous Intent discussionsIntent to prototype: >> https://groups.google.com/a/chromium.org/g/blink-dev/c/cANVKeNMHyE >> >> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDP4jD21fkKqyKdKysF_DERp%3DKzFx_u3eydAQ5jTNGWnAA%40mail.gmail.com.
