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

Re: [webrtc-pc] Define which constraints are applicable in WebRTC (#2188)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 26 Jul 2019 21:38:59 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-515607259-1564177138-sysbot+gh@w3.org>
> Looking at what Chrome is exposing, resizeMode is also potentially in scope.

This is a good example of something that would require specification. Presumable `"none"` might mean the RTPeerConnection has some indication or reason to believe the video has not downscaled for bandwidth reasons (but how can it know? Is it in the SDP?)

> By default, there is none inherited from mediacapture-main.

We already have a [note](https://w3c.github.io/mediacapture-main/getusermedia.html#media-track-supported-constraints) for that.

> In webrtc-pc spec: no constrainable property is mandatory for any remote source. A user agent MAY expose constrainable properties defined in media capture-main to remote sources.

I think I'd rather not say anything than have a MAY. It's hard to test a MAY. By the mediacapture note, I think we merely need to omit mentioning any constraints here. Then we can leave it to an extension spec to define them, maybe?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2188#issuecomment-515607259 using your GitHub account
Received on Friday, 26 July 2019 21:39:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:26 UTC