- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Jun 2022 22:24:15 +0000
- To: public-webrtc@w3.org
eladalon1983 has just created a new issue for https://github.com/w3c/mediacapture-region: == Cropping non-self-capture tracks == Assume `getDisplayMedia()` is called and the user chooses to capture another tab. The spec currently disallows cropping in such scenarios. But why? With Capture Handle Identity, it is possible for the capturing application to discover that it is capturing a tab with a known application. For example, maybe [meet.google.com](meet.google.com) is capturing [docs.google.com](docs.google.com). Such same-site applications will be able to communicate with each other using a BroadcastChannel[*], and the capturee can postMessage() a CropTarget to the capturer. Usecases are obvious (see example above). Why should we disallow this? -- [*] Using the mailman pattern. If the top-level documents are same-site, this communication method will not be blocked by Storage Partitioning. Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/63 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 June 2022 22:24:17 UTC