- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Mar 2019 13:02:45 +0000
- To: public-webrtc-logs@w3.org
> the spec language IMO does not forbid ... Most behavior is not forbidden by specs. My reading of specs is that whatever they say to do is standard; whatever they don't is not. > In Chrome in particular, applyConstraints() allows changing resolution for peerconnection tracks via rescaling. If we want this behavior to be web compatible, I suggest we specify it. That's [what we did](https://w3c.github.io/mediacapture-screen-share/#constrainable-properties-for-captured-display-surfaces) for screen-capture. I'm happy to remove the *"will always be missing"*, to avoid implying we will never do this. Beyond that, this looks like a new feature in 1.0. which I think we should resist at this point, and encourage extension specs for. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2109#issuecomment-470516790 using your GitHub account
Received on Thursday, 7 March 2019 13:02:51 UTC