- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Jan 2022 15:53:14 +0000
- To: public-webrtc-logs@w3.org
> 1. There's no guarantee that `name` is unique, even within a given origin (consider same-origin iframes that are unaware of each other). In such a case, it'd still be necessary for the entity minting crop-IDs/TabRgions to communicate them directly to would-be collaborators. (Consider multiple non-collaborating iframes each declaring "main".) If that is indeed necessary, perhaps the effort of exposing regions on the track would be fruitless. Wdyt? Right, the goal of the proposal is indeed to use sensible names like "main", "slides"... Given there is an origin associated to the name, conflict may only happen for iframes of the same origin, so I would hope they are somehow collaborating and choose unique names that actually match within their origin. If it is not possible to fully collaborate (would be sad), the application could do something like "main-XYZ", "slides-XYZ", XYZ being given to the capturer for extra safety, "main" and "slides" having an application specific semantic. > 2\. Whoever mints a token, has to keep in mind that this is a "loud" and public action, that can be "heard" by unexpected entities, if they happen to be allowed to call gDM (and if the user approves the capture). This token is only visible to trusted parties, i.e. the top level frames or frames that are deemed capturing in the name of the top level frame. I think this gives a good enough story. That said, the proposal also allows to reduce exposure to specific origins (which makes most sense for non-self capture). > think you mean `readonly attribute MediaDevicesTabRegions regions` Right. > it's a bit more ergonomic if tokens are already attached to the track It is indeed more ergonomic because it is attached to the track. The additional point is that it allows a more declarative approach so that an iframe may create its regions without ever reacting to a message from its parent, or sending a message to its parent. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/6#issuecomment-1020246599 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 January 2022 15:53:16 UTC