- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 May 2022 21:15:03 +0000
- To: public-webrtc-logs@w3.org
I should add (or I'll be called out on it) it goes on to say: _"The user agent MUST resolve p only after it has finished all the necessary internal propagation of state associated with the new [CropTarget](https://w3c.github.io/mediacapture-region/#dom-croptarget), at which point the user agent MUST be ready to receive the new [CropTarget](https://w3c.github.io/mediacapture-region/#dom-croptarget) as a valid parameter to [cropTo](https://w3c.github.io/mediacapture-region/#dom-browsercapturemediastreamtrack-cropto)."_ — but the sole requirement here seems to be that a newly created target MUST be accepted by cropTo, which is easily accomplished a number of ways given that any target must be postMessaged and cropTo is already async. The need for returning a promise for this is what has no consensus and is being challenged. Also this second part is about of _how_ it does what it does, whereas my initial quote is more importantly about what it _does_, which doesn't match claims made here. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1130559281 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 May 2022 21:15:05 UTC