- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Mar 2019 14:44:44 +0000
- To: public-webrtc-logs@w3.org
Separate from this proposal, the spec language IMO does not forbid applyConstraints() from working on tracks sourced by a peer connection. It just says "The basics of ... is outlined in [GETUSERMEDIA]". In Chrome in particular, applyConstraints() allows changing resolution for peerconnection tracks via rescaling. With regards to this proposal, I think giving a different meaning to the latency property in remote tracks, as proposed in the #2110, (instead of saying it doesn't exist) should neither mandate nor forbid constraining its value. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2109#issuecomment-470133015 using your GitHub account
Received on Wednesday, 6 March 2019 14:44:45 UTC