Re: [webrtc-pc] Constrainable properties on remote tracks are under-specified (#2121)

My 2 cents.

With respect to the behavior of applyConstraints() as well as gUM constraints, my understanding is that they should behave as filters, not as settings. This means that for local tracks it makes sense to filter which device should be used based on some criteria but with remote tracks this seems blurry, mostly because such parameters are anyway negotiated (hence, I am not sure why, after negotiation one should further filter for the right track).

GitHub Notification of comment by armax00
Please view or discuss this issue at using your GitHub account

Received on Monday, 11 March 2019 08:23:56 UTC