- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Aug 2017 17:44:25 +0000
- To: public-media-capture-logs@w3.org
> What about constraining the maximum aspect ratio? If you're asking if FF would consider rescaled modes or not, I'd say we ["can use any information available"](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-selectsettings) to make that decision. We don't need agreement for that. It'd be nice if our behaviors aligned better however. That's why I opened this issue. For instance, FF could appease the we-want-what-we-want group with rescaling in this case: ```js await navigator.mediaDevices.getUserMedia({video: 640, height: 360}); // downscales 640x480 ``` while still leaving everything else as-is: ```js await navigator.mediaDevices.getUserMedia({video: 640, height: {exact: 360}}); // error ``` It'd be internally inconsistent, and thus confusing, but as much as we all like to admire internal consistency, we tend to forget that cross-browser inconsistency is often equally confusing. I'm exploring sacrificing some internal consistency to achieve cross-browser consistency. To turn this around, assuming no interest in a new constraint, what might you be interested in pursuing to narrow the current browser gap in output from the constraints algorithm? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/472#issuecomment-321030003 using your GitHub account
Received on Tuesday, 8 August 2017 17:44:25 UTC