W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2022

Re: [mediacapture-region] Can the MediaStreamTrack list its cropping regions directly? (#6)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Jan 2022 20:53:31 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1021598450-1643144010-sysbot+gh@w3.org>
This comment continues the discussion of `expose-on-track`. Please note that, as per my previous comment, I argue that this should be a **later improvement**.

> ```
> interface MediaStreamTrackRegion {
>     USVString origin;
>     DOMString name;
> }
> ```

I think we want these to be `readonly`.

Assume we (later) extends `produceCropId()` to receive `name` as a parameter. (The `origin` is inferred from the call-site.) There's a decision to be made here. Do we...
1. ...reject `produceCropTarget(name)` if the pair `(name, origin)` would not be unique?
2. ...add a random field that ensures uniqueness?
3. ...specify that two CropTargets with the same fields can nevertheless distinct? That is, that there might be an unexposed property that's part of any comparison?

My order of preference is currently with no1 as the most preferred and no3 as the least preferred.

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

It's a credible story only so long as we don't try to reuse this mechanism for cropping non-own-tabs. That is to say, 



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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 January 2022 20:53:33 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC