- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Apr 2021 08:20:44 +0000
- To: public-webrtc-logs@w3.org
> There's some pushback on the visibility requirement, since there are use cases of capturing e.g. a Google slides presentation in another open tab, without leaving the Google Meet tab, and basically remote-control the presentation with "next page", "previous page" commands out of band from there. Pushback on visibility requirements placed on `getViewportMedia` could not be motivated by the behavior of `getDisplayMedia`. Unless the two had to have the same visibility requirements, but I don't think that's the case. Speaking of requiring visibility for gVM, I do think it would be counter-productive. * Attacks are generally possible within the span of a single frame, escaping the user's notice¹. * The tab is visible at the moment capture starts. Taken together, these mean that attacks are possible immediately or never at all. Capture persisting after loss of visibility, does not enable new attacks. But maintaining the capture when visibility is lost does increase usability, even for gVM. The user can tab away and double-check a fact on Wikipedia without interrupting the call or alerting remote participants to their interaction with other tabs. --- ¹ Attacks that have been discussed thus far, that is. If new attacks are presented, I will recant. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/155#issuecomment-827416040 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 April 2021 08:20:46 UTC