- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Sep 2019 09:14:36 +0000
- To: public-webrtc-logs@w3.org
Sometimes it makes sense to have the same constraints for tracks sourced by other means than GUM, and sometimes it does not. It has not been clear in the past. Going forward: Each spec needs to explicitly say which constraints are applicable to its tracks. I.e. captureStream() has to explicitly say that it supports crop-and-scale if that is something it does. Chromium assumed that constraints applied no matter the source as long as they "made sense", but different browsers may have made different assumptions. I believe chromium implements reading width and height by looking at frames, and reporting what it has seen recently, but I don't know the details. The spec should be clear what to do here, not surprised if chromium has a bug here. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/584#issuecomment-531698915 using your GitHub account
Received on Monday, 16 September 2019 09:14:37 UTC