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

Re: [mediacapture-region] Cropping non-self-capture tracks (#63)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Fri, 24 Jun 2022 17:53:29 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1165802971-1656093207-sysbot+gh@w3.org>
As mentioned during the interim yesterday ([2022-06-23](https://www.w3.org/2011/04/webrtc/wiki/June_23_2022)), it's incumbent on those who wish to maintain this limitation to explain why it's necessary. Barring a good explanation, we have resolved[1] to remove this limitation in the interim after the next one.

One argument mentioned by @jan-ivar[2] during that meeting as well as in the past, was his concern that a captured application might falsely advertise a CropTarget consisting of 0x0 pixels, and the capturer might mindlessly apply this CropTarget, to the detriment of the user.

I **do not** find that concern compelling:
- Why would the capturer apply an unknown CropTarget from an unknown source?
- Why can't it solve its own issue by NOT applying that CropTarget?
- Is the Web in general better off without this useful feature, just because very rare applications might use it unwisely?
- How does the capturee transmit the CropTarget to the capturer?
  - Using BroadcastChannel or similar? So they're same origin and have trust.
  - Using Capture Handle and stringification or similar? Then it can check the origin and ignore CropTargets from unknown/untrusted sources.

I am looking forward to hearing either counter-counter-arguments or alternative rationales for maintaining the limitation. Barring those, I hope that we can all agree that removing the limitation would be useful; we don't necessarily have to wait two interim meetings for that.

CC interested parties as reflected by the active participants of the meeting: @dontcallmedom, @aboba, @alvestrand, @jan-ivar, @youennf, @steely-glint.

[1] I shall point to the minutes once they're posted.
[2] The usual caveat - if my attempt at representing was your concern fell short, please set the record straight by posting a better description of it. I will edit my own comment to better reflect your stated position.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 June 2022 17:53:30 UTC

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