- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Jun 2021 11:25:22 +0000
- To: public-webrtc-logs@w3.org
> * Because it does not address all use-cases as well as exposing a capture-handle. (Note use-cases 2, 3 and 4 in the original message.) I don't really see why it does not solve 2, 3 and 4, given MessagePort would be complemented by Origin. > * Because it's an effort of greater complexity, larger scope, and much more significant security and privacy ramifications. Well, that is the end goal of the main use case you are bringing to the table. If MessagePort does not work for security reasons, I wonder whether the same security reasons might not impact the capture handle proposal. > * Because it's good to have that as a later extension. You have been advocating small initial scope, after all. Small initial scope would be origin, maybe origin plus pathname or something like that. If we expose MessagePort, the handle does seem somehow redundant. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-860609470 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 11:25:35 UTC