- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Nov 2020 19:08:14 +0000
- To: public-webrtc-logs@w3.org
I agree with @annevk here on naming. The document is the largest object being captured. > If tab X captures itself, ... @eladalon1983 When we say something "captures itself", that something is the document, not the tab. → `getDocumentMedia`. > Implementation influencing API: The method of capturing done by GetDisplayMedia (and this version) involves grabbing the framebuffer after the browsing context has been rendered, I believe. @alvestrand Ah, I couldn't figure out why the API allowed an iframe to capture its embedder, when none of the use cases require it. → `getTopLevelDocumentMedia` would also be a mouthful. I'd humbly suggest an iframe only capture itself. A simpler story, and a useful cropping tool to boot. For implementations, cutting out the relevant rectangle from the framebuffer is hopefully not too difficult. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/148#issuecomment-735982430 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 November 2020 19:08:16 UTC