W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2020

Re: [mediacapture-screen-share] Capture-current-tab: Managing capture-ability by cross-origin embedder as opt-in vs. opt-out (#156)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Dec 2020 18:52:54 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-746821699-1608144773-sysbot+gh@w3.org>
(At the risk of paraphrasing the minutes which aren't up yet) the WG at [last interim](https://www.w3.org/2011/04/webrtc/wiki/December_14_2020) seemed to disfavor opt-out over security concerns with site-driven capture, wishing instead to explore forms of opt-in, e.g. by blanking out non-consenting iframes.

> ... it would be prohibitively difficult for them to transition their very substantial application

Conversely, it would be prohibitively difficult for the rest of the web to opt-out of this new feature and its risks.

> ... lack of adoption

Does this potential user foresee embedding rich media features in the future? If so, they'll want powerful features like `SharedArrayBuffer` anyway, which [is already opt-in](https://web.dev/why-coop-coep/).

> I think it would be good if we could hear from other prospective users of this API.

Yes, clarification of use cases would be good, as so far they seem to only involve sites that want to be captured. `getDisplayMedia` remains the catch-all for those that don't, but it seems safer to leave those in the hands of the user.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/156#issuecomment-746821699 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 December 2020 18:52:56 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:53 UTC