- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Jun 2021 20:54:48 +0000
- To: public-webrtc-logs@w3.org
> Using [Capture Handle](https://github.com/w3c/mediacapture-screen-share/issues/166) ... VC applications could use this knowledge to pause remote-sharing and prompt the user to confirm they'd still like to share. ... This is a partial solution ... That's interesting, but I'd like to see this solved in the user agent, and not leave it up to individual sites to get right. What if the browser did this instead? Would you be on board with that? > (you estimated 2023) I did not. I picked 2023 in my [crystal ball slide](https://docs.google.com/presentation/d/1fyRuFEqIsMrBg5KnfRxyH_2DRo3yudtOqI7ritpMUo0/edit#slide=id.gd97c219958_0_32) as a frame of reference far enough out to avoid arguments over claims like _"All major presentation websites use site-isolation and opt into html capture"_. The point of such slides is to induce hindsight: imagine this has happened, then review whether interim proposals were steps in the right direction or shortsighted or even counter-productive. I feel we've made good progress on defining site-isolation and capture opt-in over the last few months, so I'm bullish on it being spec'able and implementable long before then, if we can agree on where to apply it. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/182#issuecomment-854992734 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 June 2021 20:55:28 UTC