- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Jan 2021 19:34:48 +0000
- To: public-webrtc-logs@w3.org
> > multi-frame applications need a crop-ID and single-frame applications can pass the div's DOM node as a parameter. > > Why not have site L do the capture? Then there's no need to define this new crop-ID concept. Capturing is just the beginning of a frame's journey to remote users. Transmitting a video to a conference may involve a **significant** amount of application logic - especially with some upcoming/under-discussion features such as Breakout Box, Web Codecs, Insertable Streams, Lego Laser, etc. I don't think large applications like Slides/Docs, that normally do not handle any video-conferencing, should be expected to take on that responsibility. Letting a Slides-like application embed an iframe with a video-conferencing application (Meet/Zoom) is the natural thing, IMHO, and I think we should support such a use case. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-763883094 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 January 2021 19:34:50 UTC