- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 14:06:27 +0000
- To: public-webrtc-logs@w3.org
> with no way for the captured app to opt-out of that part. Captured app could always opt-out of exposing its origin. One known use-case is for a web-app to ensure it is capturing itself or one of its tab. This could be supported by this 'modest' proposal. Another use-case is for a web-app to capture another tab and start driving this tab, which requires tight synchronization between the two. My understanding is that this is similar to the previous case (user needs to select the right google doc tab) except that the two tabs will start interacting. This can be supported by this 'modest' proposal. The third use-case is the same as previous one, except that now the main captured document that is part of the synchronization might disappear and synchronization might be recreated by the next top level document of the same tab. I haven't really thought about the corner cases and potential issues, but this seems more complex (although worth investigating). I also wonder whether there will be other cases where user will relate two pages for improved processing, in which case it would be nice to factor out the bootstrapping mechanism from the actual communication channel. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-852154402 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 14:07:07 UTC