- From: Elad Alon via GitHub <noreply@w3.org>
- Date: Tue, 03 Jun 2025 21:39:19 +0000
- To: public-webrtc-logs@w3.org
> That is less tight. Does it make it sufficiently useful to implement it? I believe it's useful enough. I expect a Web app calling `cropTo()`/`applyConstraints()` would only connect the track to the sink after the promise resolves. Alternatively, apps disconnect the track from the sink, apply changes and then reconnect the track. Such apps do not typically care how many frames are missed, so long as things are reasonably quick. > Also, the current region capture timing is tighter than what you say: That much is a note that begins with "expected"; it is not a guarantee. > Do we have feedback from devs using cropTo + MSTP to help us? I am aware of products that basically obtains the track, crop it, and only start using it after the promise returned by `cropTo()` is resolved. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1017#issuecomment-2937282339 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:39:20 UTC