- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Mar 2022 18:36:59 +0000
- To: public-webrtc-logs@w3.org
> When getViewportMedia is specified, implemented and embraced by the Web, we can change this. We can't because of the design principle I [mentioned above](https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1064571776), so we need to decide on the default first. > Loom ... If the user captures the current tab, then the user can record a demo of using the application itself. (Loom appears to have [posted](https://www.youtube.com/channel/UCnqj2rfVX8V0t377WcOjYoA) to YouTube ~45 videos of how one uses their app.) Thanks, but I don't accept this as a use case, because it seems trivial (better even) to open the Loom page you want to record in a separate tab (which lets you demo any page, not just ones with recording controls embedded in them). > Is it Mozilla's opinion as a group, that if Firefox comes to support tab-sharing before we specify getViewportMedia and excludeCurrentTab, then gDM will not allow the user to share the current tab? Will this be the behavior Firefox UX and PMs choose to ship? PMs don't drive specs at Mozilla. Also, "[which choices are available to choose from is up to the user agent](https://w3c.github.io/mediacapture-screen-share/#dom-mediadevices-getdisplaymedia)", so no answer owed. I think the spec question isolates to: allow apps to express that A) they want self-capture, or B) they don't want self-capture. Whether they get it or not we already decided was irrelevant (a hint). I prefer A, because most sites are in B. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1065379977 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 March 2022 18:37:00 UTC