- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Aug 2017 03:31:16 +0000
- To: public-media-capture-logs@w3.org
@guidou Interesting, but as a constraint, I think it fails, because while something like:
```js
await track.applyConstraints({height: 360, native: true});
```
...might give preference to native resolutions, the opposite:
```js
await track.applyConstraints({height: 360, native: false});
```
...would then give prefence specifically to non-native resolutions, which is always undesirable.
We'd also be bound by the [fitness-distance](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-fitness-distance) algorithm, so even with this `1` handicap, given that fake modes come with a perfect `0` score in `width`, `height`, `aspectRatio` and `frameRate`, we might not get the desired results in all cases.
Lastly, I'd like to reserve the UA's right to rescale in certain situations like https://github.com/w3c/mediacapture-main/issues/466#issuecomment-320375561, and `{native: {exact: true}}` might interfere with that.
As a boolean flag, I think it's redundant: `native: true` makes `min`, `max`, `exact`, `ideal` moot.
We didn't add `mandatory: true`, instead we overloaded the discovery keys `min`, `max` and `exact`.
Likewise, instead of `native: true` I think we should overload `min`, `max`, `exact`, and `ideal`.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/472#issuecomment-320483367 using your GitHub account
Received on Sunday, 6 August 2017 03:31:17 UTC