- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Jul 2021 08:57:44 +0000
- To: public-webrtc-logs@w3.org
> Another potential approach: > > * Add an API for tab viewport capture, e.g. navigator.mediaDevices.getTabViewPortMedia() > * Add an API for document viewport capture, e.g. document.getViewPortMedia() > * Add an API for iframe viewport capture, e.g. HTMLIFrameElement.getViewPortMedia() > All these methods would call the same underlying algorithm which would take a viewport as internal parameter. > This underlying algorithm would be responsible of permission policy, prompting, creation of MediaStreamTrack... > > With this approach, there is no default option to select in the spec and no surprise from web developers on what they will get. > Another advantage is easier discovery of whether tab/self/iframe capture are supported: browsers can gradually implement them and applications gracefully fallback. > Also, if we want to extend to other nodes (all elements for instance), getViewPortMedia() can be defined for those nodes. I'd be happy with this approach. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-872060951 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 July 2021 08:57:46 UTC