- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Mar 2022 14:42:15 +0000
- To: public-webrtc-logs@w3.org
> > Thinking a bit more though, I don't see why the spec mandates to expose a single CropTarget per Element. It makes implementations a bit harder without any real benefit. Maybe this is a left over from the CropID initial version? Removing this constraint from the spec and making cropTarget a method (probably renaming it to getXYZ as well) seems like a good idea to me. > > Could you please explain why this is a problem for implementers? To document some out-of-band discussions, I am OK with the spec mandating that an **equivalent** CropTarget, which is a less stringent requirement. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1072477262 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 March 2022 14:42:16 UTC