- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Sep 2022 20:57:05 +0000
- To: public-webrtc-logs@w3.org
> @youennf, I think you were amenable to this during TPAC 2022...? I think this is a reasonable answer to the crop target on another tab use case. An alternative to consider is to enable MessagePort level communication. One thing to consider is that the current 1024 bytes size might be harder to define with objects. As a side note, and this also applies to structured exposure of CropTargets, if a web application starts to create CropTargets proactively, UAs should make the creation of such objects cheap and only start expensive operations when these objects are actually used to crop. This is another argument in favour of creating CropTarget synchronously. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/68#issuecomment-1256669741 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 September 2022 20:57:06 UTC