W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2019

Re: [webrtc-pc] Add video latency constrainable property (#2109)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 Mar 2019 15:07:08 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-470562089-1551971224-sysbot+gh@w3.org>
It doesn't specify *how* it should work. Implementors should not have to infer this. I think there's precedent here in https://github.com/w3c/mediacapture-screen-share/issues/31.

*MediaTrackSupportedConstraints* is returned from [navigator.mediaDevices.getSupportedConstraints()](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-mediadevices-getsupportedconstraints). How exactly is it relevant to RTCPeerConnection? 

Should the following blank the remote track and  fire `overconstrainederror` and ?
await transceiver.receiver.track.applyConstraints({width: {min: 1280}}); // succeeds
transceiver.receiver.track.onoverconstrainederror = () => { /* should this fire? */ };
// Network conditions or other side using replaceTrack causes lower resolution to appear

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2109#issuecomment-470562089 using your GitHub account
Received on Thursday, 7 March 2019 15:07:10 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC