- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jul 2022 07:14:03 +0000
- To: public-webrtc-logs@w3.org
The issue is not really about other UA implementations but about web developer impact. For instance, given Chrome is globally capping the number of CropTarget due to resource exhaustion risks, web developers might want to cautiously create CropTargets, typically only once they know the web page is being captured. This goes against the idea of a web site proactively creating some CropTargets. This might also have an impact on future additions to this API. It would be good to understand whether Chrome has a plan to fix this global resource exhaustion issue. As I understand it, the main problem seems to be implementation cost. I already said that but working on https://github.com/w3c/mediacapture-region/issues/48 may allow to make progress on this particular issue. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1175864798 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 July 2022 07:14:06 UTC