- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Apr 2021 14:48:08 +0000
- To: public-webrtc-logs@w3.org
I agree that `getViewportMedia` is the holy grail. And I agree that some risks remain for `getDisplayMedia` + #166. But OP's site is **already** using `getDisplayMedia`, and might continue for a while¹. I think #166 could partially mitigate some of those risks. Examining the risk of support personnel's homepages - if they have them at all, you could mitigate by hosting them cross-origin from the main site. And even if assume it is easy to convince an end-user to type a URL and then start sharing it, the extra step is definitely valuable in that it prevents accidental oversharing. Even if tightly sealing against abuse is not achieved, I think #166 presents a small improvement for OP. (Note: This is not #166's main goal. Only the last benefit of four listed atm.) --- 1. It will take some time for gVM to be standardized and implemented; probably longer than #166. And even once gVM is implemented, OP's site might not be able to deploy COI + new-header, and keep relying on gDM. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/143#issuecomment-818796245 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 April 2021 14:48:10 UTC