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

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

From: guidou via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 Mar 2019 13:42:47 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-470529591-1551966166-sysbot+gh@w3.org>
I interpret the text "The basics of MediaTrackSupportedConstraints, MediaTrackCapabilites, MediaTrackConstraints and MediaTrackSettings is outlined [GETUSERMEDIA]" to mean that applyConstraints(), getCapabilities() and getSettings() should work for PeerConnection tracks in the way that is indicated in the getUserMedia() spec.  Thus, I do not see why these functions should not work for PeerConnection tracks.

I do not interpret the text saying that the only properties visible in MediaTrackSettings are those actually available on a PeerConnection to mean that getSettings() is the only function from the constraintable pattern that should work on PeerConnection tracks. If that is the way it should be interpreted, I think it needs a rewrite because that is not what is says.

GitHub Notification of comment by guidou
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2109#issuecomment-470529591 using your GitHub account
Received on Thursday, 7 March 2019 13:42:48 UTC

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