This is shipping in m107. (Thank you François Beaufort for implementing!) On Wednesday, June 22, 2022 at 7:20:48 PM UTC+2 Elad Alon wrote:
> When I have an exact date, I will update ChromeStatus and ping this thread > with the target. Currently, I only know that it will be before EoY, but no > earlier than August. > > On Wed, Jun 22, 2022 at 7:17 PM Joe Medley <[email protected]> wrote: > >> When do you hope to ship? >> Joe Medley | Technical Writer, Chrome DevRel | [email protected] | >> 816-678-7195 <(816)%20678-7195> >> *If an API's not documented it doesn't exist.* >> >> >> On Wed, Jun 22, 2022 at 9:17 AM Daniel Bratell <[email protected]> wrote: >> >>> LGTM3 >>> >>> /Daniel >>> On 2022-06-22 17:42, Yoav Weiss wrote: >>> >>> LGTM2 >>> >>> On Wednesday, June 22, 2022 at 5:42:36 PM UTC+2 Chris Harrelson wrote: >>> >>>> LGTM1 >>>> >>>> On Wed, Jun 1, 2022 at 8:45 AM 'Elad Alon' via blink-dev < >>>> [email protected]> wrote: >>>> >>>>> Similar to other intents, this doesn't count as an official positive >>>>>> signal. Let's wait a few days to see if one emerges. >>>>> >>>>> >>>>> I've set a reminder to ping this thread in one week, as suggested in >>>>> the other intent thread. >>>>> >>>>> Any external signals from developers? >>>>>> https://goo.gle/developer-signals >>>>> >>>>> >>>>> Yes - here >>>>> <https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1143671194> >>>>> . >>>>> >>>>> >>>>> On Wed, Jun 1, 2022 at 8:44 AM Yoav Weiss <[email protected]> >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wednesday, May 25, 2022 at 2:41:36 PM UTC+2 Elad Alon wrote: >>>>>> >>>>>>> Contact emails [email protected] >>>>>>> >>>>>>> Explainer >>>>>>> https://docs.google.com/document/d/1M63lyDHV-v6LPFzHjfsjBDMfyn075pySa3xfIRSB9zU/edit?usp=sharing >>>>>>> >>>>>>> Specification >>>>>>> https://github.com/w3c/mediacapture-screen-share/pull/216/files >>>>>>> >>>>>>> Summary >>>>>>> >>>>>>> Hint allowing Web applications to instruct the browser whether, upon >>>>>>> calling getDisplayMedia(), the current tab should be excluded from the >>>>>>> list >>>>>>> of tabs offered to the user. >>>>>>> >>>>>>> >>>>>>> Blink component Blink >>>>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink> >>>>>>> >>>>>>> TAG review N/A. This is just an addition of a single flag to an >>>>>>> existing dictionary, following well-known patterns. >>>>>>> >>>>>>> TAG review status Not applicable >>>>>>> >>>>>>> Risks >>>>>>> >>>>>>> >>>>>>> Interoperability and Compatibility *Gecko*: Positive ( >>>>>>> https://github.com/mozilla/standards-positions/issues/639) 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/032249.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 Interest expressed by Google Meet. >>>>>>> >>>>>> >>>>>> Any external signals from developers? >>>>>> https://goo.gle/developer-signals >>>>>> >>>>>> >>>>>>> >>>>>>> Security >>>>>>> >>>>>>> The current tab is the surface most under an attacker’s control. >>>>>>> Nudging the user away from this risky surface is a good thing. Of >>>>>>> course, >>>>>>> malicious applications can avoid using this new control, or use it to >>>>>>> retain the old behavior (current tab still offered). This is not a >>>>>>> problem >>>>>>> - it simply means that this new surface offers no degradation in >>>>>>> security, >>>>>>> although not a security feature in its own right. >>>>>>> >>>>>>> >>>>>>> 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/5118675366445056 >>>>>>> >>>>>>> Links to previous Intent discussions Intent to prototype: >>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/COid122-_AE >>>>>>> >>>>>>> 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/CAMO6jDPX-8KjJhQy_Z890M1hrTLUnZV7EOmsN26QvCswtW268A%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDPX-8KjJhQy_Z890M1hrTLUnZV7EOmsN26QvCswtW268A%40mail.gmail.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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/22bbb540-09b2-4dda-838a-3c4bbd9cafacn%40chromium.org >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/22bbb540-09b2-4dda-838a-3c4bbd9cafacn%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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/71bfe123-8fc7-e226-1488-0be004b89060%40gmail.com >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/71bfe123-8fc7-e226-1488-0be004b89060%40gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/454a885f-1ffc-4fb0-8af7-d1d2d339f8c5n%40chromium.org.
