- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Sun, 03 Jul 2022 20:32:32 +0000
- To: public-webrtc-logs@w3.org
> what if the CropTarget UUID was also made visible as a property of the track.
Do you mean a property of the track via being a property of Capture Handle? If so, yes, I've [had this idea](https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1170596724) too. The idea is basically for the capturee to expose a mapping like `{'name1': cropTarget1, 'name2': cropTarget2}`. But please note that this is still not useful for arbitrary pairs of capturer/capturee, because "name1" is not meaningful to the capturer if it does not recognize the capturee. I just don't think that a video-conferencing tool is going to invest engineering effort in receiving and applying crop-targets "of interest" from unknown websites. From **known websites** where a collaboration is set up manually by product managers - that's a different story.
--
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1173166969 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 3 July 2022 20:32:34 UTC