- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Dec 2020 22:44:15 +0000
- To: public-webrtc-logs@w3.org
> It also bears mentioning that this type of permission-request (entire-tab) is easiest to communicate to the user; share-iframe-and-below is less straightforward. Permission these days is always to the top-level origin, which delegates with permissions policy, so no difference here. > Content from lower in the DOM can draw over content from higher in the DOM, and the application might wish for that to be captured. > [Unsure about this one:] It is not clear to me what efficiency even an optimal implementation of stream-thyself would be. Would the browser not effectively have to render twice? Good question. I assumed an optimal implementation could simply cut out a rectangle of its framebuffer, at least in the typical case of no DOM overlap. I admit I was thinking of this mostly as a cropping tool, and would not expect browsers to render twice, or render parts of an iframe extending outside the top-level browsing context's viewport. Although I suppose we could define it either way if there is WG interest. Not having to define what the desired output is in these overlap cases, is a leg up for top-level document capture I suppose. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/148#issuecomment-737540979 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 December 2020 22:44:17 UTC