- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Nov 2017 12:46:19 +0000
- To: public-media-capture-logs@w3.org
@stefhak I think you're thinking of "constraining" = rescaling, which is not the spec definition. For instance, If `getUserMedia` worked that way, `max` and `exact` would be redundant. The spec defines `applyConstraints()` as a filtering function applied to a *UA-specific* pool of available [settings dictionaries](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-mediastreamtrack-applyconstraints()) (instances of [MediaTrackSettings](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-mediatracksettings)) for a device. A discovery API essentially. Firefox and Edge implement discrete settings dictionaries. Chrome implements a continuous space. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/495#issuecomment-341693674 using your GitHub account
Received on Friday, 3 November 2017 12:46:20 UTC