- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Feb 2022 09:25:18 +0000
- To: public-webrtc-logs@w3.org
> That requires extending the API even further. For me, this is beyond the scope of an MVP. This is part of the API example exposed in the initial message of this thread. > whenever a CropTarget is minted, it "magically" produces a new entry elsewhere with a message in the form of your `name` field. It depends on the API used to create a CropTarget, this seems fine in scope of the API example exposed in the initial message of this thread. > This amounts to introducing yet another potentially-cross-origin message channel. Yes, that is my main concern, even though in practice it does not really matter (the fact you self capture is already breaking the isolation), it seems best to stick with something simple. It is also true that the simple case of transferring a track to worker and cropping in worker is simpler to implement with transferring a CropTarget. > Wdyt? `Improvement` label Sounds good to me. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/6#issuecomment-1027738919 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 February 2022 09:25:21 UTC