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

> 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:

That tabs can be navigated after capture begins was [discussed explicitly](https://github.com/w3c/mediacapture-screen-share/issues/159#issue-843753041) two months ago in my very first message on this topic. In [this linked message](https://github.com/w3c/mediacapture-screen-share/issues/159#issue-843753041), search for the section titled "What if the user navigates the captured tab?"

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

We have discussed this. If you refer back to [my slides](https://docs.google.com/presentation/d/1fyRuFEqIsMrBg5KnfRxyH_2DRo3yudtOqI7ritpMUo0/edit#slide=id.gd98744a95d_5_145), you will see that there is an event fired.

> 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.

1. The capturing app is **already** capturing the entire browsing context. It's called [getDisplayMedia](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getDisplayMedia).
2. The capturing app is **already** observing navigation because it's getting all of the pixels from captured tab.
3. Capture Handle increases the ergonomics of observing navigation, but in a limited fashion. Please see [this section](https://docs.google.com/document/d/1oSDmBPYVlxFJxb7ZB_rV6yaAaYIBFDphbkx5bXLnzFg/edit#heading=h.cytoxb710h2) and also [this one](https://docs.google.com/document/d/1oSDmBPYVlxFJxb7ZB_rV6yaAaYIBFDphbkx5bXLnzFg/edit#heading=h.uxe72vr1msqs) of my [public explainer](https://docs.google.com/document/d/1oSDmBPYVlxFJxb7ZB_rV6yaAaYIBFDphbkx5bXLnzFg/).

> 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.

I am afraid that our memories over what this feature is are out of alignment. I'd like to encourage you to re-read (a) [the original thread](#159), (b) [OP](#166) and (c) [the explainer](https://docs.google.com/document/d/1oSDmBPYVlxFJxb7ZB_rV6yaAaYIBFDphbkx5bXLnzFg/). Capture-Handle does **not** "build" the ability to remotely drive the tab. That's something you **can** build on top of Capture-Handle.

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-853724560 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 09:23:00 UTC