- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Jun 2021 12:56:59 +0000
- To: public-webrtc-logs@w3.org
> I don't really see why it does not solve 2, 3 and 4, given MessagePort would be complemented by Origin. Assuming it IS complemented by origin, then some of these use-cases would also be **partially** addressed¹, but to an inferior extent. Motivating a change from our current approach to a new approach requires a set of compelling reasons. I have not yet heard such reasons. This new approach offers more complexity (where previously less complexity was requested by Apple) and inferior handling of the use-cases I have cited. Capture Handle is the superior solution here. -- 1. To name just one reason, consider top-level navigation. How would the capturer be notified now? Shall we add an event for that? If so, we'd be inching towards the Capture Handle proposal. We now have origin exposure, events - the only things we're missing are permittedOrigins² and the handle! 2. Please consider why permittedOrigins was included in the Capture Handle proposal - protecting again capturer dis-service if capturing a competitor. I trust you will see that you'd soon want to replicate that, too, in the new proposal. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-860662522 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 June 2021 12:57:42 UTC