- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Jun 2021 22:26:45 +0000
- To: public-webrtc-logs@w3.org
> controlling an app I think it pays to be exact when discussing potentially-alarming concepts like "control" of an app. The capturing app does **not** "control" the captured app. It is sending it messages. The captured app is not compelled to react to these messages, or even to read them. When a captured tab is navigated, no power is coercing the newly loaded application to continue the collaboration that the previous app started. I think we should keep it crisp and clear in our minds that there is no concern of residual control surviving navigation of the captured tab. > We can't share an app, so we share the next best thing: it's tab. This is an entirely different, pre-existing issue, and I think it should be addressed separately. > Adding slide controls on top of this would further lull users into this misconception. This is a valid concern, but I do not find it compelling. The reverse could also be argued - that by keeping the user away from the captured tab, unintended navigation by clicking `back` too often becomes far less likely. By establishing collaboration and keeping the user focused on the capturing tab, we emulate the properties of app-capture and reap its benefits. These benefits might be more firmly established once we **also** provide actual app-capture, but I see no reason to delay progress here. > and I'm just picking products out of a hat... Google Slides... Google Meet... Google gives away too much swag. Our hats are everywhere. 😉 -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/182#issuecomment-854225873 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 22:27:13 UTC