Re: [mediacapture-main] What is the granularity of a source? (#940)

While a source being UA-wide may have worked in the past, it breaks https://github.com/w3c/mediacapture-main/issues/804 so I think we're down to:
1. Source is per-document, or
2. Source is per top-level document

As the [stop all sources](https://w3c.github.io/mediacapture-main/#dfn-stop-all-sources) algorithm is currently written, it only works with 1. So the archeological answer is 1.

But I'd like to propose 2.

If we look at what source/device intersects with in the spec, it's: permission, privacy indicators, and track lifetime.

[Permissions integration](https://w3c.github.io/mediacapture-main/#permissions-integration) ties device permission to the top-level document, and [privacy indicators](https://w3c.github.io/mediacapture-main/#privacy-indicator-requirements) are implemented at that level too.

Regarding lifetime, I think our main concern in https://github.com/w3c/mediacapture-extensions/pull/30 was also around privacy and permission. E.g. that a user revoking _permission_ in the original web page ends transferred tracks as well, and that _privacy indicators_ remain on the original web page's tab for as long as transferred tracks are alive.

In the old days, we didn't have to consider track lifetime outside of the document that spawned a track, but now we do. And it seems to me that tying lifetime to the top-level document might be fine.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/940#issuecomment-1476894285 using your GitHub account


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

Received on Monday, 20 March 2023 20:34:49 UTC