- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Feb 2022 11:41:34 +0000
- To: public-webrtc-logs@w3.org
> It seems potentially useful to pass an element directly to cropTo instead of a a CropTarget, especially if CropTarget is created asynchronously. I think it's a good idea, but a non-blocking ergonomics improvement that affects only some cases. I'm marking it as such. > One potential issue is if at some point, it is found good to have a CropTarget getter on the track itself. Resolution: Make `cropTo(Element)` implicitly create a `CropTarget` behind the scenes, and the getter will return that token, with no observable difference to the program between whether cropTo(Element) or cropTo(CropTarget) was previously called. Noteworthy: An implicitly minted CropTarget is how Chrome would implement this anyway, and most likely other UAs as well. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/19#issuecomment-1027855127 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 11:41:36 UTC