- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Sat, 12 Jun 2021 16:56:04 +0000
- To: public-webrtc-logs@w3.org
@eladalon1983 They haven't. I [said](https://twitter.com/jibrewery/status/1403427341867655171) _"Their view on a similar proposal [[#155](https://github.com/w3c/mediacapture-screen-share/issues/155#issuecomment-812009563)] for easy self-share is that it requires not only site-isolation but opt-in from targets in order to be safe"_, and [then](https://twitter.com/jibrewery/status/1403429226385129473) _"We've put forth a proposal that would give web-pages that meet these security-criteria preferential placement in the getDisplayMedia() picker."_ > Chrome Security has spoken for cross-origin isolation and an opt-in header for getViewportMedia. We're interpreting the scope of their advice differently. They [said](https://github.com/w3c/mediacapture-screen-share/issues/155#issuecomment-812009563) _"this as a larger problem of APIs that might leak data from cross-origin resources at the page-level."_ > That's a different topic. Different API, same topic: how to have webpages capture webpages safely. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-860079809 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 12 June 2021 16:56:30 UTC