- From: camillelamy via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Apr 2021 12:43:43 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar I agree that the goal of COEP is to get pages to opt into environments with different risk profiles. I am just wondering how easy it is to communicate this risk profile to the developer. Probably, we need to work on the wording, as I am not super fan of what `COEP: require-corp; require-non-opaque` implies. To me it implies that the embedder could directly read the HTML of the embedded iframe, which it cannot do. To be clear, we are ok with a COEP based solution, as long as we envision several risk profiles being supported there. For example `COEP: require-corp; require-non-opaque-output` for getViewportMedia or `COEP: require-corp; require-non-opaque-resource-size` if we were to release a version of the memory measurement API that applies to the whole page instead of just the Agent Cluster. -- GitHub Notification of comment by camillelamy Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/155#issuecomment-820392671 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 April 2021 12:43:44 UTC