- From: Elad Alon via GitHub <noreply@w3.org>
- Date: Tue, 03 Jun 2025 18:07:49 +0000
- To: public-webrtc-logs@w3.org
Where does the difficulty lie? Note that the [Region Capture spec](https://w3c.github.io/mediacapture-region/) does something similar: > Call the track's state before this method invocation PRE-STATE, and after this method invocation POST-STATE. The user agent MUST resolve p when it is guaranteed that no more frames cropped (or uncropped) according to PRE-STATE will be delivered to the application, and that any additional frames delivered to the application will therefore be cropped (or uncropped) according to either POST-STATE or a later state. > > Note: > > The timing of the cropTo promise resolution and the timing of the actual cropping of video frames is observable to JavaScript through [MediaStreamTrack transforms](https://w3c.github.io/mediacapture-transform/). It is expected that the first newly cropped video frame will be enqueued on the MediaStreamTrack ReadableStream just after the cropTo promise is resolved. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1017#issuecomment-2936564884 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 June 2025 18:07:50 UTC