- From: youennf via GitHub <noreply@w3.org>
- Date: Tue, 03 Jun 2025 21:07:57 +0000
- To: public-webrtc-logs@w3.org
applyConstraints promise resolution will typically be done via the main thread but will receive frames off the main thread, at least in WebKit. rfvc/video element videoWidth and so on will get updated based on off the main thread information so will not be synchronised tightly with applyConstraints resolution. With MSTP, there is a tighter coordination since both applyConstraints resolution and frame reception happen in the worker thread. But the two paths to get this information may be different (they are in WebKit). When discussed at the WebRTC WG meeting, it was thought that mandating tight synchronisation in the worker thread would require a good justification to bother implementing this (and we would need to select synchronisation with which API) Looking at region capture spec, it specifically mentions MSTP so maybe we should move this issue to media capture transform, or dupe it to https://github.com/w3c/mediacapture-transform/issues/115. I agree `cropTo()` and `applyConstraints()` should probably behave the same. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1017#issuecomment-2937208911 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 21:07:57 UTC