- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jun 2022 14:53:52 +0000
- To: public-webrtc-logs@w3.org
Creating a `{}` crop target should not fail, because it would be premature to allocate cropping resources at this point for anything other than as a _UA optimization_. Any page can create cropTargets at any point, with zero knowledge of whether they'll ever be captured, making for a highly unreliable signal that cropping is about to happen.
UA optimizations are encouraged, but carry [inherent complexity](https://docs.google.com/presentation/d/1-SgzfMAeVG3u5vErJncC7OKDTGNDzSOMg_78LP8SULk/edit#slide=id.g133845ed595_0_2). I sense a general understanding in the web platform that:
1. good optimizations focus their efforts on typical cases, as not every corner case needs to be optimized
2. web developers should be shielded from complexity of when and how optimizations happen (if they happen)
3. We don't spec optimizations. As long as an API doesn't limit it, the burden is on UAs to optimize within the API
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/48#issuecomment-1152448560 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 June 2022 14:53:54 UTC