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

It doesn't specify *how* it should work. Implementors should not have to infer this. I think there's precedent here in

*MediaTrackSupportedConstraints* is returned from [navigator.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 using your GitHub account

Received on Thursday, 7 March 2019 15:07:10 UTC