Re: [mediacapture-main] Fitness distance for bool placeholder & constraints not supported by device. (#766) from Jan-Ivar Bruaroey via GitHub on 2021-01-26 (public-webrtc-logs@w3.org from January 2021)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Tue, 26 Jan 2021 00:08:20 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-767193236-1611619699-sysbot+gh@w3.org>

@youennf asked me to test how `{facingMode: {exact}}` constains cameras with unknown facing mode, since this PR would define it. Results from this [fiddle](https://jsfiddle.net/jib1/ms6j9erq/) on desktop:

Browser | facingMode: {exact: "user"} | getSettings()
------------ | ------------- | -------------
Chrome | OverconstrainedError | facingMode: undefined
Edge | OverconstrainedError | facingMode: undefined
Firefox | OverconstrainedError¹ | facingMode: undefined
Safari | Success | facingMode: undefined

I think these results favor merging the PR as-is, and that we open an issue on webkit to align with the other browsers.

---
<sub>1. Firefox considers "Facetime" cameras on macOS to have `facingMode: "user"`, so instead I verified that exact constraints correctly excluded an attached Logitech camera from the camera picker in the permission prompt, which amounts to the same thing as `OverconstrainedError` had it been the only camera available.</sub>


-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/766#issuecomment-767193236 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 26 January 2021 00:08:22 UTC