- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 May 2021 13:56:24 +0000
- To: public-webrtc-logs@w3.org
I think these two suggestions are improvement. If we go with a generated ID, it could represent the tab and be immutable on navigation. Then comes the issue of what do in case of navigation. There may be an interest in other APIs to bootstrap tighter communication between two tabs. Maybe it deserves a specific API that could be reused outside of getDisplayMedia. In that case, maybe the generated ID should actually be a JS object that would be a proxy to the captured tab. If the captured page does not opt-in, this object does not expose any information/does not allow any interaction with the captured page. If the captured page opts in, some information is exposed (its origin for instance) and interaction with the captured page can be done through this object. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-849656441 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 May 2021 13:56:26 UTC