- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Jun 2021 21:46:31 +0000
- To: public-webrtc-logs@w3.org
I think they're coupled, because we haven't sufficiently isolated (not pun intended) the use case of sharing and controlling an _app_ from that of sharing and controlling its _tab_ and everything in it (including its bfcache and anywhere new you go). * We can't share an app, so we share the next best thing: it's tab. This is oversharing. And it can bite people, because it deceptively _feels_ like sharing an app in the moment, even to tech savvy users who should know better. Adding slide controls on top of this would further lull users into this misconception. But this car has no seat-belts: hit the back button one too many times and you've accidentally shared what you were browsing right before the meeting to the entire meeting (and if it was a WG meeting, it is now on YouTube). Why is this acceptable? To me, it seems we should be able to safely offer, say — and I'm just picking products out of a hat here — the ability to share a Google Slides presentation in Google Meet, without the risk of accidentally sharing _anything else_. With this explained, I'll amend this proposal to consider freeze-and-prompt on "safe" cross-origin navigation as well. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/182#issuecomment-854202310 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 June 2021 21:47:11 UTC