Re: [mediacapture-screen-share] Auto-pause capture when user switches captured content (#255)

@jan-ivar, I think we have general alignment on the solution and are now discussing the specifics of the shape. That works for me. In the interest of clarity, I am splitting this response in two. This comment covers where we agree; the next comment covers an open issue for discussion.

> Hence the name manualSwitching() instead of enableDynamicSwitching().

That name change works for me. Almost. I think `enable...` would make it clearer that it's a setter. So `enableManualSwitching()`.

> I'd prefer if this new API came with language to encourage browsers to not gate the feature only on apps that opt-in to the event model.

Works for me.

> I have reservations about abandoning the old _injection_ model which had some unique advantages:
> 
> 1. Works with all websites without needing their support (user benefits)
> 2. No need to replaceTrack downstream peer-connection sinks
> 3. No risk of ending a MediaRecorder sink recording prematurely

We are not currently planning to abandon the old model in Chrome's implementation. Thank you for documenting some of the reasons to retain it.

> 4. Difficult for apps to deny user switching (user benefits)

In the interest of transparency, I'd like to remind you of [surfaceSwitching](https://www.w3.org/TR/screen-capture/#dom-displaymediastreamoptions-surfaceswitching). But please note that it's an orthogonal discussion. We are neither introducing `surfaceSwitching` nor deprecating it. The semantics of the new event listener would be that it has an effect **if** the user chooses to switch surfaces.

> The UA could subsequently mute the audio track as needed rather than remove it. Thoughts?

I think that we have multiple challenges and a single API that solves them all, so I don't think we need an additional API that only solves a subset of the challenges (audio).


-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1731186860 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 22 September 2023 10:28:53 UTC