- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jan 2022 16:29:55 +0000
- To: public-webrtc-logs@w3.org
> The creator of the region can decide which origins can learn about the region. That requires extending the API even further. For me, this is beyond the scope of an MVP. --- This thread has me convinced that we have a viable way forward for both (i) exposing region on the track and (ii) doing so in a way that's consistent with other-tab-capture. Tabling this discussion would not risk us painting ourselves into a corner. The only thing I see us potentially losing by not having this discussion right away, is that we might specify that `CropTarget` is transferable and is returned by `produceCropTarget`. This seems quite reasonable to me. With your improvement-proposal, collaborating frames would have to postMessage the `name` anyway. I don't think the delta between postMessage(name) and postMessage(cropTarget) is significant. Wdyt? `Improvement` label and revisit later? (Please consider that it might be more fruitful to have these discussions after more implementations - Safari, Firefox - have had the time to try this out and see what's challenging and what's not, and what the right trade-off would be.) -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/6#issuecomment-1022370476 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 January 2022 16:29:57 UTC