- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Aug 2017 04:29:22 +0000
- To: public-media-capture-logs@w3.org
@guidou Thanks for confirming, and glad to see this!
My one comment would be that, as I recall, one of our goals behind imbuing `ideal` with gravity in the [fitness distance](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-fitness-distance) algorithm was to locate a preferred native mode among several within a range. E.g.
```js
await track.applyConstraints({height: {min: 180, max: 1024, ideal: 180}}); // lowest native
await track.applyConstraints({height: {min: 160, max: 750, ideal: 750}}); // highest native
```
This does not appear to work in Chrome. Also, `advanced` doesn't seem particularly useful. e.g.:
```js
await track.applyConstraints({advanced: [{height: 180}, {height: 200}]}); // always 180
```
I've opened https://github.com/w3c/mediacapture-main/issues/472, we can continue there. Back to "different values per track" here.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/466#issuecomment-320485062 using your GitHub account
Received on Sunday, 6 August 2017 04:29:23 UTC