Re: [mediacapture-screen-share] Identification of Captured Application By Capturer (#166)

> @jan-ivar wanted a browser-assigned ID rather than an app-assigned handle.

I also wanted APIs like this under site-isolation and capture opt-in. So I'd say we've not reached our last point of disagreement.

> Another use-case is for a web-app to capture another tab and start driving this tab, which requires tight synchronization between the two. 

I feel @youennf understands the complexity that's not apparent in the OP as it conflates the capture of an "app" with capture of a tab:

> When VC-Max asks to capture a tab, and the **user chooses Presentron**, we want VC-Max to be able to identify that this selection took place. Moreover, we want Presentron to be able to declare an ID; VC-Max can then use this ID to address messages solely to the specific captured Presentron session.

To poke holes: what if the user instead chooses a non-Presentron tab, but later navigates to Presentron in it?

I'm not ready to concede that to capture a web-based presentation program _requires_ indiscriminate capture of its browsing context and all its navigation. That's an unsafe foundation to build on IMHO. We have a mandate to make web capture safe. And this isn't.

I'm also not ready to concede that to solve basic "next/previous slide" controls, _requires_ building the ability to remotely browse ("drive") a tab. 

This proposal also presents a stark contrast to `getViewportMedia` which by design isn't able to follow links easily. That's a potential shortcoming of `getViewportMedia`, since some modern web presentations may contain links that a presenter plans to follow during their presentation.

I'd prefer to take a step back and have a higher-level discussion around that. I think there's a way to solve this that is both safe and solves the web presentation use case, but I'll open a new issue on that.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-853491883 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 01:30:54 UTC