- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Oct 2017 00:29:01 +0000
- To: public-media-capture-logs@w3.org
@alvestrand With this idea, you'd still be able to invoke downscaling with bare value constraints:
```js
await track.applyConstraints({width: 640, height: 360}); // would downscale
await track.applyConstraints({width: 640, height: {max: 360}}); // would NOT downscale
```
...on the idea that `min`,`max` etc. are redundant when you know what you want.
In any case, this was just an idea I had about moving Chrome and Firefox behaviors closer together in https://github.com/w3c/mediacapture-main/issues/472#issuecomment-320484268. @guidou and I did not reach any consensus on that, so let me close it. We can re-open if there's renewed interest. The idea that bare values turn on downscaling is arbitrary perhaps.
The [current idea we're working on](https://bugzilla.mozilla.org/show_bug.cgi?id=1388667#c10) in Firefox is to downscale only where we'd throw `OverconstrainedError` otherwise, keeping everything else the same. This seemed like a reasonably intuitive way to not disrupt discovery of modes (which is our interpretation of spec intent), e.g. people can use `exact` or `max` to force downscaling.
However, while that seems like a reasonable interpretation of the spec to us, it does little to bridge differences between Chrome and Firefox, since bare values like
```js
await track.applyConstraints({width: 640, height: 360});
```
...would continue to downscale in Chrome but not in Firefox.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/473#issuecomment-338073816 using your GitHub account
Received on Friday, 20 October 2017 00:29:02 UTC