On Wed, Mar 9, 2022 at 11:26 AM 'Elad Alon' via blink-dev < [email protected]> wrote:
> Contact [email protected] > > Explainer > https://github.com/w3c/mediacapture-handle/blob/main/identity/README.md > > Specificationhttps://w3c.github.io/mediacapture-handle/identity/ > > Summary > > We introduce a mechanism that allows an application to opt-in to exposing > certain information to other applications which are video-capturing it. > This allows collaboration between capturing and captured applications. For > example, a VC application that's video-capturing a tab where a presentation > application lives, could expose user-facing controls in the VC tab for > navigating the presentation in the captured tab. > > TAG reviewhttps://github.com/w3ctag/design-reviews/issues/645 > It seems worthwhile to give the TAG a few more weeks to get back to this, as they may be able to weigh in on some of the open issues. > > > TAG review statusPending > > Risks > Interoperability and Compatibility > > > *Gecko:* > No signal (https://github.com/mozilla/standards-positions/issues/615) > > Engaged in discussions in the W3C and approved the adoption of this > document. > > There is currently a disagreement with Mozilla over issue #11 > <https://github.com/w3c/mediacapture-handle/issues/11>. Mozilla suggests > setCaptureHandleConfig() should only be callable once, to reduce the risk > of it becoming an alternative communication channel. We see relevant use > cases that calling it multiple times can enable (e.g. the captured > application changing its state and wants to notify the capturer). We > believe setCaptureHandleConfig() should be callable multiple times. > Note that there could be other mitigations for Mozilla's concerns (e.g. > rate-limiting) that will keep the use cases intact. > We'd like to ship the API as callable multiple times, while continuing to > discuss this point. This could unfold in several ways: > > - We might be able to convince Mozilla of the correctness of our > viewpoint. > - We might find out that legitimate websites often call > setCaptureHandleConfig() multiple times (but not excessively), making it > easier for us to convince Mozilla. > - We might find out that websites rarely call setCaptureHandleConfig() > multiple times, allowing us to rather painlessly change the function to > being callable only once. > - We might find out that some websites call setCaptureHandleConfig() > multiple times in suspicious ways, in which case we'd change the function > to being callable only once. > > As part of the launch, we'll add usage metrics and keep close watch for > the possibility of suspicious usage of the type Mozilla is worried about. > In either case, we have a reasonable way forward regardless of how things > turn out. > > *WebKit:* > No signal ( > https://lists.webkit.org/pipermail/webkit-dev/2022-February/032140.html) > > Engaged in discussions in the W3C and approved the adoption of this > document. > > *Web developers:* > Strongly positive ( > https://docs.google.com/document/d/12LcwOy6AruoORAP7woswhBgG3cjoxVzQfPUuB6U-Vdo/edit?usp=sharing > ) > Strong positive signals from: > > - Google (link > > <https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/2> > ) > - Microsoft (link1 > > <https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/7>, > link2 <https://github.com/eladalon1983/capture-handle/issues/1>) > - Citrix (link1 > > <https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/12>, > link2 <https://github.com/w3c/mediacapture-handle/issues/14>) > - Zoom (link > > <https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/11> > ) > - RingCentral (link > > <https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/9> > ) > - Jitsi (link > > <https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/10> > ) > > *Other signals:* > N/A > > Debuggability > > No DevTools support is needed. > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ?No > > Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1200910 > > Launch bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1200907 > > Sample links > https://w3c.github.io/mediacapture-handle/identity/demos/remote_control/capturer.html > > https://w3c.github.io/mediacapture-handle//identity/demos/self_capture_detection/index.html > > Estimated milestones > OriginTrial desktop last 102 > OriginTrial desktop first 92 > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/4854125411958784 > > Links to previous Intent discussionsIntent to prototype: > https://groups.google.com/a/chromium.org/g/blink-dev/c/yLTykllpNmI > Intent to Experiment: > https://groups.google.com/a/chromium.org/g/blink-dev/c/RKONugfoGwM/m/mpFizHPxAwAJ > Intent to Extend Experiment: > https://groups.google.com/a/chromium.org/g/blink-dev/c/eJPOkBGriZc > Intent to Extend Experiment Again: > https://groups.google.com/a/chromium.org/g/blink-dev/c/fB3IZDgcoco > > > 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/CAMO6jDNrRWJfFKmB4__6WcL_un1F%2BF0L0bnN9k2zRzjT05DdWA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDNrRWJfFKmB4__6WcL_un1F%2BF0L0bnN9k2zRzjT05DdWA%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/CAL5BFfVu6ZZOGrWtmN9-bq1q1mHLE33pMa48PGUcHowBOyt8WA%40mail.gmail.com.
